From: Paolo Bonzini <pbonzini@redhat.com>
To: Alessandro Pilotti <apilotti@cloudbasesolutions.com>
Cc: "petrutlucian94@gmail.com" <petrutlucian94@gmail.com>,
Lucian Petrut <lpetrut@cloudbasesolutions.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
Justin Terry <juterry@microsoft.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] WHPX Add signature CPUID
Date: Wed, 16 May 2018 09:34:52 +0200 [thread overview]
Message-ID: <a7f0b9ab-3c8b-87d1-9f63-e82b13f66029@redhat.com> (raw)
In-Reply-To: <9ED401B4-3DF6-4BC8-9D38-14C78C9D1A66@cloudbasesolutions.com>
On 16/05/2018 01:55, Alessandro Pilotti wrote:
> Hi Paolo,
>
> The main reason for different signatures is to allow guest workloads
> to be aware of the differences between the two platforms (eg VirtIO
> vs VMBus).
Why does it matter? CPUID tells you about the enlightenments that the
hypervisor provides, not the availability of the VMBus.
VMBus requires some of the enlightenments, mostly related to the
synthetic interrupt controllers, but the opposite is not true---you can
have enlightenments without VMBus, and in fact you probably want WHPX to
enable the relaxed timing enlightenment.
Thanks,
Paolo
next prev parent reply other threads:[~2018-05-16 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 11:37 [Qemu-devel] [PATCH] WHPX Add signature CPUID petrutlucian94
2018-05-15 14:01 ` Justin Terry (VM)
2018-05-15 14:43 ` Paolo Bonzini
2018-05-15 23:55 ` Alessandro Pilotti
2018-05-16 7:34 ` Paolo Bonzini [this message]
2018-05-16 14:18 ` Justin Terry (VM)
2018-06-27 12:53 ` Paolo Bonzini
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=a7f0b9ab-3c8b-87d1-9f63-e82b13f66029@redhat.com \
--to=pbonzini@redhat.com \
--cc=apilotti@cloudbasesolutions.com \
--cc=ehabkost@redhat.com \
--cc=juterry@microsoft.com \
--cc=lpetrut@cloudbasesolutions.com \
--cc=petrutlucian94@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).