From: David Vrabel <david.vrabel@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xensource.com
Cc: julien.grall@citrix.com, Ian.Campbell@citrix.com
Subject: Re: [PATCH v2 3/4] xen/arm: introduce GNTTABOP_cache_flush
Date: Mon, 6 Oct 2014 16:21:38 +0100 [thread overview]
Message-ID: <5432B382.3040000@citrix.com> (raw)
In-Reply-To: <1412347845-27755-3-git-send-email-stefano.stabellini@eu.citrix.com>
On 03/10/14 15:50, Stefano Stabellini wrote:
> Introduce a new hypercall to perform cache maintenance operation on
> behalf of the guest. The argument is a machine address and a size. The
> implementation checks that the memory range is owned by the guest or the
> guest has been granted access to it by another domain.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
[...]
> --- a/xen/common/grant_table.c
> +++ b/xen/common/grant_table.c
> @@ -2641,6 +2641,79 @@ do_grant_table_op(
[...]
> +
> + page = mfn_to_page(mfn);
> + owner = page_get_owner_and_reference(page);
> + if ( !owner )
> + {
> + rcu_unlock_domain(d);
> + return -EFAULT;
> + }
> +
> + spin_lock(&owner->grant_table->lock);
The grant table lock is already heavily contended, so you should skip
the lock and the grant_map_exists() check if d == owner.
> +
> + if ( !grant_map_exists(d, owner->grant_table, mfn) )
Looping over all grant table entries or all maptrack entries looks
expensive to me.
Perhaps consider allowing suitably privileged domains to
clean/invalidate any address without having to check if it's been granted.
Instead of this hypercall, could the guest clean/invalidate by set/way?
I guess this would need a suitable IPA which could be obtained by some
(offset) 1:1 mapping in the stage 2 tables?
David
next prev parent reply other threads:[~2014-10-06 15:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 14:47 [PATCH v2 0/4] xen/arm: introduce GNTTABOP_cache_flush Stefano Stabellini
2014-10-03 14:50 ` [PATCH v2 1/4] xen/arm: introduce invalidate_xen_dcache_va_range Stefano Stabellini
2014-10-03 14:50 ` [PATCH v2 2/4] xen: introduce grant_map_exists Stefano Stabellini
2014-10-03 15:02 ` Andrew Cooper
2014-10-03 16:20 ` Stefano Stabellini
2014-10-06 8:22 ` Jan Beulich
2014-10-06 9:37 ` Stefano Stabellini
2014-10-06 10:20 ` Jan Beulich
2014-10-06 13:08 ` Stefano Stabellini
2014-10-06 13:39 ` Jan Beulich
2014-10-06 13:46 ` Stefano Stabellini
2014-10-06 14:01 ` Jan Beulich
2014-10-06 14:34 ` Stefano Stabellini
2014-10-06 14:56 ` Jan Beulich
2014-10-06 14:57 ` Stefano Stabellini
2014-10-06 15:09 ` Jan Beulich
2014-10-06 9:41 ` Stefano Stabellini
2014-10-06 10:17 ` Jan Beulich
2014-10-03 14:50 ` [PATCH v2 3/4] xen/arm: introduce GNTTABOP_cache_flush Stefano Stabellini
2014-10-03 14:53 ` Stefano Stabellini
2014-10-03 15:16 ` Andrew Cooper
2014-10-03 16:33 ` Stefano Stabellini
2014-10-03 16:37 ` Andrew Cooper
2014-10-03 16:37 ` Ian Campbell
2014-10-06 8:49 ` Jan Beulich
2014-10-06 9:00 ` Jan Beulich
2014-10-06 15:21 ` David Vrabel [this message]
2014-10-08 11:54 ` Stefano Stabellini
2014-10-08 12:06 ` David Vrabel
2014-10-08 12:52 ` Stefano Stabellini
2014-10-08 13:01 ` Ian Campbell
2014-10-08 12:17 ` Ian Campbell
2014-10-08 12:45 ` David Vrabel
2014-10-03 14:50 ` [PATCH v2 4/4] Revert "xen/arm: introduce XENFEAT_grant_map_identity" 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=5432B382.3040000@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.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.