From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Takashi Iwai <tiwai@suse.de>, Jan Beulich <JBeulich@novell.com>,
tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH, v3] x86: Adjust GFP mask handling for coherent allocations
Date: Sun, 8 Nov 2009 07:45:14 -0800 [thread overview]
Message-ID: <20091108074514.61e6857c@jbarnes-piketon> (raw)
In-Reply-To: <20091108111214.GK11372@elte.hu>
On Sun, 8 Nov 2009 12:12:14 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Takashi Iwai <tiwai@suse.de> wrote:
>
> > At Wed, 04 Nov 2009 12:28:39 +0000,
> > Jan Beulich wrote:
> > >
> > > 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>
> >
> > Acked-by: Takashi Iwai <tiwai@suse.de>
>
> Jesse, mind picking this up for .32?
>
> I've attached below a slightly cleaned up version of the patch, with
> Takashi's ack added.
Sure, I just stuffed it into my for-linus tree, I'll send a pull req on
Monday or Tuesday.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-11-08 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 12:28 [PATCH] x86: adjust GFP mask handling for coherent allocations (take 2) Jan Beulich
2009-11-06 15:41 ` Takashi Iwai
2009-11-08 11:12 ` [PATCH, v3] x86: Adjust GFP mask handling for coherent allocations Ingo Molnar
2009-11-08 15:45 ` Jesse Barnes [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=20091108074514.61e6857c@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=JBeulich@novell.com \
--cc=hpa@zytor.com \
--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
all inboxes | Powered by JetHome®