From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH] L1TF KVM ARCH_CAPABILITIES #1
Date: Mon, 16 Jul 2018 10:36:39 -0400 [thread overview]
Message-ID: <20180716143639.GA24786@char.US.ORACLE.com> (raw)
In-Reply-To: <20180715135716.1874-2-pbonzini@redhat.com>
On Sun, Jul 15, 2018 at 03:57:13PM +0200, speck for Paolo Bonzini wrote:
> From: Paolo Bonzini <pbonzini@redhat.com>
> Subject: [PATCH 1/4] KVM: test L1TF EPT bug separately from X86_BUG_L1TF
>
> If bit 3 of ARCH_CAPABILITIES is set, the L1TF bug is present but the hypervisor
> does not need to flush the L1D cache on vmentry. To prepare for that, use
> l1tf_vmx_mitigation to test for the EPT variant of the bug in KVM.
> boot_cpu_has(X86_BUG_L1TF) is only used for the non-hypervisor case.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> arch/x86/include/asm/vmx.h | 1 +
> arch/x86/kernel/cpu/bugs.c | 18 ++++++++++++------
> arch/x86/kvm/vmx.c | 33 +++++++++++++++++++++++----------
> 3 files changed, 36 insertions(+), 16 deletions(-)
patching file arch/x86/include/asm/vmx.h
patching file arch/x86/kernel/cpu/bugs.c
Hunk #1 succeeded at 678 (offset 6 lines).
Hunk #2 FAILED at 743.
1 out of 2 hunks FAILED -- saving rejects to file arch/x86/kernel/cpu/bugs.c.rej
patching file arch/x86/kvm/vmx.c
[konrad@char linux]$
Which seems to be related to the whitespace in l1tf_vmx_states?
next prev parent reply other threads:[~2018-07-16 14:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 13:57 [MODERATED] [PATCH] L1TF KVM ARCH_CAPABILITIES #0 Paolo Bonzini
2018-07-15 13:57 ` [MODERATED] [PATCH] L1TF KVM ARCH_CAPABILITIES #1 Paolo Bonzini
2018-07-16 14:36 ` Konrad Rzeszutek Wilk [this message]
2018-07-16 20:02 ` Thomas Gleixner
2018-07-17 11:20 ` [MODERATED] " Paolo Bonzini
2018-07-17 11:28 ` Thomas Gleixner
2018-07-17 17:11 ` [MODERATED] " Paolo Bonzini
2018-07-17 19:23 ` Thomas Gleixner
2018-07-15 13:57 ` [MODERATED] [PATCH] L1TF KVM ARCH_CAPABILITIES #2 Paolo Bonzini
2018-07-16 20:04 ` Thomas Gleixner
2018-07-16 20:31 ` Thomas Gleixner
2018-07-16 20:41 ` [MODERATED] " Luck, Tony
2018-07-16 21:13 ` Thomas Gleixner
2018-07-15 13:57 ` [MODERATED] [PATCH] L1TF KVM ARCH_CAPABILITIES #3 Paolo Bonzini
2018-07-15 13:57 ` [MODERATED] [PATCH] L1TF KVM ARCH_CAPABILITIES #4 Paolo Bonzini
2018-07-16 14:58 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-07-16 20:06 ` Thomas Gleixner
2018-07-17 11:14 ` [MODERATED] " Paolo Bonzini
2018-07-16 20:44 ` [MODERATED] Re: [PATCH] L1TF KVM ARCH_CAPABILITIES #0 Konrad Rzeszutek Wilk
2018-07-17 11:22 ` 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=20180716143639.GA24786@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.