linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
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 16:01:28 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708271550550.9100@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070827154558.1c04e77f.akpm@linux-foundation.org>

On Mon, 27 Aug 2007, Andrew Morton wrote:

> So what do we do?
> 
> a) don't call clear_highpage() for non-highmem pages (my fix)

Then we need to be sure that this is the only case where we call 
clear_highpage() from an interrupt. This solves an i386 arch problem in 
core code. Other arches are not broken like that. See f.e. sparc:

void *kmap_atomic(struct page *page, enum km_type type)
{
        unsigned long idx;
        unsigned long vaddr;

        /* even !CONFIG_PREEMPT needs this, for in_atomic in do_page_fault */
        pagefault_disable();
        if (!PageHighMem(page))
                return page_address(page);

        idx = type + KM_TYPE_NR*smp_processor_id();
        vaddr = __fix_to_virt(FIX_KMAP_BEGIN + idx);


> 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.

The check is meaningless if we do not have highmem. kmap_atomic is a 
function to be used in atomic context. I.e. interrupts. Nested by 
definition. It is broken as is since it BUG()s on a legitimate nested 
call.

> 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.

Would that not mean leaving kmap_atomic broken on i386? Before Ingo's 
commit things were fine. Revert the commit and there is no need 
to change core code.

What exactly is the point of checking that a kmap_atomic of a non highmem 
page cannot occur during the kmap_atomic of a highmem page? AFAICT this is 
fine.

--
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 23:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23 21:07 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
2007-08-27 23:01                     ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0708271550550.9100@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=akpm@linux-foundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox