From: david.vrabel@citrix.com (David Vrabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] [PATCH v7 7/8] xen/arm/arm64: introduce xen_arch_need_swiotlb
Date: Mon, 3 Nov 2014 11:01:49 +0000 [thread overview]
Message-ID: <5457609D.2000200@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1411031044480.22875@kaball.uk.xensource.com>
On 03/11/14 10:45, Stefano Stabellini wrote:
> On Mon, 27 Oct 2014, Stefano Stabellini wrote:
>> Introduce an arch specific function to find out whether a particular dma
>> mapping operation needs to bounce on the swiotlb buffer.
>>
>> On ARM and ARM64, if the page involved is a foreign page and the device
>> is not coherent, we need to bounce because at unmap time we cannot
>> execute any required cache maintenance operations (we don't know how to
>> find the pfn from the mfn).
>>
>> No change of behaviour for x86.
>>
>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>
> Konrad, David, are you OK with the swiotlb-xen changes?
Reviewed-by: David Vrabel <david.vrabel@citrix.com>
But swiotlb is Konrad's responsibility.
David
next prev parent reply other threads:[~2014-11-03 11:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 15:08 [PATCH v7 0/8] introduce GNTTABOP_cache_flush Stefano Stabellini
2014-10-27 15:09 ` [PATCH v7 1/8] xen/arm: remove handling of XENFEAT_grant_map_identity Stefano Stabellini
2014-10-27 15:09 ` [PATCH v7 2/8] xen/arm: remove outer_*_range call Stefano Stabellini
2014-10-27 15:09 ` [PATCH v7 3/8] arm64: introduce is_device_dma_coherent Stefano Stabellini
2014-11-03 10:46 ` Stefano Stabellini
2014-11-03 10:57 ` Will Deacon
2014-11-03 11:10 ` Stefano Stabellini
2014-11-04 11:35 ` Grygorii Strashko
2014-11-04 15:00 ` Stefano Stabellini
2014-11-05 16:56 ` Catalin Marinas
2014-11-05 18:15 ` Stefano Stabellini
2014-11-06 10:33 ` Catalin Marinas
2014-11-06 12:22 ` Stefano Stabellini
2014-11-06 13:40 ` Catalin Marinas
2014-11-07 11:05 ` Catalin Marinas
2014-11-07 11:11 ` Catalin Marinas
2014-11-07 14:10 ` Stefano Stabellini
2014-11-07 14:10 ` Stefano Stabellini
2014-11-07 16:00 ` Catalin Marinas
2014-11-07 17:24 ` Stefano Stabellini
2014-11-07 17:35 ` Stefano Stabellini
2014-11-07 18:14 ` Catalin Marinas
2014-11-07 18:45 ` Stefano Stabellini
2014-11-10 10:16 ` Catalin Marinas
2014-11-10 12:35 ` Stefano Stabellini
2014-11-10 12:41 ` Stefano Stabellini
2014-10-27 15:09 ` [PATCH v7 4/8] arm: " Stefano Stabellini
2014-11-03 10:55 ` Stefano Stabellini
2014-10-27 15:09 ` [PATCH v7 5/8] xen/arm: use is_device_dma_coherent Stefano Stabellini
2014-10-27 15:09 ` [PATCH v7 6/8] xen/arm/arm64: merge xen/mm32.c into xen/mm.c Stefano Stabellini
2014-11-07 14:22 ` Catalin Marinas
2014-11-07 15:28 ` Stefano Stabellini
2014-11-07 16:03 ` Catalin Marinas
2014-11-07 16:46 ` Stefano Stabellini
2014-10-27 15:09 ` [PATCH v7 7/8] xen/arm/arm64: introduce xen_arch_need_swiotlb Stefano Stabellini
2014-11-03 10:45 ` Stefano Stabellini
2014-11-03 11:01 ` David Vrabel [this message]
2014-11-03 16:04 ` Konrad Rzeszutek Wilk
2014-10-27 15:09 ` [PATCH v7 8/8] xen/arm: introduce GNTTABOP_cache_flush Stefano Stabellini
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=5457609D.2000200@citrix.com \
--to=david.vrabel@citrix.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).