From: Hugh Dickins <hugh@veritas.com>
To: Bill Irwin <wli@holomorphy.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Bob Tracy <rct@gherkin.frus.com>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.22-rc6 bad page error
Date: Thu, 12 Jul 2007 17:13:46 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707121708180.4887@blonde.wat.veritas.com> (raw)
In-Reply-To: <20070712134606.A10012@jurassic.park.msu.ru>
On Thu, 12 Jul 2007, Ivan Kokshaysky wrote:
> On Wed, Jul 11, 2007 at 06:07:59PM +0100, Hugh Dickins wrote:
>
> > > + return __pci_alloc_consistent(dev, size, dma, GFP_ATOMIC);
> >
> > I was going to ask you why that needs to be GFP_ATOMIC on Alpha.
> > But find you're following the example of asm-generic and others.
> > So really should be asking Sparc how it gets away with GFP_KERNEL.
>
> According to DMA-mapping.txt GFP_ATOMIC is mandatory for
> pci_alloc_consistent() since it can be called from interrupt context.
> So sparc code is probably incorrect...
Hi Bill, we've veered away from the original topic, and are wondering
how the sparc32 pci_alloc_consistent() gets away with using GFP_KERNEL,
when GFP_ATOMIC seems to be required?
Hugh
prev parent reply other threads:[~2007-07-12 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070705195835.AAB19DBA1@gherkin.frus.com>
2007-07-07 13:48 ` 2.6.22-rc6 bad page error Michal Piotrowski
2007-07-07 14:56 ` Bob Tracy
2007-07-07 18:38 ` Hugh Dickins
2007-07-08 21:05 ` Bob Tracy
2007-07-09 18:53 ` Bob Tracy
2007-07-10 20:25 ` Hugh Dickins
2007-07-11 13:02 ` Ivan Kokshaysky
2007-07-11 17:07 ` Hugh Dickins
2007-07-12 9:46 ` Ivan Kokshaysky
2007-07-12 16:13 ` Hugh Dickins [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=Pine.LNX.4.64.0707121708180.4887@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@linux-foundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=rct@gherkin.frus.com \
--cc=wli@holomorphy.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