All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, Ingo Molnar <mingo@elte.hu>,
	thomas.jarosch@intra2net.com
Subject: Re: [patch 1/1] alloc_pages(): permit get_zeroed_page(GFP_ATOMIC) from interrupt context
Date: Mon, 27 Aug 2007 15:45:58 -0700	[thread overview]
Message-ID: <20070827154558.1c04e77f.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0708271512390.8783@schroedinger.engr.sgi.com>

On Mon, 27 Aug 2007 15:12:58 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:

> On Mon, 27 Aug 2007, Andrew Morton wrote:
> 
> > > Nesting (at least allocate a 
> > > regular page while highmem page is being mapped) needs to work in order to 
> > > be able to allocate a page from an interrupt contexts.
> > 
> > yup, but interrupt-level code should use the reserved-for-interrupt kmap
> > slots (KM_IRQ0, etc).
> 
> We are not using any kmap slot since we are allocating a non highmem page!

Right.  So a get_zeroed_page() from IRQ context happens to be not buggy,
even though it goes BUG.

So what do we do?

a) don't call clear_highpage() for non-highmem pages (my fix)

b) don't do the is-the-pte-zero check in kmap_atomic_prot() if the page
   isn't highmem

   This is bad because it'll disable the check completely if the machine
   doesn't physically have highmem, or if the page happened to be a lowmem
   one.

c) don't do the is-the-pte-zero check if __GFP_HIGHMEM wasn't set.

   OK, but we don't pass the gfp_t into kmap_atomic.  So we need to do
   this at the caller site.  That's what a) does.

--
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:[~2007-08-27 22:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23 21:07 [patch 1/1] alloc_pages(): permit get_zeroed_page(GFP_ATOMIC) from interrupt context akpm, Andrew Morton
2007-08-27 20:13 ` Christoph Lameter
2007-08-27 20:33   ` Andrew Morton
2007-08-27 21:00     ` Christoph Lameter
2007-08-27 21:04       ` Andrew Morton
2007-08-27 21:20         ` Christoph Lameter
2007-08-27 21:32           ` Christoph Lameter
2007-08-27 21:34           ` Andrew Morton
2007-08-27 21:43             ` Christoph Lameter
2007-08-27 22:11               ` Andrew Morton
2007-08-27 22:12                 ` Christoph Lameter
2007-08-27 22:45                   ` Andrew Morton [this message]
2007-08-27 23:01                     ` Christoph Lameter
2007-08-27 23:40                       ` Andrew Morton
2007-08-27 23:48                         ` Christoph Lameter

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=20070827154558.1c04e77f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=thomas.jarosch@intra2net.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.