From: "Steven J. Hill" <Steven.Hill@imgtec.com>
To: Jayachandran C <jchandra@broadcom.com>
Cc: <ralf@linux-mips.org>, <linux-mips@linux-mips.org>
Subject: Re: [PATCH 0/3] Use scratch registers when MIPS_PGD_C0_CONTEXT is not set
Date: Wed, 26 Jun 2013 18:31:07 -0500 [thread overview]
Message-ID: <51CB79BB.9090905@imgtec.com> (raw)
In-Reply-To: <1372011381-18600-1-git-send-email-jchandra@broadcom.com>
On 06/23/2013 01:16 PM, Jayachandran C wrote:
>
> Jayachandran C (3):
> MIPS: Move generated code to .text for microMIPS
> MIPS: mm: Use scratch for PGD when !CONFIG_MIPS_PGD_C0_CONTEXT
> MIPS: Move definition of SMP processor id register to header file
>
> arch/mips/include/asm/mmu_context.h | 28 ++---
> arch/mips/include/asm/stackframe.h | 24 +---
> arch/mips/include/asm/thread_info.h | 33 +++++-
> arch/mips/mm/Makefile | 2 +-
> arch/mips/mm/tlb-funcs.S | 37 ++++++
> arch/mips/mm/tlbex.c | 224 ++++++++++++++++-------------------
> 6 files changed, 187 insertions(+), 161 deletions(-)
> create mode 100644 arch/mips/mm/tlb-funcs.S
>
The microMIPS kernel compiles, but fails to boot. It stops at:
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
and does not go any further. I will look at this later this evening.
-Steve
WARNING: multiple messages have this Message-ID (diff)
From: "Steven J. Hill" <Steven.Hill@imgtec.com>
To: Jayachandran C <jchandra@broadcom.com>
Cc: ralf@linux-mips.org, linux-mips@linux-mips.org
Subject: Re: [PATCH 0/3] Use scratch registers when MIPS_PGD_C0_CONTEXT is not set
Date: Wed, 26 Jun 2013 18:31:07 -0500 [thread overview]
Message-ID: <51CB79BB.9090905@imgtec.com> (raw)
Message-ID: <20130626233107.qTEVc64_9fzE7rRUbes9MHBg1AwiD0Gf6PtKAWlJSSw@z> (raw)
In-Reply-To: <1372011381-18600-1-git-send-email-jchandra@broadcom.com>
On 06/23/2013 01:16 PM, Jayachandran C wrote:
>
> Jayachandran C (3):
> MIPS: Move generated code to .text for microMIPS
> MIPS: mm: Use scratch for PGD when !CONFIG_MIPS_PGD_C0_CONTEXT
> MIPS: Move definition of SMP processor id register to header file
>
> arch/mips/include/asm/mmu_context.h | 28 ++---
> arch/mips/include/asm/stackframe.h | 24 +---
> arch/mips/include/asm/thread_info.h | 33 +++++-
> arch/mips/mm/Makefile | 2 +-
> arch/mips/mm/tlb-funcs.S | 37 ++++++
> arch/mips/mm/tlbex.c | 224 ++++++++++++++++-------------------
> 6 files changed, 187 insertions(+), 161 deletions(-)
> create mode 100644 arch/mips/mm/tlb-funcs.S
>
The microMIPS kernel compiles, but fails to boot. It stops at:
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
and does not go any further. I will look at this later this evening.
-Steve
next prev parent reply other threads:[~2013-06-26 23:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 18:16 [PATCH 0/3] Use scratch registers when MIPS_PGD_C0_CONTEXT is not set Jayachandran C
2013-06-23 18:16 ` [PATCH 1/3] MIPS: Move generated code to .text for microMIPS Jayachandran C
2013-06-23 18:16 ` [PATCH 2/3] MIPS: mm: Use scratch for PGD when !CONFIG_MIPS_PGD_C0_CONTEXT Jayachandran C
2013-06-23 18:16 ` [PATCH 3/3] MIPS: Move definition of SMP processor id register to header file Jayachandran C
2013-06-26 18:32 ` [PATCH 0/3] Use scratch registers when MIPS_PGD_C0_CONTEXT is not set Ralf Baechle
2013-06-26 23:31 ` Steven J. Hill [this message]
2013-06-26 23:31 ` Steven J. Hill
2013-06-27 0:00 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51CB79BB.9090905@imgtec.com \
--to=steven.hill@imgtec.com \
--cc=jchandra@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox