All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Wanpeng Li <wanpeng.li@linux.intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, KVM <kvm@vger.kernel.org>,
	Gleb Natapov <gleb@kernel.org>, Rik van Riel <riel@redhat.com>,
	Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
	Michael Mueller <mimu@linux.vnet.ibm.com>
Subject: Re: [PATCH/RFC] KVM: track pid for VCPU only on KVM_RUN ioctl
Date: Wed, 20 Aug 2014 09:01:04 +0200	[thread overview]
Message-ID: <53F447B0.1000808@de.ibm.com> (raw)
In-Reply-To: <20140819232246.GA8759@kernel>

On 20/08/14 01:22, Wanpeng Li wrote:
> On Tue, Aug 19, 2014 at 04:04:03PM +0200, Christian Borntraeger wrote:
>> On 18/08/14 07:02, Wanpeng Li wrote:
>>> Hi Christian,
>>> On Tue, Aug 05, 2014 at 04:44:14PM +0200, Christian Borntraeger wrote:
>>>> We currently track the pid of the task that runs the VCPU in
>>>> vcpu_load. Since we call vcpu_load for all kind of ioctls on a
>>>> CPU, this causes hickups due to synchronize_rcu if one CPU is
>>>> modified by another CPU or the main thread (e.g. initialization,
>>>> reset). We track the pid only for the purpose of yielding, so
>>>> let's update the pid only in the KVM_RUN ioctl.
>>>>
>>>> In addition, don't do a synchronize_rcu on startup (pid == 0).
>>>>
>>>> This speeds up guest boot time on s390 noticably for some configs, e.g.
>>>> HZ=100, no full state tracking, 64 guest cpus 32 host cpus.
>>>>
>>>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>>>> CC: Rik van Riel <riel@redhat.com>
>>>> CC: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
>>>> CC: Michael Mueller <mimu@linux.vnet.ibm.com>
>>>> ---
>>>> virt/kvm/kvm_main.c | 17 +++++++++--------
>>>> 1 file changed, 9 insertions(+), 8 deletions(-)
>>>>
>>>> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
>>>> index 9ae9135..ebc8f54 100644
>>>> --- a/virt/kvm/kvm_main.c
>>>> +++ b/virt/kvm/kvm_main.c
>>>> @@ -124,14 +124,6 @@ int vcpu_load(struct kvm_vcpu *vcpu)
>>>>
>>>> 	if (mutex_lock_killable(&vcpu->mutex))
>>>> 		return -EINTR;
>>>
>>> One question: 
>>>
>>>> -	if (unlikely(vcpu->pid != current->pids[PIDTYPE_PID].pid)) {
>>>
>>> When vcpu->pid and current->pids[PIDTYPE_PID].pid will be different?
>>
>> If two different thread call an ioctl on a vcpu fd. (It must be an ioctl that has done vcpu_load - almost all except for some interrupt injections)
> 
> Thanks for your explanation. When can this happen?

In general, by using clone and do an ioctl in the new thread on a pre-existing fd.
In qemu, e.g. by using an kvm_ioctl on a vcpu from main thread or another cpu.



  reply	other threads:[~2014-08-20  7:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05 14:44 [PATCH/RFC] KVM: track pid for VCPU only on KVM_RUN ioctl Christian Borntraeger
2014-08-07  8:21 ` Raghavendra K T
2014-08-07  9:59   ` Christian Borntraeger
2014-08-07 13:40     ` Paolo Bonzini
2014-08-19  8:38       ` Christian Borntraeger
2014-08-07 13:39 ` Paolo Bonzini
2014-08-19  8:38   ` Christian Borntraeger
2014-08-19  9:27     ` Paolo Bonzini
2014-08-19  9:47       ` Christian Borntraeger
2014-08-19  9:53         ` Paolo Bonzini
2014-08-19  9:59           ` Christian Borntraeger
2014-08-19 10:03             ` Paolo Bonzini
2014-08-19 10:09               ` Christian Borntraeger
2014-08-19 10:31                 ` Paolo Bonzini
2014-08-19 10:48                   ` Christian Borntraeger
2014-08-19 10:50                     ` Paolo Bonzini
2014-08-19 11:28       ` David Hildenbrand
2014-08-19 12:06         ` Paolo Bonzini
2014-08-19 12:14           ` David Hildenbrand
2014-08-19 14:10             ` Christian Borntraeger
2014-08-19 14:23               ` David Hildenbrand
2014-08-19 14:46                 ` Christian Borntraeger
2014-08-19 14:52                   ` David Hildenbrand
2014-08-18  5:02 ` Wanpeng Li
2014-08-19 14:04   ` Christian Borntraeger
2014-08-19 23:22     ` Wanpeng Li
2014-08-20  7:01       ` Christian Borntraeger [this message]
2014-12-03 13:20 ` 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=53F447B0.1000808@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=mimu@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=raghavendra.kt@linux.vnet.ibm.com \
    --cc=riel@redhat.com \
    --cc=wanpeng.li@linux.intel.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.