From: Adrian Pop <apop@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Tamas K Lengyel <tamas@tklengyel.com>,
Sergej Proskurin <proskurin@sec.in.tum.de>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v4 3/3] x86/altp2m: Add a hvmop for querying the suppress #VE bit
Date: Mon, 27 Aug 2018 12:38:52 +0300 [thread overview]
Message-ID: <20180827093852.GB1307@hel> (raw)
In-Reply-To: <5B604B8302000078001D9692@prv1-mh.provo.novell.com>
On Tue, Jul 31, 2018 at 05:44:03AM -0600, Jan Beulich wrote:
> >>> On 25.07.18 at 13:18, <apop@bitdefender.com> wrote:
> > --- a/xen/include/public/hvm/hvm_op.h
> > +++ b/xen/include/public/hvm/hvm_op.h
> > @@ -38,7 +38,7 @@ struct xen_hvm_param {
> > typedef struct xen_hvm_param xen_hvm_param_t;
> > DEFINE_XEN_GUEST_HANDLE(xen_hvm_param_t);
> >
> > -struct xen_hvm_altp2m_set_suppress_ve {
> > +struct xen_hvm_altp2m_suppress_ve {
>
> Please add this without the "set_" right away in patch 2.
Sure. Thanks!
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-08-27 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 11:18 [PATCH v4 0/3] Add hvmops for setting and getting the suppress #VE bit Adrian Pop
2018-07-25 11:18 ` [PATCH v4 1/3] x86/mm: Change default value for suppress #VE in set_mem_access() Adrian Pop
2018-07-25 11:18 ` [PATCH v4 2/3] x86/altp2m: Add a hvmop for setting the suppress #VE bit Adrian Pop
2018-07-25 11:18 ` [PATCH v4 3/3] x86/altp2m: Add a hvmop for querying " Adrian Pop
2018-07-31 11:44 ` Jan Beulich
2018-08-27 9:38 ` Adrian Pop [this message]
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=20180827093852.GB1307@hel \
--to=apop@bitdefender.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien.grall@arm.com \
--cc=proskurin@sec.in.tum.de \
--cc=rcojocaru@bitdefender.com \
--cc=sstabellini@kernel.org \
--cc=tamas@tklengyel.com \
--cc=tim@xen.org \
--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).