From: Paolo Bonzini <pbonzini@redhat.com>
To: "Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
"valdis.kletnieks@vt.edu" <valdis.kletnieks@vt.edu>
Cc: Jon Masters <jcm@jonmasters.org>,
David Woodhouse <dwmw2@infradead.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"x86@kernel.org" <x86@kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hansen, Dave" <dave.hansen@intel.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 2/2] x86/speculation: Support "Enhanced IBRS" on future CPUs
Date: Tue, 20 Feb 2018 16:09:38 +0100 [thread overview]
Message-ID: <5b39cfbb-a04f-46a8-87cb-3a52fc8e9700@redhat.com> (raw)
In-Reply-To: <0575AF4FD06DD142AD198903C74E1CC87A6194AB@ORSMSX103.amr.corp.intel.com>
On 20/02/2018 15:59, Van De Ven, Arjan wrote:
>
>>> I meant software wise. You're not going to live migrate from xen to
>>> kvm or backwards. or between very radically different versions of the
>>> kvm stack.
>>
>> Forwards migration to a radically newer version certainly happens. So
>> when the source hypervisor was too old to tell the VM about IBRS_ALL,
>> for example, migration should work properly and the VM should perform
>> well on the destination hypervisor.
>
> that makes sense, compatibility in this direction can be done
> and is useful as you move a fleet of servers forward
>
>> Backwards migration to older hypervisors also happens sometimes, but in
>> general it creates more userspace than kernel issues.
>
> that direction is obviously harder
>From KVM's point of view it's mostly a matter of having a complete ioctl
API right. I'm not that much worried by it.
Paolo
next prev parent reply other threads:[~2018-02-20 15:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 15:27 [PATCH 1/2] x86/speculation: Correct Speculation Control microcode blacklist again David Woodhouse
2018-02-12 15:27 ` [PATCH 2/2] x86/speculation: Support "Enhanced IBRS" on future CPUs David Woodhouse
2018-02-13 7:47 ` Ingo Molnar
2018-02-13 8:12 ` David Woodhouse
2018-02-13 8:02 ` Paolo Bonzini
2018-02-13 8:15 ` David Woodhouse
2018-02-13 9:58 ` Paolo Bonzini
2018-02-13 10:21 ` David Woodhouse
2018-02-13 10:36 ` David Woodhouse
2018-02-13 10:41 ` Paolo Bonzini
2018-02-13 10:53 ` David Woodhouse
2018-02-13 10:55 ` Paolo Bonzini
2018-02-16 9:58 ` David Woodhouse
2018-02-16 10:08 ` Paolo Bonzini
2018-02-16 10:21 ` David Woodhouse
2018-02-16 11:04 ` Paolo Bonzini
2018-02-16 12:10 ` David Woodhouse
2018-02-19 23:37 ` Jon Masters
2018-02-19 23:42 ` Van De Ven, Arjan
2018-02-19 23:53 ` valdis.kletnieks
2018-02-20 0:00 ` Van De Ven, Arjan
2018-02-20 0:13 ` Alan Cox
2018-02-20 0:43 ` Linus Torvalds
2018-02-20 1:03 ` Alan Cox
2018-02-20 1:08 ` Van De Ven, Arjan
2018-02-20 8:52 ` Thomas Gleixner
2018-02-20 11:43 ` Paolo Bonzini
2018-02-20 14:08 ` Van De Ven, Arjan
2018-02-20 14:46 ` Paolo Bonzini
2018-02-20 14:59 ` Van De Ven, Arjan
2018-02-20 15:09 ` Paolo Bonzini [this message]
2018-02-23 18:12 ` Is: RSB Alternative bit in IA32_ARCH_CAPABILITIES Was:Re: " Konrad Rzeszutek Wilk
2018-02-23 18:18 ` Van De Ven, Arjan
2018-02-15 15:21 ` Pavel Machek
2018-02-13 8:57 ` [tip:x86/pti] x86/speculation: Correct Speculation Control microcode blacklist again tip-bot for David Woodhouse
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=5b39cfbb-a04f-46a8-87cb-3a52fc8e9700@redhat.com \
--to=pbonzini@redhat.com \
--cc=arjan.van.de.ven@intel.com \
--cc=dave.hansen@intel.com \
--cc=dwmw2@infradead.org \
--cc=jcm@jonmasters.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=valdis.kletnieks@vt.edu \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®