public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Hugh Dickins <hugh@veritas.com>,
	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, 5 Feb 2009 21:57:35 +0100	[thread overview]
Message-ID: <20090205205735.GA21500@elte.hu> (raw)
In-Reply-To: <498B4F1F.5070306@goop.org>


* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> Hugh Dickins wrote:
>> However... I forget how the folding works out.  The pgd in the 32-bit
>> PAE case used to have just the pfn and the present bit set in that
>> little array of four entries: if pud_bad() ends up getting applied
>> to that, I guess it will blow up.
>>   
>
> Ah, that's a good point.
>
>> If so, my preferred answer would actually be to make those 4 entries
>> look more like real ptes; but you may think I'm being a bit silly.
>
> Hardware doesn't allow it.  It will explode (well, trap) if you set  
> anything other than P in the top level.

Yeah. I was the first Linux hacker in history to put a x86 CPU into PAE mode 
under Linux 10+ years ago, and i can attest to the 'explodes way too easily' 
aspect quite emphatically ;-) Took me 3-4 days to bootstrap it.

> By the by, what are the chances we'll be able to deprecate non-PAE 32-bit?

For the next 10 years: pretty much zero.

	Ingo

      parent reply	other threads:[~2009-02-05 20:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 18:23 pud_bad vs pud_bad 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
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 [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=20090205205735.GA21500@elte.hu \
    --to=mingo@elte.hu \
    --cc=hugh@veritas.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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