From: Eduardo Habkost <ehabkost@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Jingqi Liu <jingqi.liu@intel.com>,
rth@twiddle.net, mtosatti@redhat.com, qemu-devel@nongnu.org,
wei.w.wang@intel.com, "Hu, Robert" <robert.hu@intel.com>
Subject: Re: [Qemu-devel] [PATCH] kvm: x86: Add support for -machine split-lock-ac
Date: Wed, 4 Jul 2018 14:52:34 -0300 [thread overview]
Message-ID: <20180704175234.GX7451@localhost.localdomain> (raw)
In-Reply-To: <cfe2a879-d038-f80f-cbec-ae247afde702@redhat.com>
On Wed, Jul 04, 2018 at 03:38:32PM +0200, Paolo Bonzini wrote:
> On 04/07/2018 15:12, Jingqi Liu wrote:
> > Add the option split-lock-ac to control whether the #AC
> > exception is generated for split locked accesses, which
> > is introduced for the machine, there is an example to enable it:
> > -machine split-lock-ac=on
> > It is disabled on default.
> >
> > When bit 29 of the MSR (33H) is set, the processor
> > causes an #AC exception to be issued instead of suppressing LOCK on
> > bus(during split lock access).
>
> This should be a CPU feature, not a machine feature. As mentioned in
> the review of the kernel patch, please work with Robert to use the same
> infrastructure for both MSR_TEST_CTL and MSR_IA32_ARCH_CAPABILITIES.
>
> (Robert, does IceLake have this feature? If so, we cannot create the
> CPU model until everything is in place).
I don't think we need to block the CPU model because QEMU+KVM
doesn't support some features yet, as long as kernel versions
capable of running the 3.0 version of IceLake-Server will be also
capable of running the 3.1 version of IceLake-Server.
Now, if that condition won't be true and we have some IceLake
features that will added only to more recent kernels, it might be
a good idea to hold the inclusion of the CPU model until
everything is in place.
>
> BTW, why is the availability of the feature not exposed with a CPUID
> bit? It doesn't make much sense.
I have the same question. Without a CPUID bit, guests may block
the VM from being migrated to older hosts because the additional
section for the MSR will appear.
--
Eduardo
next prev parent reply other threads:[~2018-07-04 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 13:12 [Qemu-devel] [PATCH] kvm: x86: Add support for -machine split-lock-ac Jingqi Liu
2018-07-04 13:38 ` Paolo Bonzini
2018-07-04 17:52 ` Eduardo Habkost [this message]
2018-07-05 10:58 ` Paolo Bonzini
2018-07-05 8:45 ` Hu, Robert
2018-07-05 12:05 ` Paolo Bonzini
2018-07-04 14:05 ` no-reply
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=20180704175234.GX7451@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=jingqi.liu@intel.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@intel.com \
--cc=rth@twiddle.net \
--cc=wei.w.wang@intel.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 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).