From: "Michael S. Tsirkin" <mst@redhat.com>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-ppc@nongnu.org, "Stefano Garzarella" <sgarzare@redhat.com>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>
Subject: Re: [PATCH v4 0/9] single-binary: hw/virtio
Date: Thu, 5 Feb 2026 01:43:39 -0500 [thread overview]
Message-ID: <20260205014101-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <571ef1d1-88f1-4f4c-9800-00f114a85e02@linaro.org>
On Wed, Feb 04, 2026 at 09:27:10PM -0800, Pierrick Bouvier wrote:
> On 2/3/26 12:56 PM, Pierrick Bouvier wrote:
> > This series eliminates target specifics in hw/virtio and replace them with
> > runtime functions where needed.
> >
> > Performance has been measured with this automated fio benchmark, with
> > original instructions from Stefan [1].
> >
> > $ git clone https://github.com/pbo-linaro/qemu-linux-stack -b x86_64_io_benchmark
> > $ cd qemu-linux-stack
> > $ ./build.sh
> > $ ./run.sh /path/to/qemu-system-x86_64
> >
> > [1] https://lore.kernel.org/qemu-devel/20260202185233.GC405548@fedora/
> >
> > Results are on 20 runs and expressed in kIOPS:
> > reference: mean=239.2 std_dev=3.48
> > with_series: mean=238.5 std_dev=3.46
> >
> > Performance is on par, and within standard deviation.
> >
>
> Does it look better to you Michael?
>
> Regards,
> Pierrick
better for sure. is there a reason you dropped stefanha
from CC? he suggested these tests...
--
MST
next prev parent reply other threads:[~2026-02-05 6:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 20:56 [PATCH v4 0/9] single-binary: hw/virtio Pierrick Bouvier
2026-02-03 20:56 ` [PATCH v4 1/9] hw/virtio: Constify virtio_is_big_endian() argument Pierrick Bouvier
2026-02-03 20:56 ` [PATCH v4 2/9] hw/virtio: Introduce VirtIODevice::access_is_big_endian boolean field Pierrick Bouvier
2026-02-03 20:56 ` [PATCH v4 3/9] hw/virtio: Use VirtIODevice::access_is_big_endian field Pierrick Bouvier
2026-02-03 22:11 ` Philippe Mathieu-Daudé
2026-02-03 22:38 ` BALATON Zoltan
2026-02-03 22:45 ` Pierrick Bouvier
2026-02-06 4:37 ` Pierrick Bouvier
2026-02-03 20:56 ` [PATCH v4 4/9] target-info: add target_base_ppc, target_ppc and target_ppc64 Pierrick Bouvier
2026-02-03 20:56 ` [PATCH v4 5/9] include/hw/virtio/virtio-access.h: remove target specifics define Pierrick Bouvier
2026-02-04 2:10 ` Richard Henderson
2026-02-04 16:37 ` Pierrick Bouvier
2026-02-05 18:54 ` Pierrick Bouvier
2026-02-03 20:56 ` [PATCH v4 6/9] include/hw/ppc/spapr: extract SPAPR_MAX_RAM_SLOTS in a new header Pierrick Bouvier
2026-02-03 20:56 ` [PATCH v4 7/9] hw/virtio/vhost-user: make compilation unit common Pierrick Bouvier
2026-02-03 20:56 ` [PATCH v4 8/9] hw/virtio/virtio-qmp: " Pierrick Bouvier
2026-02-03 20:56 ` [PATCH v4 9/9] hw/virtio/: make all compilation units common Pierrick Bouvier
2026-02-05 5:27 ` [PATCH v4 0/9] single-binary: hw/virtio Pierrick Bouvier
2026-02-05 6:43 ` Michael S. Tsirkin [this message]
2026-02-05 17:17 ` Pierrick Bouvier
2026-02-05 18:38 ` Stefan Hajnoczi
2026-02-06 4:38 ` Pierrick Bouvier
2026-02-06 22:21 ` Pierrick Bouvier
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=20260205014101-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sgarzare@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 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.