From: "Jan Beulich" <JBeulich@suse.com>
To: "David Vrabel" <david.vrabel@citrix.com>
Cc: <x86@kernel.org>, "Thomas Gleixner" <tglx@linutronix.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
<xen-devel@lists.xenproject.org>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Ingo Molnar" <mingo@redhat.com>, <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Xen-devel] [PATCH 2/3] x86: allow dma_get_required_mask() to be overridden
Date: Thu, 13 Nov 2014 10:25:28 +0000 [thread overview]
Message-ID: <546495280200007800047203@mail.emea.novell.com> (raw)
In-Reply-To: <1415805906-27316-3-git-send-email-david.vrabel@citrix.com>
>>> On 12.11.14 at 16:25, <david.vrabel@citrix.com> wrote:
> --- a/arch/x86/include/asm/device.h
> +++ b/arch/x86/include/asm/device.h
> @@ -13,4 +13,6 @@ struct dev_archdata {
> struct pdev_archdata {
> };
>
> +#define ARCH_HAS_DMA_GET_REQUIRED_MASK
Is there a particular reason you put this here rather than in
dma-mapping.h?
Jan
next prev parent reply other threads:[~2014-11-13 10:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 15:25 [PATCHv2 0/3]: dma,x86,xen: reduce SWIOTLB usage in Xen guests David Vrabel
2014-11-12 15:25 ` [PATCH 1/3] dma,ia64: add dma_get_required_mask_from_max_pfn() David Vrabel
2014-11-14 15:11 ` [Xen-devel] [PATCH 1/3] dma, ia64: " Stefano Stabellini
2014-11-12 15:25 ` [PATCH 2/3] x86: allow dma_get_required_mask() to be overridden David Vrabel
2014-11-13 10:25 ` Jan Beulich [this message]
2014-11-13 10:30 ` [Xen-devel] " David Vrabel
2014-11-13 10:32 ` Jan Beulich
2014-11-14 15:19 ` Stefano Stabellini
2014-11-12 15:25 ` [PATCH 3/3] x86/xen: use the maximum MFN to calculate the required DMA mask David Vrabel
2014-11-12 15:55 ` [Xen-devel] " Jan Beulich
2014-11-12 16:59 ` David Vrabel
2014-11-12 17:18 ` Jan Beulich
2014-11-13 9:57 ` Jan Beulich
2014-11-13 10:38 ` Andrew Cooper
2014-11-13 10:53 ` Jan Beulich
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=546495280200007800047203@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®