From: George Dunlap <George.Dunlap@eu.citrix.com>
To: Petre Pircalabu <ppircalabu@bitdefender.com>
Cc: Tim Deegan <tim@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v8] x86/altp2m: support for setting restrictions for an array of pages
Date: Mon, 11 Dec 2017 16:18:40 +0000 [thread overview]
Message-ID: <CAFLBxZYDhD3CoJEnoHoequerD2b_KLoQpm-DSvcGch7QAy1jrg@mail.gmail.com> (raw)
In-Reply-To: <1508840345-18126-1-git-send-email-ppircalabu@bitdefender.com>
On Tue, Oct 24, 2017 at 11:19 AM, Petre Pircalabu
<ppircalabu@bitdefender.com> 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>
FWIW the approach looks good to me here.
You mainly need an x86 maintainer's ack and a toolstack maintainer's
ack (of which I am neither).
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2017-12-11 16:18 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
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 [this message]
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=CAFLBxZYDhD3CoJEnoHoequerD2b_KLoQpm-DSvcGch7QAy1jrg@mail.gmail.com \
--to=george.dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=ppircalabu@bitdefender.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 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).