From: Petre Ovidiu PIRCALABU <ppircalabu@bitdefender.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "sstabellini@kernel.org" <sstabellini@kernel.org>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"rcojocaru@bitdefender.com" <rcojocaru@bitdefender.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"George.Dunlap@eu.citrix.com" <George.Dunlap@eu.citrix.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
"tim@xen.org" <tim@xen.org>,
"jbeulich@suse.com" <jbeulich@suse.com>
Subject: Re: [PATCH v8] x86/altp2m: support for setting restrictions for an array of pages
Date: Mon, 20 Nov 2017 09:35:03 +0000 [thread overview]
Message-ID: <1511170502.2901.3.camel@bitdefender.com> (raw)
In-Reply-To: <1508840345-18126-1-git-send-email-ppircalabu@bitdefender.com>
On Ma, 2017-10-24 at 13:19 +0300, Petre Pircalabu wrote:
> From: Razvan Cojocaru <rcojocaru@bitdefender.com>
>
> For the default EPT view we have xc_set_mem_access_multi(), which
> is able to set an array of pages to an array of access rights with
> a single hypercall. However, this functionality was lacking for the
> altp2m subsystem, which could only set page restrictions for one
> page at a time. This patch addresses the gap.
>
> HVMOP_altp2m_set_mem_access_multi has been added as a HVMOP (as
> opposed to a
> DOMCTL) for consistency with its HVMOP_altp2m_set_mem_access
> counterpart (and
> hence with the original altp2m design, where domains are allowed -
> with the
> proper altp2m access rights - to alter these settings), in the
> absence of an
> official position on the issue from the original altp2m designers.
>
> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
> Signed-off-by: Petre Pircalabu <ppircalabu@bitdefender.com>
>
Hello,
Are there still any outstanding issues with this patch?
Many thanks,
Petre
________________________
This email was scanned by Bitdefender
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-11-20 9:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 10:19 [PATCH v8] x86/altp2m: support for setting restrictions for an array of pages Petre Pircalabu
2017-11-20 9:35 ` Petre Ovidiu PIRCALABU [this message]
2017-11-20 11:39 ` Jan Beulich
2017-12-08 12:18 ` Jan Beulich
2017-12-08 12:42 ` Razvan Cojocaru
2017-12-08 16:56 ` Tamas K Lengyel
2017-12-11 9:14 ` Jan Beulich
2017-12-11 11:06 ` Andrew Cooper
2017-12-11 12:12 ` Jan Beulich
2017-12-11 12:50 ` George Dunlap
2017-12-11 13:36 ` Jan Beulich
2017-12-11 14:46 ` Razvan Cojocaru
2017-12-11 14:51 ` George Dunlap
2017-12-11 14:55 ` George Dunlap
2017-12-11 15:05 ` Jan Beulich
2017-12-11 15:54 ` George Dunlap
2017-12-11 15:58 ` Razvan Cojocaru
2017-12-11 16:24 ` Jan Beulich
2017-12-11 16:00 ` Tamas K Lengyel
2017-12-11 16:07 ` Razvan Cojocaru
2017-12-11 15:03 ` Jan Beulich
2017-12-11 14:50 ` George Dunlap
2017-12-11 14:58 ` Jan Beulich
2017-12-11 15:38 ` George Dunlap
2017-12-11 16:18 ` George Dunlap
2017-12-11 16:22 ` George Dunlap
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=1511170502.2901.3.camel@bitdefender.com \
--to=ppircalabu@bitdefender.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=rcojocaru@bitdefender.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.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.