From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Wanpeng Li" <kernellwp@gmail.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Wanpeng Li" <wanpeng.li@hotmail.com>
Subject: Re: [PATCH v5 2/4] KVM: X86: Add paravirt remote TLB flush
Date: Thu, 16 Nov 2017 11:06:13 -0500 [thread overview]
Message-ID: <20171116160613.GY21113@char.us.oracle.com> (raw)
In-Reply-To: <d7ef9549-9339-251f-b0d1-de1a4c83cea0@redhat.com>
On Thu, Nov 16, 2017 at 12:00:45PM +0100, Paolo Bonzini wrote:
> On 15/11/2017 22:11, Konrad Rzeszutek Wilk wrote:
> > If we migrate to another host that does not expose this, should the
> > flush_tlb_others be reset back to the generic one? Or we don't care that
> > much ?
>
> Migration to a host that does not expose the feature would be a
> configuration error.
Right, so should there be an check somewhere to disallow this <lots of hand waving>?
Or at least print out a "Hey, this is not a good idea!"
>
> Paolo
next prev parent reply other threads:[~2017-11-16 16:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 10:01 [PATCH v5 0/4] KVM: X86: Paravirt " Wanpeng Li
2017-11-13 10:01 ` [PATCH v5 1/4] KVM: X86: Add vCPU running/preempted state Wanpeng Li
2017-11-13 10:01 ` [PATCH v5 2/4] KVM: X86: Add paravirt remote TLB flush Wanpeng Li
2017-11-15 21:11 ` Konrad Rzeszutek Wilk
2017-11-16 10:17 ` Wanpeng Li
2017-11-16 11:00 ` Paolo Bonzini
2017-11-16 16:06 ` Konrad Rzeszutek Wilk [this message]
2017-11-16 5:30 ` Wanpeng Li
2017-11-16 8:38 ` Peter Zijlstra
2017-11-16 8:51 ` Wanpeng Li
2017-11-16 9:07 ` Peter Zijlstra
2017-11-13 10:01 ` [PATCH v5 3/4] KVM: X86: introduce invalidate_gpa argument to tlb flush Wanpeng Li
2017-11-13 10:01 ` [PATCH v5 4/4] KVM: X86: Add flush_on_enter before guest enter Wanpeng Li
2017-11-15 21:05 ` [PATCH v5 0/4] KVM: X86: Paravirt remote TLB flush Konrad Rzeszutek Wilk
2017-11-16 10:21 ` Wanpeng 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=20171116160613.GY21113@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=wanpeng.li@hotmail.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
Powered by JetHome