All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanpeng Li <kernellwp@gmail.com>
To: David Hildenbrand <david@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	kvm <kvm@vger.kernel.org>, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Wanpeng Li" <wanpeng.li@hotmail.com>
Subject: Re: [PATCH v8 1/4] KVM: X86: Add vCPU running/preempted state
Date: Wed, 13 Dec 2017 19:38:00 +0800	[thread overview]
Message-ID: <CANRm+CwN=e9x-t+P3tEb7NvWkWACXvqf1UTG35Cwkxj_Y3HboQ@mail.gmail.com> (raw)
In-Reply-To: <3fb56993-3bb6-442c-f12e-0c99c06ef5c2@redhat.com>

2017-12-13 18:20 GMT+08:00 David Hildenbrand <david@redhat.com>:
> On 13.12.2017 02:33, Wanpeng Li wrote:
>> From: Wanpeng Li <wanpeng.li@hotmail.com>
>>
>> This patch reuses the preempted field in kvm_steal_time, and will export
>> the vcpu running/pre-empted information to the guest from host. This will
>> enable guest to intelligently send ipi to running vcpus and set flag for
>> pre-empted vcpus. This will prevent waiting for vcpus that are not running.
>>
>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>> Cc: Radim Krčmář <rkrcmar@redhat.com>
>> Cc: Peter Zijlstra <peterz@infradead.org>
>> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com>
>> ---
>>  arch/x86/include/uapi/asm/kvm_para.h | 3 +++
>>  arch/x86/kernel/kvm.c                | 2 +-
>>  arch/x86/kvm/x86.c                   | 4 ++--
>>  3 files changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/x86/include/uapi/asm/kvm_para.h b/arch/x86/include/uapi/asm/kvm_para.h
>> index 09cc064..763b692 100644
>> --- a/arch/x86/include/uapi/asm/kvm_para.h
>> +++ b/arch/x86/include/uapi/asm/kvm_para.h
>> @@ -51,6 +51,9 @@ struct kvm_steal_time {
>>       __u32 pad[11];
>>  };
>>
>> +#define KVM_VCPU_NOT_PREEMPTED      (0 << 0)
>> +#define KVM_VCPU_PREEMPTED          (1 << 0)
>
> Is it really helpful to have two flags?
>
> Just use KVM_VCPU_PREEMPTED  and clear that one in record_steal_time()

I think it is fine since there is a third flag introduced in patch
2/4, it is more clear currently.

Regards,
Wanpeng Li

  reply	other threads:[~2017-12-13 11:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13  1:33 [PATCH v8 0/4] KVM: X86: Add Paravirt TLB Shootdown Wanpeng Li
2017-12-13  1:33 ` [PATCH v8 1/4] KVM: X86: Add vCPU running/preempted state Wanpeng Li
2017-12-13 10:20   ` David Hildenbrand
2017-12-13 11:38     ` Wanpeng Li [this message]
2017-12-13 11:45       ` David Hildenbrand
2017-12-13 12:31         ` Paolo Bonzini
2017-12-13  1:33 ` [PATCH v8 2/4] KVM: X86: Add Paravirt TLB Shootdown Wanpeng Li
2017-12-13 12:33   ` Paolo Bonzini
2017-12-13  1:33 ` [PATCH v8 3/4] KVM: X86: introduce invalidate_gpa argument to tlb flush Wanpeng Li
2017-12-13 13:35   ` Peter Zijlstra
2017-12-13  1:33 ` [PATCH v8 4/4] KVM: X86: Add flush_on_enter before guest enter Wanpeng Li
2017-12-13 12:54   ` Peter Zijlstra
2017-12-13 13:32     ` Paolo Bonzini
2017-12-13 13:35   ` Peter Zijlstra
2017-12-13 13:37     ` Paolo Bonzini
2017-12-13  9:42 ` [PATCH v8 0/4] KVM: X86: Add Paravirt TLB Shootdown Wanpeng Li
2017-12-13 12:47   ` Paolo Bonzini
2017-12-13 13:13     ` 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='CANRm+CwN=e9x-t+P3tEb7NvWkWACXvqf1UTG35Cwkxj_Y3HboQ@mail.gmail.com' \
    --to=kernellwp@gmail.com \
    --cc=david@redhat.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 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.