From: Ian Campbell <Ian.Campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: julien.grall@citrix.com, xen-devel@lists.xensource.com,
JBeulich@suse.com
Subject: Re: [PATCH v8 6/8] xen/arm: introduce GNTTABOP_cache_flush
Date: Mon, 20 Oct 2014 16:24:28 +0100 [thread overview]
Message-ID: <1413818668.29506.7.camel@citrix.com> (raw)
In-Reply-To: <1413798499-28314-6-git-send-email-stefano.stabellini@eu.citrix.com>
On Mon, 2014-10-20 at 10:48 +0100, Stefano Stabellini wrote:
>
> @@ -574,6 +576,25 @@ struct gnttab_swap_grant_ref {
> typedef struct gnttab_swap_grant_ref gnttab_swap_grant_ref_t;
> DEFINE_XEN_GUEST_HANDLE(gnttab_swap_grant_ref_t);
>
> +/*
> + * Issue one or more cache maintenance operations on a portion of a
> + * page granted to the calling domain by a foreign domain.
> + */
> +struct gnttab_cache_flush {
> + union {
> + uint64_t dev_bus_addr;
> + grant_ref_t ref;
> + } a;
> + uint16_t offset; /* offset from start of grant */
> + uint16_t length; /* size within the grant */
So are these not valid when used with dev_bus_addr? I can see that being
the case for offset, but length too?
> +#define GNTTAB_CACHE_CLEAN (1<<0)
> +#define GNTTAB_CACHE_INVAL (1<<1)
> +#define GNTTAB_CACHE_SOURCE_GREF (1<<31)
> + uint32_t op;
> +};
> +typedef struct gnttab_cache_flush gnttab_cache_flush_t;
> +DEFINE_XEN_GUEST_HANDLE(gnttab_cache_flush_t);
> +
> #endif /* __XEN_INTERFACE_VERSION__ */
>
> /*
next prev parent reply other threads:[~2014-10-20 15:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 9:47 [PATCH v8 0/8] xen/arm: introduce GNTTABOP_cache_flush Stefano Stabellini
2014-10-20 9:48 ` [PATCH v8 1/8] xen: introduce gnttab_max_frames and gnttab_max_maptrack_frames command line options Stefano Stabellini
2014-10-20 10:34 ` Jan Beulich
2014-10-20 9:48 ` [PATCH v8 2/8] xen/arm: rename *_xen_dcache_* operations to *_dcache_* Stefano Stabellini
2014-10-20 14:55 ` Ian Campbell
2014-10-20 9:48 ` [PATCH v8 3/8] xen/arm: return int *_dcache_va_range Stefano Stabellini
2014-10-20 14:57 ` Ian Campbell
2014-10-20 15:23 ` Jan Beulich
2014-10-20 15:27 ` Ian Campbell
2014-10-20 16:34 ` Stefano Stabellini
2014-10-21 9:07 ` Ian Campbell
2014-10-20 9:48 ` [PATCH v8 4/8] xen/arm: introduce invalidate_dcache_va_range Stefano Stabellini
2014-10-20 9:48 ` [PATCH v8 5/8] xen/x86: introduce more cache maintenance operations Stefano Stabellini
2014-10-20 9:48 ` [PATCH v8 6/8] xen/arm: introduce GNTTABOP_cache_flush Stefano Stabellini
2014-10-20 10:58 ` Jan Beulich
2014-10-20 15:00 ` Ian Campbell
2014-10-20 15:24 ` Ian Campbell [this message]
2014-10-20 15:30 ` Jan Beulich
2014-10-20 16:31 ` Stefano Stabellini
2014-10-21 9:04 ` Ian Campbell
2014-10-21 9:14 ` Jan Beulich
2014-10-21 9:35 ` Ian Campbell
2014-10-21 9:39 ` Stefano Stabellini
2014-10-21 14:33 ` Jan Beulich
2014-10-20 9:48 ` [PATCH v8 7/8] Revert "xen/arm: introduce XENFEAT_grant_map_identity" Stefano Stabellini
2014-10-20 15:00 ` Ian Campbell
2014-10-20 9:48 ` [PATCH v8 8/8] Revert "xen: introduce arch_grant_(un)map_page_identity" Stefano Stabellini
2014-10-20 15:01 ` Ian Campbell
2014-10-20 10:26 ` [PATCH v8 0/8] xen/arm: introduce GNTTABOP_cache_flush Jan Beulich
2014-10-20 10:36 ` Stefano Stabellini
2014-10-20 11:00 ` 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=1413818668.29506.7.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.