From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/2] ia64,kexec: refactor some mmu-related marcors to allow them to be reused by kexec
Date: Tue, 20 Jun 2006 09:09:19 +0000 [thread overview]
Message-ID: <20060620090919.61ECF3402B@koto.vergenet.net> (raw)
In-Reply-To: <20060619082353.GA15635@verge.net.au>
In article <20060620062252.GB18805@cse.unsw.EDU.AU> you wrote:
> On Tue, Jun 20, 2006 at 02:47:57PM +0900, Horms wrote:
>> Sure, could you give me a quick heads-up on what I should do to make
>> that happen.
>
> Well, personally, I'd like to see the whole thing pulled out in
> something like
>
> http://www.gelato.unsw.edu.au/archives/linux-ia64/0511/15890.html
>
> (ignore the bug I missed in ivt.S)
>
> I guess it should be sufficient to just do something like
>
> #ifdef CONFIG_PGTABLE_3
> #define MAPPED_SPACE_BITS (3*(PAGE_SHIFT - PTE_BITS) + PAGE_SHIFT)
> #elif CONFIG_PGTABLE_4
> #define MAPPED_SPACE_BITS (4*(PAGE_SHIFT - PTE_BITS) + PAGE_SHIFT)
> #endif
>
> (but then VMALLOC_END is still "wrong", you still can't easily change
> the PTE size...)
>
> This is really tangential to your change however, so probably doesn't
> belong in the same changeset. Maybe I could revive that old patch if
> anyone has any comments.
Well, I was thinking in terms of a second patch.
I'd be happy to look over (or upport) a fresh version of your
patch, but I will be up front and say that my understanding of
pte vs pmd, pud and pgd is weak. That said, I for one think
your patch did make things easier to understand, and probably
easier to update.
--
Horms http://www.vergenet.net/~horms/
prev parent reply other threads:[~2006-06-20 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 8:23 [PATCH 1/2] ia64,kexec: refactor some mmu-related marcors to allow them to be reused by kexec Horms
2006-06-20 2:14 ` Horms
2006-06-20 3:31 ` Ian Wienand
2006-06-20 5:47 ` Horms
2006-06-20 6:22 ` Ian Wienand
2006-06-20 9:09 ` Horms [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=20060620090919.61ECF3402B@koto.vergenet.net \
--to=horms@verge.net.au \
--cc=linux-ia64@vger.kernel.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