From: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>, Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>
Subject: Re: [PATCH v4 02/12] x86/mm: add HYPERVISOR_memory_op to acquire guest resources
Date: Thu, 7 Sep 2017 11:37:43 +0000 [thread overview]
Message-ID: <6ef2650d78b64f47864e9db441b9b2db@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <20170907113629.lsyvh57mpfuzqsq6@citrix.com>
> -----Original Message-----
> From: Wei Liu [mailto:wei.liu2@citrix.com]
> Sent: 07 September 2017 12:36
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Wei Liu <wei.liu2@citrix.com>; xen-devel@lists.xenproject.org; Andrew
> Cooper <Andrew.Cooper3@citrix.com>; Jan Beulich <jbeulich@suse.com>
> Subject: Re: [Xen-devel] [PATCH v4 02/12] x86/mm: add
> HYPERVISOR_memory_op to acquire guest resources
>
> On Thu, Sep 07, 2017 at 12:18:25PM +0100, Paul Durrant wrote:
> > > -----Original Message-----
> > > From: Wei Liu [mailto:wei.liu2@citrix.com]
> > > Sent: 07 September 2017 12:11
> > > To: Paul Durrant <Paul.Durrant@citrix.com>
> > > Cc: xen-devel@lists.xenproject.org; Andrew Cooper
> > > <Andrew.Cooper3@citrix.com>; Jan Beulich <jbeulich@suse.com>; Wei
> Liu
> > > <wei.liu2@citrix.com>
> > > Subject: Re: [Xen-devel] [PATCH v4 02/12] x86/mm: add
> > > HYPERVISOR_memory_op to acquire guest resources
> > >
> > > On Tue, Sep 05, 2017 at 12:37:06PM +0100, Paul Durrant wrote:
> > > [...]
> > > >
> > > > +static int xenmem_acquire_grant_table(struct domain *d,
> > > > + unsigned long frame,
> > > > + unsigned long nr_frames,
> > > > + unsigned long mfn_list[])
> > > > +{
> > > > + unsigned int i;
> > > > +
> > > > + /*
> > > > + * Iterate through the list backwards so that gnttab_get_frame() is
> > > > + * first called for the highest numbered frame. This means that the
> > > > + * out-of-bounds check will be done on the first iteration and, if
> > > > + * the table needs to grow, it will only grow once.
> > > > + */
> > > > + i = nr_frames;
> > > > + while ( i-- != 0 )
> > > > + {
> > > > + mfn_t mfn = gnttab_get_frame(d, frame + i);
> > > > +
> > >
> > > I think you should lock guest grant table first and use the _locked
> > > variant here to get a consistent view of guest grant table frames.
> >
> > Once the table has grown, is there any way they can change?
> >
>
> Hmm... no.
>
> I think you can leave the code as-is.
>
> >
> > Ok, if you think it's necessary. (This is a tools-only hypercall and the ranges
> are supplied by privcmd, allocated in kernel).
> >
>
> IMHO we should allow for use case for semi-trusted users of this
> hypercall in the future.
Ok, I'll send a v5.
Cheers,
Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-09-07 11:37 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 11:37 [PATCH v4 00/12] x86: guest resource mapping Paul Durrant
2017-09-05 11:37 ` [PATCH v4 01/12] x86/mm: allow a privileged PV domain to map guest mfns Paul Durrant
2017-09-07 11:02 ` Wei Liu
2017-09-07 11:05 ` Paul Durrant
2017-09-07 11:09 ` Wei Liu
2017-09-07 11:19 ` Andrew Cooper
2017-09-05 11:37 ` [PATCH v4 02/12] x86/mm: add HYPERVISOR_memory_op to acquire guest resources Paul Durrant
2017-09-07 11:10 ` Wei Liu
2017-09-07 11:18 ` Paul Durrant
2017-09-07 11:36 ` Wei Liu
2017-09-07 11:37 ` Paul Durrant [this message]
2017-09-07 11:54 ` Jan Beulich
2017-09-05 11:37 ` [PATCH v4 03/12] tools/libxenforeignmemory: add support for resource mapping Paul Durrant
2017-09-07 11:48 ` Wei Liu
2017-09-05 11:37 ` [PATCH v4 04/12] tools/libxenforeignmemory: reduce xenforeignmemory_restrict code footprint Paul Durrant
2017-09-07 11:48 ` Wei Liu
2017-09-05 11:37 ` [PATCH v4 05/12] tools/libxenctrl: use new xenforeignmemory API to seed grant table Paul Durrant
2017-09-07 11:49 ` Wei Liu
2017-09-05 11:37 ` [PATCH v4 06/12] x86/hvm/ioreq: rename .*pfn and .*gmfn to .*gfn Paul Durrant
2017-09-05 11:37 ` [PATCH v4 07/12] x86/hvm/ioreq: use bool rather than bool_t Paul Durrant
2017-09-07 11:10 ` Wei Liu
2017-09-05 11:37 ` [PATCH v4 08/12] x86/hvm/ioreq: maintain an array of ioreq servers rather than a list Paul Durrant
2017-09-07 11:40 ` Wei Liu
2017-09-07 14:41 ` Roger Pau Monné
2017-09-07 14:51 ` Juergen Gross
2017-09-07 14:57 ` Roger Pau Monné
2017-09-07 15:16 ` Jan Beulich
2017-09-08 8:32 ` Paul Durrant
2017-09-05 11:37 ` [PATCH v4 09/12] x86/hvm/ioreq: simplify code and use consistent naming Paul Durrant
2017-09-07 11:45 ` Wei Liu
2017-09-05 11:37 ` [PATCH v4 10/12] x86/hvm/ioreq: use gfn_t in struct hvm_ioreq_page Paul Durrant
2017-09-07 11:45 ` Wei Liu
2017-09-05 11:37 ` [PATCH v4 11/12] x86/hvm/ioreq: defer mapping gfns until they are actually requsted Paul Durrant
2017-09-07 12:00 ` Wei Liu
2017-09-07 12:03 ` Paul Durrant
2017-09-07 12:16 ` Wei Liu
2017-09-07 12:29 ` Paul Durrant
2017-09-07 14:22 ` Wei Liu
2017-09-08 8:34 ` Paul Durrant
2017-09-05 11:37 ` [PATCH v4 12/12] x86/hvm/ioreq: add a new mappable resource type Paul Durrant
2017-09-07 14:51 ` Wei Liu
2017-09-08 8:28 ` Paul Durrant
2017-09-07 14:56 ` Roger Pau Monné
2017-09-07 14:59 ` Wei Liu
2017-09-07 15:23 ` Roger Pau Monné
2017-09-08 8:29 ` Paul Durrant
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=6ef2650d78b64f47864e9db441b9b2db@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).