From: Wei Liu <wei.liu2@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: "Juergen Gross" <jgross@suse.com>,
"Wei Liu" <wei.liu2@citrix.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Ian Jackson" <Ian.Jackson@eu.citrix.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
Xen-devel <xen-devel@lists.xen.org>,
"Jim Fehlig" <jfehlig@suse.com>,
"Christian Lindig" <christian.lindig@citrix.com>,
"David Scott" <dave@recoil.org>
Subject: Re: [PATCH RFC] tools: Drop xc_cpuid_check() and bindings
Date: Thu, 20 Jul 2017 17:36:22 +0100 [thread overview]
Message-ID: <20170720163622.isn2bttssg2ea23x@citrix.com> (raw)
In-Reply-To: <6fbaf6e0-ef7c-4794-5771-8cde05c13c1b@oracle.com>
On Wed, Jul 19, 2017 at 08:50:07AM -0400, Boris Ostrovsky wrote:
> On 07/19/2017 06:43 AM, Juergen Gross wrote:
> > On 19/07/17 12:32, Wei Liu wrote:
> >> On Mon, Jul 17, 2017 at 01:38:03PM +0100, Andrew Cooper wrote:
> >>> There are no current users which I can locate. One piece of xend which didn't
> >>> move forwards into xl/libxl is this:
> >>>
> >>> # Configure host CPUID consistency checks, which must be satisfied for this
> >>> # VM to be allowed to run on this host's processor type:
> >>> #cpuid_check=[ '1:ecx=xxxxxxxxxxxxxxxxxxxxxxxxxx1xxxxx' ]
> >>> # - Host must have VMX feature flag set
> >>>
> >>> The implementation of xc_cpuid_check() is conceptually broken. Dom0's view of
> >>> CPUID is not the approprite view to check, and will be wrong in the presence
> >>> of CPUID masking/faulting, and for HVM-based toolstack domains.
> >>>
> >>> If it turns out that the functionality is required, it should be implemented
> >>> in terms of XEN_SYSCTL_get_cpuid_policy to use the proper CPUID view.
> >>>
> >>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> >>> ---
> >>> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
> >>> CC: Wei Liu <wei.liu2@citrix.com>
> >>> CC: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> >>> CC: David Scott <dave@recoil.org>
> >>> CC: Christian Lindig <christian.lindig@citrix.com>
> >>> CC: Juergen Gross <jgross@suse.com>
> >>> CC: Jim Fehlig <jfehlig@suse.com>
> >>> CC: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> >>> CC: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> >>>
> >>> RFC initially for feedback, and to see if anyone does expect to be using this
> >>> call. It turns out that Xapi has a library function using it, but that
> >>> function is dead so can be removed.
> >> FAOD I am still waiting for Oracle and Suse folks to express their
> >> opinions.
> > No objection from me.
> >
>
>
> Or from me.
>
In that case -- queued.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-07-20 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 12:38 [PATCH RFC] tools: Drop xc_cpuid_check() and bindings Andrew Cooper
2017-07-17 13:54 ` Christian Lindig
2017-07-18 20:56 ` Marek Marczykowski-Górecki
2017-07-19 10:32 ` Wei Liu
2017-07-19 10:43 ` Juergen Gross
2017-07-19 12:50 ` Boris Ostrovsky
2017-07-20 16:36 ` Wei Liu [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=20170720163622.isn2bttssg2ea23x@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=christian.lindig@citrix.com \
--cc=dave@recoil.org \
--cc=jfehlig@suse.com \
--cc=jgross@suse.com \
--cc=marmarek@invisiblethingslab.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).