From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: RFC: powerpc: Start splitting up mmu.h by MMU type
Date: Sun, 22 Apr 2007 10:35:13 +1000 [thread overview]
Message-ID: <1177202113.6080.28.camel@localhost.localdomain> (raw)
In-Reply-To: <17961.19168.571692.127151@cargo.ozlabs.ibm.com>
> > Specifically it splits the ppc64 specific (or more strictly, the
> > 64-bit hash table specific) parts of asm-powerpc/mmu.h into its own
> > file, asm-powerpc/mmu-hash64/mmu.h. Similarly, PowerPC 44x
> > definitions are taken from asm-ppc/mmu.h, trimmed down for use in
> > arch/powerpc and place in their own file, asm-powerpc/mmu-44x/mmu.h.
>
> Why do we want to create a directory per mmu type? What other files
> would go in there?
Especially if we're ever going to get a different MMU type on 64 bits, I
would really like to try to be able to build a kernel supporting both
(if realistic).
Ben.
prev parent reply other threads:[~2007-04-22 0:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 6:54 RFC: powerpc: Start splitting up mmu.h by MMU type David Gibson
2007-04-19 12:11 ` Kumar Gala
2007-04-20 0:56 ` David Gibson
2007-04-20 19:26 ` Kumar Gala
2007-04-20 23:21 ` Paul Mackerras
2007-04-22 0:35 ` Benjamin Herrenschmidt [this message]
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=1177202113.6080.28.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).