From: "Jan Beulich" <JBeulich@novell.com>
To: <mingo@elte.hu>, <tglx@linutronix.de>, <hpa@zytor.com>
Cc: "Takashi Iwai" <tiwai@suse.de>, <linux-kernel@vger.kernel.org>,
<jbarnes@virtuousgeek.org>
Subject: [PATCH] x86: adjust GFP mask handling for coherent allocations
Date: Thu, 22 Oct 2009 13:03:48 +0100 [thread overview]
Message-ID: <4AE06644020000780001B4AD@vpn.id2.novell.com> (raw)
Rather than forcing GFP flags and DMA mask to be inconsistent, GFP
flags should be determined even for the fallback device through
dma_alloc_coherent_mask()/dma_alloc_coherent_gfp_flags(). This
restores 64-bit behavior as it was prior to commits
8965eb19386fdf5ccd0ef8b02593eb8560aa3416 and
4a367f3a9dbf2e7ffcee4702203479809236ee6e (not sure why there are two of
them), where GFP_DMA was forced on for 32-bit, but not for 64-bit, with
the slight adjustment that afaict even 32-bit doesn't need this without
CONFIG_ISA.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Cc: Takashi Iwai <tiwai@suse.de>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
---
arch/x86/include/asm/dma-mapping.h | 4 +---
arch/x86/kernel/pci-dma.c | 8 +++++---
2 files changed, 6 insertions(+), 6 deletions(-)
--- linux-2.6.32-rc5/arch/x86/include/asm/dma-mapping.h 2009-10-19 13:09:44.000000000 +0200
+++ 2.6.32-rc5-x86-dma-mask-gfp/arch/x86/include/asm/dma-mapping.h 2009-10-22 10:54:08.000000000 +0200
@@ -124,10 +124,8 @@ dma_alloc_coherent(struct device *dev, s
if (dma_alloc_from_coherent(dev, size, dma_handle, &memory))
return memory;
- if (!dev) {
+ if (!dev)
dev = &x86_dma_fallback_dev;
- gfp |= GFP_DMA;
- }
if (!is_device_dma_capable(dev))
return NULL;
--- linux-2.6.32-rc5/arch/x86/kernel/pci-dma.c 2009-10-19 13:09:45.000000000 +0200
+++ 2.6.32-rc5-x86-dma-mask-gfp/arch/x86/kernel/pci-dma.c 2009-10-22 10:56:46.000000000 +0200
@@ -45,12 +45,14 @@ int iommu_pass_through __read_mostly;
dma_addr_t bad_dma_address __read_mostly = 0;
EXPORT_SYMBOL(bad_dma_address);
-/* Dummy device used for NULL arguments (normally ISA). Better would
- be probably a smaller DMA mask, but this is bug-to-bug compatible
- to older i386. */
+/* Dummy device used for NULL arguments (normally ISA). */
struct device x86_dma_fallback_dev = {
.init_name = "fallback device",
+#ifdef CONFIG_ISA
+ .coherent_dma_mask = DMA_BIT_MASK(24),
+#else
.coherent_dma_mask = DMA_BIT_MASK(32),
+#endif
.dma_mask = &x86_dma_fallback_dev.coherent_dma_mask,
};
EXPORT_SYMBOL(x86_dma_fallback_dev);
next reply other threads:[~2009-10-22 12:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 12:03 Jan Beulich [this message]
2009-10-23 11:48 ` [PATCH] x86: adjust GFP mask handling for coherent allocations 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
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=4AE06644020000780001B4AD@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--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 \
/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