From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Gleb Natapov <gleb@minantech.com>, KVM <kvm@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
agraf@suse.de
Subject: Re: [PATCHv3] kvm/irqchip: Speed up KVM_SET_GSI_ROUTING
Date: Fri, 17 Jan 2014 15:03:43 +0100 [thread overview]
Message-ID: <52D9383F.7040206@redhat.com> (raw)
In-Reply-To: <20140116202213.GF29522@redhat.com>
Il 16/01/2014 21:22, Michael S. Tsirkin ha scritto:
>> [PATCHv3] kvm/irqchip: Speed up KVM_SET_GSI_ROUTING
>>
>> When starting lots of dataplane devices the bootup takes very long
>> on my s390 system(prototype irqfd code). With larger setups we are even
>> able to trigger some timeouts in some components.
>> Turns out that the KVM_SET_GSI_ROUTING ioctl takes very
>> long (strace claims up to 0.1 sec) when having multiple CPUs.
>> This is caused by the synchronize_rcu and the HZ=100 of s390.
>>
>> Lets use the expedited variant to speed things up as suggested by
>> Michael S. Tsirkin
>>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> ---
>> virt/kvm/irqchip.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/virt/kvm/irqchip.c b/virt/kvm/irqchip.c
>> index 20dc9e4..dbcfde7 100644
>> --- a/virt/kvm/irqchip.c
>> +++ b/virt/kvm/irqchip.c
>> @@ -226,7 +226,7 @@ int kvm_set_irq_routing(struct kvm *kvm,
>> kvm_irq_routing_update(kvm, new);
>> mutex_unlock(&kvm->irq_lock);
>>
>> - synchronize_rcu();
>> + synchronize_rcu_expedited();
>>
>> new = old;
>> r = 0;
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Well... I love to contradict myself, so: no way this can be accepted
this close to the end of the merge window. :(
synchronize_rcu_expedited() forces a context switch on all CPUs, even
those that are not running KVM. Thus, this patch might help a guest DoS
its host by changing the IRQ routing tables in a loop.
So this will have to wait for 3.15. We have ~2 months to do performance
measurements on the v2 patch. Sorry.
Thanks,
Paolo
next prev parent reply other threads:[~2014-01-17 14:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 9:23 [PATCH] kvm/irqchip: Speed up KVM_SET_GSI_ROUTING Christian Borntraeger
2014-01-16 11:24 ` Paolo Bonzini
2014-01-16 12:44 ` [PATCHv2/RFC] " Christian Borntraeger
2014-01-16 12:59 ` Paolo Bonzini
2014-01-16 13:06 ` Christian Borntraeger
2014-01-16 13:07 ` Paolo Bonzini
2014-01-16 18:56 ` Michael S. Tsirkin
2014-01-17 8:29 ` Christian Borntraeger
2014-01-17 9:19 ` Paolo Bonzini
2014-02-19 22:23 ` Paolo Bonzini
2014-02-21 4:59 ` Andrew Theurer
2014-01-16 18:55 ` Michael S. Tsirkin
2014-01-16 20:07 ` [PATCHv3] " Christian Borntraeger
2014-01-16 20:22 ` Michael S. Tsirkin
2014-01-17 14:03 ` Paolo Bonzini [this message]
2014-01-17 15:03 ` Christian Borntraeger
2014-01-17 15:26 ` Paolo Bonzini
2014-02-21 17:35 ` [PATCHv2/RFC] " Paolo Bonzini
2014-02-24 11:58 ` [PATCHv2] " Christian Borntraeger
2014-02-24 12:02 ` 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=52D9383F.7040206@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=gleb@minantech.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mst@redhat.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;
as well as URLs for NNTP newsgroup(s).