xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 10/18 V2]: PVH xen: introduce vmx_pvh.c and pvh.c
Date: Mon, 1 Apr 2013 17:08:24 -0700	[thread overview]
Message-ID: <20130401170824.4dd25565@mantra.us.oracle.com> (raw)
In-Reply-To: <514713C202000078000C657D@nat28.tlf.novell.com>

On Mon, 18 Mar 2013 12:16:50 +0000
"Jan Beulich" <JBeulich@suse.com> wrote:

> >>> On 16.03.13 at 01:41, Mukesh Rathor <mukesh.rathor@oracle.com>
> >>> wrote:
> > +static int pvh_grant_table_op(
> > +              unsigned int cmd, XEN_GUEST_HANDLE(void) uop,
> > unsigned int count) +{
> > +    switch (cmd)
> > +    {
> > +        case GNTTABOP_map_grant_ref:
> > +        case GNTTABOP_unmap_grant_ref:
> > +        case GNTTABOP_setup_table:
> > +        case GNTTABOP_copy:
> > +        case GNTTABOP_query_size:
> > +        case GNTTABOP_set_version:
> > +            return do_grant_table_op(cmd, uop, count);
> 
> While for HVM guests such white lists may be appropriate, for PVH
> this doesn't seem to be the case: The code would require updating
> whenever a new sub-hypercall gets added to any of the hypercalls
> dealt with like this.

Right, these are verified for PVH. As they are added, they would need
to be verfied to make sure OK for PVH. We can remove this later. I can
ifdef DEBUG if you'd like.

  reply	other threads:[~2013-04-02  0:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16  0:41 [PATCH 10/18 V2]: PVH xen: introduce vmx_pvh.c and pvh.c Mukesh Rathor
2013-03-18 12:16 ` Jan Beulich
2013-04-02  0:08   ` Mukesh Rathor [this message]
2013-04-02  7:00     ` Jan Beulich
2013-03-18 16:32 ` Konrad Rzeszutek Wilk
2013-04-02  1:26   ` Mukesh Rathor
2013-04-02 14:10     ` Konrad Rzeszutek Wilk
2013-04-03  1:29       ` Mukesh Rathor
2013-04-03 14:40         ` Konrad Rzeszutek Wilk
2013-04-03  1:45       ` Mukesh Rathor
2013-04-03  1:42   ` Mukesh Rathor
2013-04-04  1:01   ` Mukesh Rathor
2013-04-04  8:23     ` Jan Beulich
2013-03-21 16:49 ` Tim Deegan
2013-03-22  8:32   ` Jan Beulich
2013-03-22 10:06     ` Tim Deegan
2013-04-03  1:37   ` Mukesh Rathor
2013-04-03  8:06     ` Jan Beulich
2013-04-03 23:38       ` Mukesh Rathor
2013-04-04  9:12     ` Tim Deegan
2013-04-04 23:00       ` Mukesh Rathor

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=20130401170824.4dd25565@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=JBeulich@suse.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 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).