From: david.vrabel@citrix.com (David Vrabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] xen/arm: introduce GNTTABOP_cache_flush
Date: Fri, 3 Oct 2014 16:05:14 +0100 [thread overview]
Message-ID: <542EBB2A.6030104@citrix.com> (raw)
In-Reply-To: <1412348006-27884-2-git-send-email-stefano.stabellini@eu.citrix.com>
On 03/10/14 15:53, Stefano Stabellini wrote:
> Introduce support for new hypercall GNTTABOP_cache_flush.
> Use it to perform cache flashing on pages used for dma when necessary.
[..]
> /* functions called by SWIOTLB */
> @@ -22,16 +25,31 @@ static void dma_cache_maint(dma_addr_t handle, unsigned long offset,
> size_t len = left;
> void *vaddr;
>
> + if (len + offset > PAGE_SIZE)
> + len = PAGE_SIZE - offset;
> +
> if (!pfn_valid(pfn))
> {
> - /* TODO: cache flush */
> + struct gnttab_cache_flush cflush;
> +
> + cflush.op = 0;
> + cflush.a.dev_bus_addr = pfn << PAGE_SHIFT;
> + cflush.offset = offset;
> + cflush.size = len;
> +
> + if (op == dmac_unmap_area && dir != DMA_TO_DEVICE)
> + cflush.op = GNTTAB_CACHE_INVAL;
> + if (op == dmac_map_area) {
> + cflush.op = GNTTAB_CACHE_CLEAN;
> + if (dir == DMA_FROM_DEVICE)
> + cflush.op |= GNTTAB_CACHE_INVAL;
> + }
Are all these cache operations needed? You do a clean on map regardless
of the direction and INVAL on map seems unnecessary.
I would have thought it would be:
map && (TO_DEVICE || BOTH)
op = CLEAN
unmap && (FROM_DEVICE || BOTH)
op = INVAL
> --- a/include/xen/interface/grant_table.h
> +++ b/include/xen/interface/grant_table.h
> @@ -479,6 +479,24 @@ struct gnttab_get_version {
> DEFINE_GUEST_HANDLE_STRUCT(gnttab_get_version);
>
> /*
> + * Issue one or more cache maintenance operations on a portion of a
> + * page granted to the calling domain by a foreign domain.
> + */
> +#define GNTTABOP_cache_flush 12
> +struct gnttab_cache_flush {
> + union {
> + uint64_t dev_bus_addr;
> + grant_ref_t ref;
> + } a;
> + uint32_t offset; /* offset from start of grant */
> + uint32_t size; /* size within the grant */
> +#define GNTTAB_CACHE_CLEAN (1<<0)
> +#define GNTTAB_CACHE_INVAL (1<<1)
> + uint32_t op;
> +};
> +DEFINE_GUEST_HANDLE_STRUCT(gnttab_cache_flush);
> +
> +/*
> * Bitfield values for update_pin_status.flags.
> */
> /* Map the grant entry for access by I/O devices. */
If the ARM bits are correct, have a
Reviewed-by: David Vrabel <david.vrabel@citrix.com>
for the common header.
David
next prev parent reply other threads:[~2014-10-03 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 14:52 [PATCH v2 0/2] introduce XENMEM_cache_flush Stefano Stabellini
2014-10-03 14:53 ` [PATCH v2 1/2] xen/arm: remove handling of XENFEAT_grant_map_identity Stefano Stabellini
2014-10-03 14:53 ` [PATCH v2 2/2] xen/arm: introduce GNTTABOP_cache_flush Stefano Stabellini
2014-10-03 15:05 ` David Vrabel [this message]
2014-10-03 16:20 ` Stefano Stabellini
2014-10-03 16:34 ` Ian Campbell
2014-10-03 16:36 ` David Vrabel
2014-10-03 16:57 ` Russell King - ARM Linux
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=542EBB2A.6030104@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).