From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] tests/bios-tables-test: Fix endianess problems when passing data to iasl
Date: Mon, 20 Nov 2017 22:32:29 +0200 [thread overview]
Message-ID: <20171120223048-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20171120175522.76bf71c3@redhat.com>
On Mon, Nov 20, 2017 at 05:55:22PM +0100, Igor Mammedov wrote:
> On Thu, 16 Nov 2017 13:17:02 +0100
> Thomas Huth <thuth@redhat.com> wrote:
>
> > The bios-tables-test was writing out files that we pass to iasl in
> > with the wrong endianness in the header when running on a big endian
> > host. So instead of storing mixed endian information in our structures,
> > let's keep everything in little endian and byte-swap it only when we
> > need a value in the code.
> >
> > Reported-by: Daniel P. Berrange <berrange@redhat.com>
> > Buglink: https://bugs.launchpad.net/qemu/+bug/1724570
> > Suggested-by: Michael S. Tsirkin <mst@redhat.com>
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> > v2: Fixed vmgenid-test which was accidentially broken in v1
> >
> > tests/acpi-utils.h | 27 +++++----------------------
> > tests/bios-tables-test.c | 42 ++++++++++++++++++++++--------------------
> > tests/vmgenid-test.c | 22 ++++++++++++----------
> > 3 files changed, 39 insertions(+), 52 deletions(-)
> >
> > diff --git a/tests/acpi-utils.h b/tests/acpi-utils.h
> > index f8d8723..d5ca5b6 100644
> > --- a/tests/acpi-utils.h
> > +++ b/tests/acpi-utils.h
> > @@ -28,24 +28,9 @@ typedef struct {
> > bool tmp_files_retain; /* do not delete the temp asl/aml */
> > } AcpiSdtTable;
> >
> > -#define ACPI_READ_FIELD(field, addr) \
> > - do { \
> > - switch (sizeof(field)) { \
> > - case 1: \
> > - field = readb(addr); \
> > - break; \
> > - case 2: \
> > - field = readw(addr); \
> > - break; \
> > - case 4: \
> > - field = readl(addr); \
> > - break; \
> > - case 8: \
> > - field = readq(addr); \
> > - break; \
> > - default: \
> > - g_assert(false); \
> > - } \
> probably it's been discussed but, why not do
> leXX_to_cpu()
> here, instead of making each place that access read field
> to do leXX_to_cpu() manually.?
>
> Beside of keeping access to structure in natural host order,
> it should also be less error-prone as field users don't
> have to worry about endianness.
Yes, I suggested that.
The issue is that we don't byte-swap all of the tables
(we can't, that would require a full ACPI parser).
So when byte-swapping we end up with a mixed host/LE
structures.
Keeping it all LE seems cleaner.
--
MST
next prev parent reply other threads:[~2017-11-20 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 12:17 [Qemu-devel] [PATCH v2] tests/bios-tables-test: Fix endianess problems when passing data to iasl Thomas Huth
2017-11-20 16:55 ` Igor Mammedov
2017-11-20 20:00 ` Thomas Huth
2017-11-20 20:32 ` Michael S. Tsirkin [this message]
2017-11-21 13:26 ` Igor Mammedov
2017-11-21 14:47 ` Michael S. Tsirkin
2017-11-21 15:58 ` Igor Mammedov
2017-11-21 16:02 ` Michael S. Tsirkin
2017-11-21 16:22 ` Igor Mammedov
2017-11-21 16:31 ` Michael S. Tsirkin
2017-11-21 16:58 ` Igor Mammedov
2017-11-21 17:09 ` Michael S. Tsirkin
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=20171120223048-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=imammedo@redhat.com \
--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.