From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>,
Andy Lutomirski <luto@kernel.org>
Cc: Tao Xu <tao3.xu@intel.com>, Paolo Bonzini <pbonzini@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>, X86 ML <x86@kernel.org>,
kvm list <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] KVM: VMX: Enable Notify VM exit
Date: Mon, 17 May 2021 15:20:32 +0800 [thread overview]
Message-ID: <5117f8d3-c40c-204d-b09c-e49af42ad665@intel.com> (raw)
In-Reply-To: <20201102183359.GE21563@linux.intel.com>
Hi Sean, Andy and Paolo,
On 11/3/2020 2:33 AM, Sean Christopherson wrote:
> On Mon, Nov 02, 2020 at 10:01:16AM -0800, Andy Lutomirski wrote:
>> On Mon, Nov 2, 2020 at 9:31 AM Sean Christopherson
>> <sean.j.christopherson@intel.com> wrote:
>>>
>>> Tao, this patch should probably be tagged RFC, at least until we can experiment
>>> with the threshold on real silicon. KVM and kernel behavior may depend on the
>>> accuracy of detecting actual attacks, e.g. if we can set a threshold that has
>>> zero false negatives and near-zero false postives, then it probably makes sense
>>> to be more assertive in how such VM-Exits are reported and logged.
>>
>> If you can actually find a threshold that reliably mitigates the bug
>> and does not allow a guest to cause undesirably large latency in the
>> host, then fine. 1/10 if a tick is way too long, I think.
>
> Yes, this was my internal review feedback as well. Either that got lost along
> the way or I wasn't clear enough in stating what should be used as a placeholder
> until we have silicon in hand.
>
We have tested on real silicon and found it can work even with threshold
being set to 0.
It has an internal threshold, which is added to vmcs.notify_window as
the final effective threshold. The internal threshold is big enough to
cover normal instructions. For those long latency instructions like
WBINVD, the processor knows they cannot cause no interrupt window
attack. So no Notify VM exit will happen on them.
Initially, our hardware architect wants to set the notify window to
scheduler tick to not break kernel scheduling. But you folks want a
smaller one. So are you OK to set the window to 0?
next prev parent reply other threads:[~2021-05-17 7:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 6:14 [PATCH] KVM: VMX: Enable Notify VM exit Tao Xu
2020-11-02 16:43 ` Andy Lutomirski
2020-11-02 17:31 ` Sean Christopherson
2020-11-02 18:01 ` Andy Lutomirski
2020-11-02 18:25 ` Paolo Bonzini
2020-11-03 6:39 ` Xiaoyao Li
2020-11-02 18:33 ` Sean Christopherson
2021-05-17 7:20 ` Xiaoyao Li [this message]
2021-05-17 8:55 ` Xiaoyao Li
2020-11-03 5:35 ` Tao Xu
2020-11-03 6:08 ` Tao Xu
2020-11-03 7:29 ` Xiaoyao Li
2020-11-02 17:32 ` Sean Christopherson
2020-11-03 5:36 ` Tao Xu
2020-11-02 22:53 ` Jim Mattson
2020-11-03 6:12 ` Tao Xu
2020-11-03 6:24 ` Xiaoyao Li
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=5117f8d3-c40c-204d-b09c-e49af42ad665@intel.com \
--to=xiaoyao.li@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tao3.xu@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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.