From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Björn Steinbrink" <B.Steinbrink@gmx.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.24-git: kmap_atomic() WARN_ON()
Date: Tue, 26 Feb 2008 10:19:28 -0800 [thread overview]
Message-ID: <20080226101928.f6c16c66.akpm@linux-foundation.org> (raw)
In-Reply-To: <47C43F18.6060207@pobox.com>
On Tue, 26 Feb 2008 11:32:24 -0500 Jeff Garzik <jgarzik@pobox.com> wrote:
> Ingo Molnar wrote:
> > * Jeff Garzik <jgarzik@pobox.com> wrote:
> >
> >> + unsigned long flags;
> >> +
> >> + local_irq_save(flags);
> >
> > hm, couldnt we attach the irq disabling to some spinlock, in a natural
> > way? Explicit flags fiddling is a PITA once we do things like threaded
> > irq handlers, -rt, etc.
>
> Attaching the irq disabling to some spinlock is what would be
> artificial... See the ahci.c patch earlier in this thread. It is taken
> without spin_lock_irqsave() in the interrupt handler, and there is no
> reason to disable interrupts for the entirety of the interrupt handler
> run -- only the part where we call kmap.
>
> This is only being done to satisfy kmap_atomic's requirements, not libata's.
>
> I could add a "kmap lock" but that just seems silly.
>
It's a bit sad to disable interupts across a memset (how big is it?) just
for the small proportion of cases which are accessing a highmem page.
What you could do is to add an `unsigned long *flags' arg to
ata_scsi_rbuf_get() and ata_scsi_rbuf_put(), and then, in
ata_scsi_rbuf_get() do
if (PageHighmem(page))
local_irq_disable(*flags);
next prev parent reply other threads:[~2008-02-26 18:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 23:58 2.6.24-git: kmap_atomic() WARN_ON() Thomas Gleixner
2008-02-13 22:39 ` Rafael J. Wysocki
2008-02-14 1:13 ` Thomas Gleixner
2008-02-25 19:59 ` Björn Steinbrink
2008-02-25 20:08 ` Jeff Garzik
2008-02-25 20:35 ` Björn Steinbrink
2008-02-25 20:40 ` Andrew Morton
2008-02-25 22:01 ` Thomas Gleixner
2008-02-25 22:17 ` Andrew Morton
2008-02-25 23:19 ` Jeff Garzik
2008-02-26 8:39 ` Ingo Molnar
2008-02-26 16:32 ` Jeff Garzik
2008-02-26 18:19 ` Andrew Morton [this message]
2008-02-26 20:49 ` Ingo Molnar
2008-02-26 21:37 ` Andrew Morton
2008-02-26 22:59 ` Jeff Garzik
2008-02-27 0:02 ` Alan Cox
2008-02-26 23:49 ` Nick Piggin
2008-02-26 8:50 ` Thomas Gleixner
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=20080226101928.f6c16c66.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=B.Steinbrink@gmx.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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