From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [patch 08/15] SSB updates V17 8
Date: Thu, 17 May 2018 12:23:44 -0400 [thread overview]
Message-ID: <20180517162344.GE18423@char.us.oracle.com> (raw)
In-Reply-To: <7336bf63-e63b-5a70-0d2e-2bf093314fda@redhat.com>
On Thu, May 17, 2018 at 06:17:53PM +0200, speck for Paolo Bonzini wrote:
> On 17/05/2018 18:13, speck for Tom Lendacky wrote:
> >>> Paolo (I'm assuming your on this list),
> >>>
> >>> Do you know if anyone is working on Qemu / Libvirt patches to support the
> >>> new AMD VIRT_SSBD feature (new CPU definitions, etc.)?
> >> But surely you have a patch that you wrote for testing this?
> > Yes, but I want to build upon anything that may already be in progress.
> > Also, I'm not a qemu expert so I wanted to be sure I had everything.
> > For example, I can already see that the KVM support needs to add
> > MSR_AMD64_VIRT_SPEC_CTRL to msrs_to_save in arch/x86/kvm/x86.c (I'll
> > send a follow-up patch to the list to add that).
> >
> >> Did you have in mind these two patches (inline), not tested, still compiling.
> >>
> >> If you can test them, I can sync up with Daniel P. Berrangé who is going
> >> to post the Intel SSBD ones for libvirt+qemu on Monday.
> > Yes, I'll review and test. I have some initial comments below.
>
> I got (Konrad's?) patches for QEMU via Dan, and they seem to be okay.
Did my SoB/authorship get lost?
I will fix them up and send them to Dan, John, and you
per Tom's commnents.
>
> > I'll provide a patch back on top of these patches with any other updates.
>
>
next prev parent reply other threads:[~2018-05-17 16:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 13:51 [patch 00/15] SSB updates V17 0 Thomas Gleixner
2018-05-16 13:51 ` [patch 01/15] SSB updates V17 1 Thomas Gleixner
2018-05-16 13:51 ` [patch 02/15] SSB updates V17 2 Thomas Gleixner
2018-05-16 14:29 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 13:51 ` [patch 03/15] SSB updates V17 3 Thomas Gleixner
2018-05-17 1:06 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 13:51 ` [patch 04/15] SSB updates V17 4 Thomas Gleixner
2018-05-17 1:14 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 13:51 ` [patch 05/15] SSB updates V17 5 Thomas Gleixner
2018-05-17 1:14 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 13:51 ` [patch 06/15] SSB updates V17 6 Thomas Gleixner
2018-05-17 1:28 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 13:51 ` [patch 07/15] SSB updates V17 7 Thomas Gleixner
2018-05-17 1:29 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 13:51 ` [patch 08/15] SSB updates V17 8 Thomas Gleixner
2018-05-16 21:13 ` [MODERATED] " Tom Lendacky
2018-05-17 2:56 ` Konrad Rzeszutek Wilk
2018-05-17 16:13 ` Tom Lendacky
2018-05-17 16:17 ` Paolo Bonzini
2018-05-17 16:23 ` Konrad Rzeszutek Wilk [this message]
2018-05-17 21:25 ` Tom Lendacky
2018-05-17 16:18 ` Tom Lendacky
2018-05-16 13:51 ` [patch 09/15] SSB updates V17 9 Thomas Gleixner
2018-05-17 1:40 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 13:51 ` [patch 10/15] SSB updates V17 10 Thomas Gleixner
2018-05-17 1:43 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 13:51 ` [patch 11/15] SSB updates V17 11 Thomas Gleixner
2018-05-17 1:45 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-16 13:51 ` [patch 12/15] SSB updates V17 12 Thomas Gleixner
2018-05-16 13:51 ` [patch 13/15] SSB updates V17 13 Thomas Gleixner
2018-05-17 2:08 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-17 8:45 ` Thomas Gleixner
2018-05-16 13:51 ` [patch 14/15] SSB updates V17 14 Thomas Gleixner
2018-05-16 16:34 ` [MODERATED] " Tom Lendacky
2018-05-16 21:26 ` Thomas Gleixner
2018-05-16 13:51 ` [patch 15/15] SSB updates V17 15 Thomas Gleixner
2018-05-17 2:18 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-17 12:42 ` Paolo Bonzini
2018-05-17 15:09 ` Thomas Gleixner
2018-05-16 14:09 ` [patch 00/15] SSB updates V17 0 Thomas Gleixner
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=20180517162344.GE18423@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=speck@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.