public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Borislav Petkov" <bp@alien8.de>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Jörg Rödel" <joro@8bytes.org>,
	"Andre Przywara" <andre.przywara@arm.com>,
	"kvm ML" <kvm@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	"Tom Lendacky" <thomas.lendacky@amd.com>,
	"Eric Blake" <eblake@redhat.com>
Subject: Re: kvm: RDTSCP on AMD
Date: Tue, 11 Dec 2018 09:55:46 -0200	[thread overview]
Message-ID: <20181211115546.GQ4669@habkost.net> (raw)
In-Reply-To: <20181211103839.GC921@redhat.com>

On Tue, Dec 11, 2018 at 10:38:39AM +0000, Daniel P. Berrangé wrote:
> On Mon, Dec 10, 2018 at 06:08:43PM -0200, Eduardo Habkost wrote:
> > On Mon, Dec 10, 2018 at 08:42:58PM +0100, Borislav Petkov wrote:
> > > On Mon, Dec 10, 2018 at 05:06:00PM -0200, Eduardo Habkost wrote:
> > > > I mean documenting it.  We already have code that will print
> > > > warnings if a feature isn't available.
> > > > 
> > > > See my previous attempt to document the minimum kernel version
> > > > at <https://www.mail-archive.com/qemu-devel@nongnu.org/msg486559.html>.
> > > 
> > > Something like this?
> > > 
> > > I still have no clue how to add RDTSCP on pc-*-4.0 and newer.
> > 
> > qemu.git master have no PC_COMPAT_3_1 and pc-*-4.0 machine-types
> > yet.  I've sent another reply with additional pointers.
> > 
> > > 
> > > Thx.
> > > 
> > > ---
> > > diff --git a/qemu-doc.texi b/qemu-doc.texi
> > > index f7ad1dfe4b69..913b2ef68d54 100644
> > > --- a/qemu-doc.texi
> > > +++ b/qemu-doc.texi
> > > @@ -37,6 +37,7 @@
> > >  * QEMU System emulator for non PC targets::
> > >  * QEMU Guest Agent::
> > >  * QEMU User space emulator::
> > > +* System requirements::
> > >  * Implementation notes::
> > >  * Deprecated features::
> > >  * Supported build platforms::
> > > @@ -2813,6 +2814,13 @@ Act as if the host page size was 'pagesize' bytes
> > >  Run the emulation in single step mode.
> > >  @end table
> > >  
> > > +@node System requirements
> > > +@chapter System requirements
> > > +
> > > +@section KVM kernel module
> > > +
> > > +On x86_64 hosts, the default set of CPU features enabled by the KVM accelerator
> > > +require the host to be running Linux v4.5 or newer.
> > >  
> > 
> > Sounds good, but it would be nice to document what exactly makes
> > Linux 4.5+ necessary.  e.g.:
> > 
> > | On x86_64 hosts, it is recommended to run Linux 4.5 or newer on
> > | the host when using the KVM accelerator.
> > | 
> > | The Opteron_G2, OpteronG3, Opteron_G4, and Opteron_G5 CPU
> > | models require KVM support for RDTSCP, which was added on
> > | Linux 4.5.
> > 
> > I'm CCing some people who may help review English grammar and
> > style.
> 
> Note that QEMU has a declared supported platform list which is used to
> set the minimum software versions required.
> 
>    https://qemu.weilnetz.de/doc/qemu-doc.html#Linux-OS
> 
> Based on that policy, the Linux distros we aim to support have the
> following kernel versions:
> 
>   - Debian Jessie: 4.5
>   - Debian Stretch: 4.5
>   - RHEL-7: 3.10
>   - Ubuntu LTS (Xenial): 4.5
>   - OpenSUSE Leap 15: 4.12.14
> 
> So we can't require Linux 4.5 as a minimum version at this time.

I'd like us to take a step back and consider what exactly
"support" means here.  QEMU will still work on older kernels if
we add RDTSCP to the CPU models, but at the same time I would
like to document that our strict runnability guarantees may not
be kept if running Linux < 4.5.

-- 
Eduardo

  reply	other threads:[~2018-12-11 11:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10 18:13 kvm: RDTSCP on AMD Borislav Petkov
2018-12-10 18:37 ` Eduardo Habkost
2018-12-10 18:41   ` Borislav Petkov
2018-12-10 19:06     ` Eduardo Habkost
2018-12-10 19:42       ` Borislav Petkov
2018-12-10 20:08         ` Eduardo Habkost
2018-12-10 20:39           ` Borislav Petkov
2018-12-11 10:38           ` Daniel P. Berrangé
2018-12-11 11:55             ` Eduardo Habkost [this message]
2018-12-11 14:35               ` Daniel P. Berrangé
2018-12-11 15:23               ` Paolo Bonzini
2018-12-11 15:30                 ` Daniel P. Berrangé
2018-12-11 16:14                   ` [PATCH] target-i386: Reenable RDTSCP support on Opteron_G[345] CPU models Borislav Petkov
2018-12-12 19:52                     ` Eduardo Habkost
2018-12-12 20:08                       ` [PATCH -v2] target-i386: Reenable RDTSCP support on Opteron_G[345] CPU models " Borislav Petkov
2018-12-20 12:10                         ` Eduardo Habkost
2018-12-10 19:47     ` kvm: RDTSCP on AMD Eduardo Habkost
2018-12-10 20:16       ` Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2016-07-06 12:44 Borislav Petkov
2016-07-06 13:01 ` Paolo Bonzini
2016-07-06 17:34   ` Eduardo Habkost
2016-07-06 21:27     ` 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=20181211115546.GQ4669@habkost.net \
    --to=ehabkost@redhat.com \
    --cc=andre.przywara@arm.com \
    --cc=berrange@redhat.com \
    --cc=bp@alien8.de \
    --cc=eblake@redhat.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=thomas.lendacky@amd.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