All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Borislav Petkov <bp@alien8.de>,
	Andy Lutomirski <luto@amacapital.net>
Subject: Re: HVMlite gains
Date: Tue, 15 Mar 2016 18:39:40 -0400	[thread overview]
Message-ID: <20160315223940.GC29183@char.us.oracle.com> (raw)
In-Reply-To: <CAB=NE6XzPXvUYBuq_aFs2C94e9sd6wM=6a2pkxH4RAGmbDedWw@mail.gmail.com>

On Tue, Mar 15, 2016 at 02:14:15PM -0700, Luis R. Rodriguez wrote:
> While discussing HVMLite with a few people a few questions have come
> up. Since I only really understand a few possible gains with the
> current design I wanted to get clarificaiton on a few which I simply

Just think of baremetal without BIOS. Without PCI support (unless
needed).

> have no clue if we stand to gain from them, or if its on the roadmap:
> 
>   a) Will context switches use the actual CR3 register?

Yes.
>   b) Will IOPL live in the actual FLAGS register?

Yes.
>   c) Will guest-usable CPU features should show up in CPUID, and will
> features that shouldn't be used should *not* show up in CPUID. For

Correct.
> instance currently you happen to boot Xen 4.4.0 with a new Linux dom0
> on a CPU that supports MPX what will happen? What about with HVMlite?

It should boot just normally. Either PV dom0 guest or HVMLite dom0
guest (whenever that is operational).


>   d)  Will acking an interrupt use the standard APIC mechanism?  Do
> any of the current Xen variants do that?

Yes and no. It is disabled right now but it will be enabled as I want
to make sure we can use vAPIC in the guest.

You don't want to use emulated APIC mechanism as it incurs VMEXITs.

>   e) Can timing use RDTSC?

Yes (odd question? You could always use rdtsc). 
> 
>  Luis

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      parent reply	other threads:[~2016-03-15 22:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 21:14 HVMlite gains Luis R. Rodriguez
2016-03-15 21:29 ` Andrew Cooper
2016-03-15 21:36   ` Andy Lutomirski
2016-03-15 21:50     ` Boris Ostrovsky
2016-03-15 21:50     ` Andrew Cooper
2016-03-15 21:52       ` Andy Lutomirski
2016-03-15 22:05         ` Andrew Cooper
2016-03-16  3:18           ` Andy Lutomirski
2016-03-16 10:46             ` Andrew Cooper
2016-03-15 22:39 ` Konrad Rzeszutek Wilk [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=20160315223940.GC29183@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=luto@amacapital.net \
    --cc=matt@codeblueprint.co.uk \
    --cc=mcgrof@kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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.