xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	jbeulich@suse.com, keir@xen.org
Cc: roger.pau@citrix.com, david.vrabel@citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH] x86/hvm: Provide list of emulated features in HVM CPUID leaf
Date: Tue, 2 Feb 2016 23:22:23 +0000	[thread overview]
Message-ID: <56B13A2F.3070209@citrix.com> (raw)
In-Reply-To: <1454455041-4647-1-git-send-email-boris.ostrovsky@oracle.com>

On 02/02/2016 23:17, Boris Ostrovsky wrote:
> Hypervisor may choose which features to emulate for HVMlite guests.
> Guest will query the HVM CPUID leaf to find out what is available.
>
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

Roger also submitted a patch to do this.  However, it is not
appropriate, so was dropped.

An HVMLite domain should assume there are no emulated devices.  The very
old legacy devices will never be implemented, and any others we care
about possibly implementing in the future have APCI-based ways of
indicating support.

~Andrew

  reply	other threads:[~2016-02-02 23:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 23:17 [PATCH] x86/hvm: Provide list of emulated features in HVM CPUID leaf Boris Ostrovsky
2016-02-02 23:22 ` Andrew Cooper [this message]
2016-02-02 23:30   ` Boris Ostrovsky
2016-02-03  0:17     ` Andrew Cooper
2016-02-03  8:43       ` Roger Pau Monné
2016-02-03 14:30         ` Boris Ostrovsky
2016-02-03 14:37           ` Andrew Cooper
2016-02-03 14:46             ` Boris Ostrovsky
2016-02-03 15:05           ` Roger Pau Monné
2016-02-03 15:27             ` Boris Ostrovsky
2016-02-03  3:51 ` Tian, Kevin

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=56B13A2F.3070209@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=roger.pau@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).