All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v2.1 0/6] On top of Thomas+Paolo's
Date: Wed, 20 Jun 2018 23:14:31 -0400	[thread overview]
Message-ID: <20180621031431.GA9544@char.us.oracle.com> (raw)
In-Reply-To: <20180620204255.997582191@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]

On Wed, Jun 20, 2018 at 04:42:56PM -0400, speck for konrad.wilk_at_oracle.com wrote:
> Hey,
> 
> This patchset replaces Paolo's second patch but also adds the warnings
> that Linus wanted. Along with some extra knobs in case the MSR will
> have more things in the future.
> 
> Oh, and one bug-fix.
> 
> I am also working on using the VMX Load MSR list so that the L1D flush
> happens automatically on VMENTER.

Done.

Attached is the git bundle of the patches that were posted and also
code to do L1D flush using the VMX load MSR list. 

I can most certainly post it, but I hadn't run any performance numbers
so not sure if that approach is even worth it or not.

> 
> 
> Konrad Rzeszutek Wilk (5):
>       x86/bugs: Move the l1tf function and define pr_fmt properly
>       x86/cpufeatures: Add detection of L1D cache flush support.
>       x86/bugs: Read FLUSH_CMD MSR during boot.
>       x86/KVM: Warn user if KVM is loaded SMT and L1TF CPU bug being present.
>       x86/KVM: Use L1 cache flush before VMENTER if available.
> 
> Paolo Bonzini (1):
>       kvm: x86: mitigation for L1 cache terminal fault vulnerabilities
> 
>  Documentation/admin-guide/kernel-parameters.txt |  4 ++
>  arch/x86/include/asm/cpu.h                      |  4 ++
>  arch/x86/include/asm/cpufeatures.h              |  1 +
>  arch/x86/include/asm/kvm_host.h                 |  7 ++-
>  arch/x86/include/asm/msr-index.h                |  6 ++
>  arch/x86/kernel/cpu/bugs.c                      | 83 +++++++++++++++++--------
>  arch/x86/kvm/mmu.c                              |  1 +
>  arch/x86/kvm/svm.c                              |  3 +-
>  arch/x86/kvm/vmx.c                              | 46 +++++++++++++-
>  arch/x86/kvm/x86.c                              | 80 +++++++++++++++++++++++-
>  kernel/cpu.c                                    |  1 +
>  11 files changed, 205 insertions(+), 31 deletions(-)

[-- Attachment #2: kvm.l1tf.v4.rc5.bundle --]
[-- Type: application/octet-stream, Size: 49667 bytes --]

  reply	other threads:[~2018-06-21  3:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 20:42 [MODERATED] [PATCH v2.1 0/6] On top of Thomas+Paolo's konrad.wilk
2018-06-21  3:14 ` Konrad Rzeszutek Wilk [this message]
2018-06-21  8:46   ` [MODERATED] " Peter Zijlstra
2018-06-21 15:35     ` Thomas Gleixner
2018-06-21 17:49       ` [MODERATED] " Konrad Rzeszutek Wilk
2018-06-21 20:37     ` Linus Torvalds

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=20180621031431.GA9544@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.