From: Daniel De Graaf <dgdegra@tycho.nsa.gov>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Keir Fraser <keir@xen.org>,
xen-devel@lists.xen.org
Subject: Re: [PATCH RESEND 1/4] xen/xsm: add hooks for claim
Date: Fri, 03 May 2013 12:29:51 -0400 [thread overview]
Message-ID: <5183E5FF.7050004@tycho.nsa.gov> (raw)
In-Reply-To: <20130503154613.GA4249@phenom.dumpdata.com>
On 05/03/2013 11:46 AM, Konrad Rzeszutek Wilk wrote:
> On Fri, May 03, 2013 at 10:09:13AM -0400, Daniel De Graaf wrote:
>> Adds XSM hooks for the recently introduced XENMEM_claim_pages and
>> XENMEM_get_outstanding_pages operations, and adds FLASK access vectors
>> for them. This makes the access control decisions for these operations
>> match those in the rest of the hypervisor.
>
> I am not that familiar with this, but it looks OK. However I am
> going to post a patch soon that will eliminate one of the hypercalls
> (xenmem_get_outstanding_pages).
>
> Do you want to wait for this or would it be better if I posted
> the patch along with some changes to xsm hooks to delete it and
> you can Ack it?
Either way would be fine with me. I think re-posting may work better as
I just found a typo in patch 4 that will be fixed on repost.
next prev parent reply other threads:[~2013-05-03 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 14:09 [PATCH v4 0/4] Rename/remove IS_PRIV Daniel De Graaf
2013-05-03 14:09 ` [PATCH RESEND 1/4] xen/xsm: add hooks for claim Daniel De Graaf
2013-05-03 15:46 ` Konrad Rzeszutek Wilk
2013-05-03 16:29 ` Daniel De Graaf [this message]
2013-05-03 16:00 ` Keir Fraser
2013-05-03 14:09 ` [PATCH RESEND 2/4] xen/arm: remove rcu_lock_target_domain_by_id users Daniel De Graaf
2013-05-03 14:26 ` Ian Campbell
2013-05-03 14:09 ` [PATCH RESEND 3/4] xen/common: remove rcu_lock_target_domain_by_id Daniel De Graaf
2013-05-03 16:00 ` Keir Fraser
2013-05-03 14:09 ` [PATCH RESEND 4/4] xen: rename IS_PRIV to is_hardware_domain Daniel De Graaf
2013-05-03 16:00 ` Keir Fraser
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=5183E5FF.7050004@tycho.nsa.gov \
--to=dgdegra@tycho.nsa.gov \
--cc=dan.magenheimer@oracle.com \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.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 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.