From: "Jan Beulich" <JBeulich@suse.com>
To: Tamas K Lengyel <tamas@tklengyel.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH V2] x86/altp2m: Added xc_altp2m_set_mem_access_multi()
Date: Fri, 10 Mar 2017 00:34:45 -0700 [thread overview]
Message-ID: <58C265250200007800141E4A@prv-mh.provo.novell.com> (raw)
In-Reply-To: <CABfawh=-MgCVS2NmAJVRDBGV_agF9DnCMhWNkGuCScO7oBAjNQ@mail.gmail.com>
>>> On 09.03.17 at 18:29, <tamas@tklengyel.com> wrote:
> On Thu, Mar 9, 2017 at 9:56 AM, Jan Beulich <JBeulich@suse.com> wrote:
>> However - is this interface supposed to be usable by a guest on itself?
>> Arguably the same question would apply to some of the other sub-ops
>> too, but anyway.
>
> AFAIK the only op the guest would use on itself is
> HVMOP_altp2m_vcpu_enable_notify.
Which then means we should move all of them out of here, into a
suitable domctl. That will in turn reduce the scope of the bogus
interface versioning, which Andrew did point out, quite a bit.
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-10 7:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 9:38 [PATCH V2] x86/altp2m: Added xc_altp2m_set_mem_access_multi() Razvan Cojocaru
2017-03-09 16:56 ` Jan Beulich
2017-03-09 17:15 ` Razvan Cojocaru
2017-03-10 7:31 ` Jan Beulich
2017-03-10 8:04 ` Razvan Cojocaru
2017-03-09 17:29 ` Tamas K Lengyel
2017-03-10 7:34 ` Jan Beulich [this message]
2017-03-10 11:21 ` Andrew Cooper
2017-03-10 19:01 ` Tamas K Lengyel
2017-03-13 12:01 ` Razvan Cojocaru
2017-03-13 12:19 ` Jan Beulich
2017-03-13 12:29 ` Razvan Cojocaru
2017-03-13 12:40 ` Jan Beulich
2017-03-13 12:44 ` Razvan Cojocaru
2017-03-13 17:17 ` Tamas K Lengyel
2017-03-15 13:12 ` Razvan Cojocaru
2017-08-03 7:09 ` 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=58C265250200007800141E4A@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=rcojocaru@bitdefender.com \
--cc=tamas@tklengyel.com \
--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.