From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [rfc] dynamic 3-level / 4-level page table
Date: Fri, 28 Apr 2006 17:22:25 +0000 [thread overview]
Message-ID: <4t153d$rpmen@azsmga001.ch.intel.com> (raw)
In-Reply-To: <4sur0l$s99mf@fmsmga001.fm.intel.com>
Robin Holt wrote on Friday, April 28, 2006 8:34 AM
> On Thu, Apr 27, 2006 at 07:09:17PM -0700, Chen, Kenneth W wrote:
> > --- ./arch/ia64/kernel/ivt.S.orig 2006-04-27 19:21:55.000000000 -0700
> > +++ ./arch/ia64/kernel/ivt.S 2006-04-27 19:46:44.000000000 -0700
> > @@ -142,16 +142,16 @@ ENTRY(vhpt_miss)
> > (p7) dep r17=r18,r17,3,(PAGE_SHIFT-6) // r17=pgd_offset for region[0-4]
> > cmp.eq p7,p6=0,r21 // unused address bits all zeroes?
> > #ifdef CONFIG_PGTABLE_4
> > - shr.u r28=r22,PUD_SHIFT // shift pud index into position
> > + extr.u r28=r22,PUD_SHIFT,11 // get pud index
>
> How well does this work with different page sizes?
Thanks! I should've use PTRS_PER_PTD_SHIFT for that constant "11". I forgot
to put that in.
> > +
> > +#ifdef CONFIG_PGTABLE_4
> > +int pgtbl3;
> > +static __init int setup_pgtbl3(char *s)
> > +{
> > + pgtbl3 = 1;
> > + return 0;
> > +}
> > +early_param("pgtbl3", setup_pgtbl3);
> > +#endif
>
> What about taking out CONFIG_PGTABLE_*, having the default be 3, and have the
> boot option enable 4 levels? I haven't given this much though yet, but my
> first reaction was that would be the correct way to go.
OK, if there isn't any objections from other people, I will go ahead and do
it that way.
next prev parent reply other threads:[~2006-04-28 17:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 2:09 [rfc] dynamic 3-level / 4-level page table Chen, Kenneth W
2006-04-28 8:57 ` Zoltan Menyhart
2006-04-28 15:33 ` Robin Holt
2006-04-28 17:16 ` Chen, Kenneth W
2006-04-28 17:22 ` Chen, Kenneth W [this message]
2006-05-02 8:28 ` Zoltan Menyhart
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='4t153d$rpmen@azsmga001.ch.intel.com' \
--to=kenneth.w.chen@intel.com \
--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