From: "Andreas Färber" <afaerber@suse.de>
To: "Daniel P. Berrange" <berrange@redhat.com>,
Pavel Fedin <p.fedin@samsung.com>
Cc: 'Paolo Bonzini' <pbonzini@redhat.com>,
'QEMU Developers' <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] Do not use slow [*] expansion for GPIO creation
Date: Sun, 6 Sep 2015 20:53:29 +0200 [thread overview]
Message-ID: <55EC8BA9.3030103@suse.de> (raw)
In-Reply-To: <20150731122631.GG2392@redhat.com>
Am 31.07.2015 um 14:26 schrieb Daniel P. Berrange:
> On Fri, Jul 31, 2015 at 03:23:22PM +0300, Pavel Fedin wrote:
>> Expansion of [*] suffix is very slow because index expansion is done using
>> trial and error strategy, starting every time from zero and retrying with
>> the next index until insertion succeeds. With large number of already added
>> properties this process takes huge amount of time (O(n^2) complexity).
>>
>> Some architectures (like ARM) use very large amount of IRQ pins in interrupt
>> controller models. This flaw makes machine startup extremely slow
>> (~20 seconds for ARM64 with 32 CPUs. This patch decreases this time down to
>> ~10 seconds.
>>
>> Also in qdev_init_gpio_out_named() memset() is now called only once for the
>> whole array instead of per-cell cleaning
>>
>> Signed-off-by: Pavel Fedin <p.fedin@samsung.com>
>> ---
>> hw/core/qdev.c | 21 +++++++++++++++------
>> 1 file changed, 15 insertions(+), 6 deletions(-)
>
> Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
Thanks, queued on qom-next now:
https://github.com/afaerber/qemu-cpu/commits/qom-next
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-09-06 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 12:23 [Qemu-devel] [PATCH v2] Do not use slow [*] expansion for GPIO creation Pavel Fedin
2015-07-31 12:26 ` Daniel P. Berrange
2015-09-06 18:53 ` Andreas Färber [this message]
2015-07-31 12:39 ` 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=55EC8BA9.3030103@suse.de \
--to=afaerber@suse.de \
--cc=berrange@redhat.com \
--cc=p.fedin@samsung.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.