From: "Jan Beulich" <JBeulich@novell.com>
To: "FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>
Cc: <mingo@elte.hu>, <yinghai@kernel.org>, <tglx@linutronix.de>,
<tiwai@suse.de>, <linux-kernel@vger.kernel.org>,
<jbarnes@virtuousgeek.org>, <hpa@zytor.com>
Subject: Re: [PATCH] x86: adjust GFP mask handling for coherent allocations
Date: Tue, 27 Oct 2009 09:47:32 +0000 [thread overview]
Message-ID: <4AE6CFC4020000780001BF75@vpn.id2.novell.com> (raw)
In-Reply-To: <20091027183658A.fujita.tomonori@lab.ntt.co.jp>
>>> FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> 27.10.09 10:37 >>>
>On Tue, 27 Oct 2009 09:23:38 +0000
>"Jan Beulich" <JBeulich@novell.com> wrote:
>
>> Because there's quite a few of them - just search for callers of
>> dma_alloc_coherent() passing NULL as the first argument. Of course
>> I'd rather see the fallback gone, but I think this requires cooperation
>> from/action taken by the driver maintainers first. A first step might be
>> to add a WRN_ON() for that case, but I don't see it being reasonable
>> to eliminate the fallback right away. Hence, with it having got broken
>> in .26 I think it is reasonable to fix it for the time being.
>
>Well, the most of them are drivers that nobody cares about (uses).
>
>What drivers did you hit this problem with?
drivers/firmware/dell_rbu.c (on .27.x, and in particular with the derivation
of __GFP_NORETRY from __GFP_DMA, which fortunately doesn't exist in
newer kernels anymore).
>We've lived with the current code for some years so this problem isn't
>urgent at all. Please don't add another workaround for broken code.
>Let's put WARN_ON for callers that use NULL and see who complains.
Jan
next prev parent reply other threads:[~2009-10-27 9:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 12:03 [PATCH] x86: adjust GFP mask handling for coherent allocations Jan Beulich
2009-10-23 11:48 ` Ingo Molnar
2009-10-26 15:13 ` Jan Beulich
2009-10-26 15:22 ` Ingo Molnar
2009-10-26 15:45 ` Jan Beulich
2009-10-26 20:19 ` Ingo Molnar
2009-10-26 20:44 ` Jesse Barnes
2009-10-27 1:38 ` FUJITA Tomonori
2009-10-27 8:58 ` Jan Beulich
2009-10-27 9:00 ` Jan Beulich
2009-10-27 9:11 ` FUJITA Tomonori
2009-10-27 9:23 ` Jan Beulich
2009-10-27 9:37 ` FUJITA Tomonori
2009-10-27 9:47 ` Jan Beulich [this message]
2009-10-27 10:15 ` FUJITA Tomonori
2009-10-27 10:19 ` Alan Cox
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=4AE6CFC4020000780001BF75@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
--cc=yinghai@kernel.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