From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
David Hildenbrand <david@redhat.com>
Cc: "Wanpeng Li" <kernellwp@gmail.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Wanpeng Li" <wanpeng.li@hotmail.com>
Subject: Re: [PATCH v4 1/4] KVM: X86: Add vCPU running/preempted state
Date: Tue, 14 Nov 2017 18:04:16 +0100 [thread overview]
Message-ID: <af928d95-a9f7-4cb8-3891-0849e680a7ff@redhat.com> (raw)
In-Reply-To: <20171114170318.GE3165@worktop.lehotels.local>
On 14/11/2017 18:03, Peter Zijlstra wrote:
>> KVM_STEAL_TIME_(FLAG_)PREEMPTED
>> KVM_STEAL_TIME_(FLAG_)NOT_PREEMPTED
> Shees, and I thought the KVM_CPU_ crap was already long winded.
Yeah, it's too long. KVM_VCPU_* is not a great name, but it's clear and
concise.
Paolo
next prev parent reply other threads:[~2017-11-14 17:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 0:33 [PATCH v4 0/4] KVM: X86: Paravirt remote TLB flush Wanpeng Li
2017-11-13 0:33 ` [PATCH v4 1/4] KVM: X86: Add vCPU running/preempted state Wanpeng Li
2017-11-14 16:45 ` David Hildenbrand
2017-11-14 17:03 ` Peter Zijlstra
2017-11-14 17:04 ` Paolo Bonzini [this message]
2017-11-13 0:33 ` [PATCH v4 2/4] KVM: X86: Add paravirt remote TLB flush Wanpeng Li
2017-11-13 7:59 ` Peter Zijlstra
2017-11-13 8:12 ` Wanpeng Li
2017-11-13 8:04 ` Peter Zijlstra
2017-11-13 8:26 ` Wanpeng Li
2017-11-13 10:46 ` Peter Zijlstra
2017-11-13 13:02 ` Peter Zijlstra
2017-11-14 6:10 ` Wanpeng Li
2017-11-14 7:35 ` Peter Zijlstra
2017-11-14 6:28 ` Wanpeng Li
2017-11-14 7:56 ` Peter Zijlstra
2017-11-13 0:33 ` [PATCH v4 3/4] KVM: X86: introduce invalidate_gpa argument to tlb flush Wanpeng Li
2017-11-13 0:33 ` [PATCH v4 4/4] KVM: X86: Add flush_on_enter before guest enter 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=af928d95-a9f7-4cb8-3891-0849e680a7ff@redhat.com \
--to=pbonzini@redhat.com \
--cc=david@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®