From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>,
Jan Beulich <JBeulich@suse.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Getting the XSAVE size from userspace
Date: Thu, 5 Nov 2015 10:53:38 +0000 [thread overview]
Message-ID: <563B3532.2000903@citrix.com> (raw)
In-Reply-To: <563B33AC.8000106@bitdefender.com>
On 05/11/15 10:47, Razvan Cojocaru wrote:
> On 11/05/2015 12:42 PM, Jan Beulich wrote:
>>>>> On 05.11.15 at 10:52, <rcojocaru@bitdefender.com> wrote:
>>> I need to get the XSAVE size from userspace. The easiest way seems to be
>>> to use the XEN_DOMCTL_getvcpuextstate hypercall, but that hypercall is
>>> not public / there's no xenctrl.h wrapper for it.
>> Before going into any detail of the rest of your mail - any reason you
>> can't just consult CPUID output?
> That's because the userspace application doesn't live in dom0, but in a
> dedicated privileged domain, and I'm unsure if a CPUID issued there
> yields the same results as a CPUID issued in dom0. So I thought the
> safest way is to get the information directly from the hypervisor. Is
> this assumption incorrect?
What purpose are you wanting the information for?
Using cpuid (should) get you the information concerning your domain,
which is liable to be different to what another domain might see.
Currently, the information available through the domain cpuid policy is
inaccurate, and *not* migration safe. I am working on fixing this as
part 2 of my cpuid levelling fixes.
~Andrew
next prev parent reply other threads:[~2015-11-05 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 9:52 Getting the XSAVE size from userspace Razvan Cojocaru
2015-11-05 10:42 ` Jan Beulich
2015-11-05 10:47 ` Razvan Cojocaru
2015-11-05 10:52 ` Jan Beulich
2015-11-05 10:53 ` Andrew Cooper [this message]
2015-11-05 10:49 ` Andrew Cooper
2015-11-05 10:51 ` Jan Beulich
2015-11-05 11:35 ` Andrei LUTAS
2015-11-05 11:44 ` Andrew Cooper
2015-11-05 12:26 ` Razvan Cojocaru
2015-11-05 14:05 ` Andrew Cooper
2015-11-05 14:13 ` 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=563B3532.2000903@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=rcojocaru@bitdefender.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.