linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	William Lee Irwin III <wli@movementarian.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: pud_bad vs pud_bad
Date: Thu, 05 Feb 2009 13:05:36 -0800	[thread overview]
Message-ID: <498B54A0.7040005@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0902052046240.18431@blonde.anvils>

Hugh Dickins wrote:
>> Hardware doesn't allow it.  It will explode (well, trap) if you set anything
>> other than P in the top level.
>>     
>
> Oh, interesting, I'd never realized that.
>   

There are some later extensions to reuse some of the bits for things 
like tlb reload policy (I think; I'd have to check to be sure), so 
they're fairly non-pte-like.

>> By the by, what are the chances we'll be able to deprecate non-PAE 32-bit?
>>     
>
> I sincerely hope 0!  I shed no tears at losing support for NUMAQ,
> but why should we be forced to double all the 32-bit ptes?  You want
> us all to be using NX?  Or you just want to cut your test/edit matrix -
> that I can well understand!
>   

Yes, that's the gist of it.  We could simplify things by having only one 
pte format and only have to parameterise with 3/4 level pagetables.  
We'd lose support for non-PAE cpus, including the first Pentium M (which 
is probably still in fairly wide use, unfortunately).

    J

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-02-05 21:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 18:23 Jeremy Fitzhardinge
2009-02-05 18:43 ` Ingo Molnar
2009-02-05 18:54   ` Jeremy Fitzhardinge
2009-02-05 19:10     ` Ingo Molnar
2009-02-05 19:26       ` Jeremy Fitzhardinge
2009-02-05 19:31         ` Ingo Molnar
2009-02-05 19:38       ` Hugh Dickins
2009-02-05 19:49         ` Ingo Molnar
2009-02-05 19:58           ` wli
2009-02-05 20:14             ` Hugh Dickins
2009-02-05 20:56               ` wli
2009-02-05 21:09                 ` Hugh Dickins
2009-02-05 20:12           ` Hugh Dickins
2009-02-05 20:42         ` Jeremy Fitzhardinge
2009-02-05 20:51           ` Hugh Dickins
2009-02-05 21:05             ` Jeremy Fitzhardinge [this message]
2009-02-05 21:50               ` Ingo Molnar
2009-02-05 22:07                 ` Jeremy Fitzhardinge
2009-02-05 23:42                   ` Ingo Molnar
2009-02-06  0:08                     ` Jeremy Fitzhardinge
2009-02-06  0:50                       ` Ingo Molnar
2009-02-05 20:57           ` Ingo Molnar

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=498B54A0.7040005@goop.org \
    --to=jeremy@goop.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=wli@movementarian.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