public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>, "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 15:30:17 +0000	[thread overview]
Message-ID: <20181211153017.GN921@redhat.com> (raw)
In-Reply-To: <e4d9a943-2de2-34a7-3f52-ee3d64ea889a@redhat.com>

On Tue, Dec 11, 2018 at 04:23:51PM +0100, Paolo Bonzini wrote:
> On 11/12/18 12:55, Eduardo Habkost wrote:
> >>   - 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.
> 
> Anyway RHEL does have RDTSC support for AMD, and a bunch of other stuff.
>  The frankenkernel's KVM is somewhere between 4.5 and 4.10, with a dash
> of 4.20 of course. :)

Great, then, this is a non-issue - we just need to mention that fact
in the commit that sets the min version for the kernel 

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2018-12-11 15:30 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
2018-12-11 14:35               ` Daniel P. Berrangé
2018-12-11 15:23               ` Paolo Bonzini
2018-12-11 15:30                 ` Daniel P. Berrangé [this message]
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=20181211153017.GN921@redhat.com \
    --to=berrange@redhat.com \
    --cc=andre.przywara@arm.com \
    --cc=bp@alien8.de \
    --cc=eblake@redhat.com \
    --cc=ehabkost@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