From: Eduardo Habkost <ehabkost@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "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>
Subject: Re: kvm: RDTSCP on AMD
Date: Mon, 10 Dec 2018 17:06:00 -0200 [thread overview]
Message-ID: <20181210190600.GK4669@habkost.net> (raw)
In-Reply-To: <20181210184153.GB5482@zn.tnic>
On Mon, Dec 10, 2018 at 07:41:53PM +0100, Borislav Petkov wrote:
> On Mon, Dec 10, 2018 at 04:37:30PM -0200, Eduardo Habkost wrote:
> > It isn't as simply as reverting commit 33b5e8c03ae7, but we can
> > surely re-add RDTSCP on pc-*-4.0 and newer.
>
> Sure. If you could only point me to an example how to add that to
> pc-*-4.0 and newer, I'll gladly cook up a patch and test it.
>
> > I thought we added documentation mentioning the minimum kernel
> > version required by QEMU, but I can't find it. In either case,
> > it seems reasonable to require Linux 4.5 or newer on newer
> > machine-types.
>
> When you say "require" does that mean, one puts it in a text file
> somewhere in the qemu sources or do we enforce it somehow?
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>.
--
Eduardo
next prev parent reply other threads:[~2018-12-10 19:06 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 [this message]
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é
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=20181210190600.GK4669@habkost.net \
--to=ehabkost@redhat.com \
--cc=andre.przywara@arm.com \
--cc=bp@alien8.de \
--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