From: Wei Liu <wei.liu2@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: sstabellini@kernel.org, Wei Liu <wei.liu2@citrix.com>,
george.dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org,
julien.grall@arm.com, tamas@tklengyel.com,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH V4] tools/libxc, xen/x86: Added xc_set_mem_access_multi()
Date: Thu, 15 Sep 2016 14:55:02 +0100 [thread overview]
Message-ID: <20160915135502.GA9451@citrix.com> (raw)
In-Reply-To: <39fea0de-8427-899b-5886-e396a274b773@bitdefender.com>
On Thu, Sep 15, 2016 at 04:52:32PM +0300, Razvan Cojocaru wrote:
> On 09/15/2016 04:49 PM, Wei Liu wrote:
> > On Thu, Sep 15, 2016 at 04:39:47PM +0300, Razvan Cojocaru wrote:
> >> On 09/07/2016 07:01 PM, Jan Beulich wrote:
> >>>>>> On 07.09.16 at 11:12, <rcojocaru@bitdefender.com> wrote:
> >>>> Currently it is only possible to set mem_access restrictions only for
> >>>> a contiguous range of GFNs (or, as a particular case, for a single GFN).
> >>>> This patch introduces a new libxc function taking an array of GFNs.
> >>>> The alternative would be to set each page in turn, using a userspace-HV
> >>>> roundtrip for each call, and triggering a TLB flush per page set.
> >>>>
> >>>> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
> >>>> Acked-by: Wei Liu <wei.liu2@citrix.com>
> >>>
> >>> Hypervisor parts (without ARM and x86/mm)
> >>> Acked-by: Jan Beulich <jbeulich@suse.com>
> >>>
> >>> albeit I spotted one more cosmetic issue (which I guess could be
> >>> fixed up during commit, if no other reason for a v5 arises):
> >>>
> >>>> @@ -321,9 +322,22 @@ int compat_memory_op(unsigned int cmd, XEN_GUEST_HANDLE_PARAM(void) compat)
> >>>> }
> >>>>
> >>>> case XENMEM_access_op:
> >>>> - return mem_access_memop(cmd,
> >>>> - guest_handle_cast(compat,
> >>>> - xen_mem_access_op_t));
> >>>> + {
> >>>> + if ( copy_from_guest(&cmp.mao, compat, 1) )
> >>>> + return -EFAULT;
> >>>> +
> >>>> +#define XLAT_mem_access_op_HNDL_pfn_list(_d_, _s_) \
> >>>> + guest_from_compat_handle((_d_)->pfn_list, (_s_)->pfn_list)
> >>>> +#define XLAT_mem_access_op_HNDL_access_list(_d_, _s_) \
> >>>> + guest_from_compat_handle((_d_)->access_list, (_s_)->access_list)
> >>>> +
> >>>> + XLAT_mem_access_op(nat.mao, &cmp.mao);
> >>>> +
> >>>> +#undef XLAT_mem_access_op_HNDL_pfn_list
> >>>> +#undef XLAT_mem_access_op_HNDL_access_list
> >>>> +
> >>>> + break;
> >>>> + }
> >>>
> >>> There are no local variables declared here, so I don't see the need
> >>> for the braces.
> >>
> >> There have only been Acked-by replies so far, but if you'd prefer I have
> >> no problem sending a V5 removing the braces.
> >>
> >
> > Does this patch have all the necessary acks? If so I don't mind fixing
> > it up and committing it.
>
> In addition to your ack, it's:
>
> Acked-by: Jan Beulich <jbeulich@suse.com>
> Acked-by: Tamas K Lengyel <tamas@tklengyel.com>
> Acked-by: Julien Grall <julien.grall@arm.com>
>
> for the hypervisor parts (without ARM and x86/mm), vm_event and ARM
> respectively.
>
I think it still needs an ack from George for x86/mm changes.
Wei.
>
> Thanks,
> Razvan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-15 13:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 9:12 [PATCH V4] tools/libxc, xen/x86: Added xc_set_mem_access_multi() Razvan Cojocaru
2016-09-07 14:36 ` Tamas K Lengyel
2016-09-07 16:01 ` Jan Beulich
2016-09-15 13:39 ` Razvan Cojocaru
2016-09-15 13:49 ` Wei Liu
2016-09-15 13:52 ` Razvan Cojocaru
2016-09-15 13:55 ` Wei Liu [this message]
2016-09-15 13:55 ` Razvan Cojocaru
2016-09-09 16:31 ` Julien Grall
2016-09-19 15:51 ` George Dunlap
2016-09-21 12:03 ` Jan Beulich
2016-09-21 12:27 ` Razvan Cojocaru
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=20160915135502.GA9451@citrix.com \
--to=wei.liu2@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@arm.com \
--cc=rcojocaru@bitdefender.com \
--cc=sstabellini@kernel.org \
--cc=tamas@tklengyel.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.