From: "Kinsella, Ray" <mdr@ashroe.eu>
To: Gal Hammer <ghammer@redhat.com>, qemu-devel@nongnu.org
Cc: mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/3 v2] virtio: improve virtio devices initialization time
Date: Tue, 16 Jan 2018 15:40:21 +0000 [thread overview]
Message-ID: <4a649398-c643-33d2-f4ec-cd031b963e2f@ashroe.eu> (raw)
In-Reply-To: <1515924416-9266-1-git-send-email-ghammer@redhat.com>
Hi Gal,
Brilliant - will test this in the next day or two.
Hopefully this will help resolve the issues I reported last summer.
http://lists.nongnu.org/archive/html/qemu-devel/2017-07/msg05268.html
Ray K
On 14/01/2018 10:06, Gal Hammer wrote:
> A bug was reported about a very slow boot time and a 100% CPU usage of
> both Windows and Linux guests when running a VM with multiple
> virtio-serial devices (https://bugzilla.redhat.com/1528588).
>
> For example, running a VM with 25 virtio-serial devices, each one with
> max_ports=511, could have a boot time of around 30 minutes. With this
> patch (and another patch to kvm) the boot time is reduced to
> approximately 3 minutes.
>
> The patch wraps all the changes made to the Memory Regions during the
> eventfd registrations in a memory regions transaction. I had to add a
> cleanup callback function to the EventNotifier struct, so it will be
> possible to use a transaction in the shutdown code path as well.
>
> Gal Hammer (3):
> qemu: add a cleanup callback function to EventNotifier
> virtio: postpone the execution of event_notifier_cleanup function
> virtio: improve virtio devices initialization time
>
> accel/kvm/kvm-all.c | 4 ++++
> hw/virtio/virtio-bus.c | 19 +++++++++++--------
> hw/virtio/virtio.c | 5 +++++
> include/qemu/event_notifier.h | 1 +
> util/event_notifier-posix.c | 5 ++++-
> util/event_notifier-win32.c | 2 ++
> 6 files changed, 27 insertions(+), 9 deletions(-)
>
next prev parent reply other threads:[~2018-01-16 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 10:06 [Qemu-devel] [PATCH 0/3 v2] virtio: improve virtio devices initialization time Gal Hammer
2018-01-14 10:06 ` [Qemu-devel] [PATCH 1/3] qemu: add a cleanup callback function to EventNotifier Gal Hammer
2018-01-14 10:06 ` [Qemu-devel] [PATCH 2/3] virtio: postpone the execution of event_notifier_cleanup function Gal Hammer
2018-01-22 11:53 ` Michal Privoznik
2018-01-22 17:35 ` Marc-André Lureau
2018-01-23 15:16 ` Michael S. Tsirkin
2018-01-14 10:06 ` [Qemu-devel] [PATCH 3/3] virtio: improve virtio devices initialization time Gal Hammer
2018-01-16 15:40 ` Kinsella, Ray [this message]
2018-01-17 9:28 ` [Qemu-devel] [PATCH 0/3 v2] " Gal Hammer
2018-01-17 10:53 ` Kinsella, Ray
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=4a649398-c643-33d2-f4ec-cd031b963e2f@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=ghammer@redhat.com \
--cc=mst@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 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).