From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Thomas Huth <thuth@redhat.com>, Fabiano Rosas <farosas@suse.de>,
qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Pierrick Bouvier <pierrick.bouvier@linaro.org>
Subject: Re: [PATCH] tests/qtest/libqos: Avoid double swapping when using modern virtio
Date: Wed, 30 Apr 2025 10:40:36 +0200 [thread overview]
Message-ID: <c3efa112-5c79-4ead-9a0c-3e27f328cce2@linaro.org> (raw)
In-Reply-To: <20250430073343.526867-1-thuth@redhat.com>
On 30/4/25 09:33, Thomas Huth wrote:
> From: Thomas Huth <thuth@redhat.com>
>
> The logic in the qvirtio_read/write function is rather a headache,
> involving byte-swapping when the target is big endian, just to
> maybe involve another byte-swapping in the qtest_read/write
> function immediately afterwards (on the QEMU side). Let's do it in
> a more obvious way here: For virtio 1.0, we know that the values have
> to be little endian, so let's read/write the bytes in that well known
> order here.
Thanks for looking at this!
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> This also decreases our usage of qtest_big_endian() which might (or
> might not) get helpful for the universal binary one day...
>
> tests/qtest/libqos/virtio.c | 61 ++++++++++++++++++++++++++-----------
> 1 file changed, 44 insertions(+), 17 deletions(-)
>
> diff --git a/tests/qtest/libqos/virtio.c b/tests/qtest/libqos/virtio.c
> index 2e7979652fd..078adf3c8dc 100644
> --- a/tests/qtest/libqos/virtio.c
> +++ b/tests/qtest/libqos/virtio.c
> @@ -25,49 +25,76 @@
> */
> static uint16_t qvirtio_readw(QVirtioDevice *d, QTestState *qts, uint64_t addr)
> {
> - uint16_t val = qtest_readw(qts, addr);
> + uint8_t buf[2];
>
> - if (d->features & (1ull << VIRTIO_F_VERSION_1) && qtest_big_endian(qts)) {
> - val = bswap16(val);
> + if (d->features & (1ull << VIRTIO_F_VERSION_1)) {
> + qtest_memread(qts, addr, buf, sizeof(buf));
> + return (buf[1] << 8) | buf[0];
> + } else {
> + return qtest_readw(qts, addr);
> }
> - return val;
> }
What about using cpu_to_le() API?
-- >8 --
static uint16_t qvirtio_readw(QVirtioDevice *d, QTestState *qts,
uint64_t addr)
{
- uint16_t val = qtest_readw(qts, addr);
+ uint16_t val;
- if (d->features & (1ull << VIRTIO_F_VERSION_1) &&
qtest_big_endian(qts)) {
- val = bswap16(val);
+ if (d->features & (1ull << VIRTIO_F_VERSION_1)) {
+ qtest_memread(qts, addr, &val, sizeof(val));
+ cpu_to_le16s(&val);
+ } else {
+ val = qtest_readw(qts, addr);
}
+
return val;
}
---
next prev parent reply other threads:[~2025-04-30 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 7:33 [PATCH] tests/qtest/libqos: Avoid double swapping when using modern virtio Thomas Huth
2025-04-30 8:40 ` Philippe Mathieu-Daudé [this message]
2025-04-30 11:37 ` Thomas Huth
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=c3efa112-5c79-4ead-9a0c-3e27f328cce2@linaro.org \
--to=philmd@linaro.org \
--cc=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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.