From: Li Qiang <liq3ea@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Li Qiang" <liq3ea@163.com>,
lvivier@redhat.com, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Qemu Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 3/4] tests: fw_cfg: add reboot_timeout test case
Date: Wed, 24 Apr 2019 22:08:59 +0800 [thread overview]
Message-ID: <CAKXe6SJ5iqXTMZMKQG4X0r1dDKNCBq06hcDPVzzUupCD=nH4zw@mail.gmail.com> (raw)
In-Reply-To: <6dd699b1-f24d-743b-343e-f1df6c8672b9@redhat.com>
Thomas Huth <thuth@redhat.com> 于2019年4月24日周三 下午3:31写道:
> On 24/04/2019 03.16, Li Qiang wrote:
> >
> > Thomas Huth <thuth@redhat.com <mailto:thuth@redhat.com>> 于2019年4月24日
> > 周三 上午12:29写道:
> >
> > On 20/04/2019 12.00, Li Qiang wrote:
> > > Signed-off-by: Li Qiang <liq3ea@163.com <mailto:liq3ea@163.com>>
> > > ---
> > > tests/fw_cfg-test.c | 19 +++++++++++++++++++
> > > 1 file changed, 19 insertions(+)
> > >
> > > diff --git a/tests/fw_cfg-test.c b/tests/fw_cfg-test.c
> > > index c22503619f..9f75dbb5f4 100644
> > > --- a/tests/fw_cfg-test.c
> > > +++ b/tests/fw_cfg-test.c
> > > @@ -174,6 +174,24 @@ static void test_fw_cfg_boot_menu(void)
> > > qtest_quit(s);
> > > }
> > >
> > > +static void test_fw_cfg_reboot_timeout(void)
> > > +{
> > > + QFWCFG *fw_cfg;
> > > + QTestState *s;
> > > + uint32_t reboot_timeout = 0;
> > > + size_t filesize;
> > > +
> > > + s = qtest_init("-boot reboot-timeout=15");
> > > + fw_cfg = pc_fw_cfg_init(s);
> > > +
> > > + filesize = qfw_cfg_get_file(fw_cfg, "etc/boot-fail-wait",
> > > + &reboot_timeout, sizeof(reboot_timeout));
> > > + g_assert_cmpint(filesize, ==, sizeof(reboot_timeout));
> > > + g_assert_cmpint(reboot_timeout, ==, 15);
> >
> > Is this endianess-safe? Or do you need to byteswap reboot_timeout if
> the
> > host and guest endianess does not match?
> >
> > Good question!
> >
> > IIUC, the qemu fw_cfg store the 'file' entry data just in byte stream.
> > So there is no need
> > to consider the file's endianess. If when the file entry is stored
> > without considering endianess,
> > it will be ok to ignore the endianess. So for this patch, the
> > 'reboot_timeout' is ok as when we stored
> > it we don't consider endianess. But for 'splash-time', when we stored
> > it we convert it to little endian
> > so when we fetches it, we should also convert it from little endian to
> > cpu-endian.
>
> I just gave these patches a try on a big endian host, and the test fails
> indeed:
>
>
Hi Thomas,
I have sent out a revision patchset, could you please also try the new in
the big endian host.
Thanks,
Li Qiang
> $ QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 tests/fw_cfg-test
> /x86_64/fw_cfg/signature: OK
> /x86_64/fw_cfg/id: OK
> /x86_64/fw_cfg/uuid: OK
> /x86_64/fw_cfg/ram_size: OK
> /x86_64/fw_cfg/nographic: OK
> /x86_64/fw_cfg/nb_cpus: OK
> /x86_64/fw_cfg/max_cpus: OK
> /x86_64/fw_cfg/numa: OK
> /x86_64/fw_cfg/boot_menu: OK
> /x86_64/fw_cfg/reboot_timeout: **
> ERROR:tests/fw_cfg-test.c:190:test_fw_cfg_reboot_timeout: assertion
> failed (reboot_timeout == 15): (0 == 15)
> Aborted
>
> => it also fails for reboot_timeout already, not only for splash_time.
>
> > So I think we can have following choose:
> >
> > 1. Don't consider the endianess, this is ok when emaulated target and
> > host target has the same endianess.
>
> Sorry, but that's not a real choice. qtests must also work when you e.g.
> run qemu-system-x86_64 on a big endian host.
>
> Thomas
>
WARNING: multiple messages have this Message-ID (diff)
From: Li Qiang <liq3ea@gmail.com>
To: Thomas Huth <thuth@redhat.com>
Cc: lvivier@redhat.com, "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Li Qiang" <liq3ea@163.com>,
"Qemu Developers" <qemu-devel@nongnu.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/4] tests: fw_cfg: add reboot_timeout test case
Date: Wed, 24 Apr 2019 22:08:59 +0800 [thread overview]
Message-ID: <CAKXe6SJ5iqXTMZMKQG4X0r1dDKNCBq06hcDPVzzUupCD=nH4zw@mail.gmail.com> (raw)
Message-ID: <20190424140859.s9ty7KCwFr9ZC_qv6NGMBDH8DXoHWyaWCTgpxLFsPl8@z> (raw)
In-Reply-To: <6dd699b1-f24d-743b-343e-f1df6c8672b9@redhat.com>
Thomas Huth <thuth@redhat.com> 于2019年4月24日周三 下午3:31写道:
> On 24/04/2019 03.16, Li Qiang wrote:
> >
> > Thomas Huth <thuth@redhat.com <mailto:thuth@redhat.com>> 于2019年4月24日
> > 周三 上午12:29写道:
> >
> > On 20/04/2019 12.00, Li Qiang wrote:
> > > Signed-off-by: Li Qiang <liq3ea@163.com <mailto:liq3ea@163.com>>
> > > ---
> > > tests/fw_cfg-test.c | 19 +++++++++++++++++++
> > > 1 file changed, 19 insertions(+)
> > >
> > > diff --git a/tests/fw_cfg-test.c b/tests/fw_cfg-test.c
> > > index c22503619f..9f75dbb5f4 100644
> > > --- a/tests/fw_cfg-test.c
> > > +++ b/tests/fw_cfg-test.c
> > > @@ -174,6 +174,24 @@ static void test_fw_cfg_boot_menu(void)
> > > qtest_quit(s);
> > > }
> > >
> > > +static void test_fw_cfg_reboot_timeout(void)
> > > +{
> > > + QFWCFG *fw_cfg;
> > > + QTestState *s;
> > > + uint32_t reboot_timeout = 0;
> > > + size_t filesize;
> > > +
> > > + s = qtest_init("-boot reboot-timeout=15");
> > > + fw_cfg = pc_fw_cfg_init(s);
> > > +
> > > + filesize = qfw_cfg_get_file(fw_cfg, "etc/boot-fail-wait",
> > > + &reboot_timeout, sizeof(reboot_timeout));
> > > + g_assert_cmpint(filesize, ==, sizeof(reboot_timeout));
> > > + g_assert_cmpint(reboot_timeout, ==, 15);
> >
> > Is this endianess-safe? Or do you need to byteswap reboot_timeout if
> the
> > host and guest endianess does not match?
> >
> > Good question!
> >
> > IIUC, the qemu fw_cfg store the 'file' entry data just in byte stream.
> > So there is no need
> > to consider the file's endianess. If when the file entry is stored
> > without considering endianess,
> > it will be ok to ignore the endianess. So for this patch, the
> > 'reboot_timeout' is ok as when we stored
> > it we don't consider endianess. But for 'splash-time', when we stored
> > it we convert it to little endian
> > so when we fetches it, we should also convert it from little endian to
> > cpu-endian.
>
> I just gave these patches a try on a big endian host, and the test fails
> indeed:
>
>
Hi Thomas,
I have sent out a revision patchset, could you please also try the new in
the big endian host.
Thanks,
Li Qiang
> $ QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64 tests/fw_cfg-test
> /x86_64/fw_cfg/signature: OK
> /x86_64/fw_cfg/id: OK
> /x86_64/fw_cfg/uuid: OK
> /x86_64/fw_cfg/ram_size: OK
> /x86_64/fw_cfg/nographic: OK
> /x86_64/fw_cfg/nb_cpus: OK
> /x86_64/fw_cfg/max_cpus: OK
> /x86_64/fw_cfg/numa: OK
> /x86_64/fw_cfg/boot_menu: OK
> /x86_64/fw_cfg/reboot_timeout: **
> ERROR:tests/fw_cfg-test.c:190:test_fw_cfg_reboot_timeout: assertion
> failed (reboot_timeout == 15): (0 == 15)
> Aborted
>
> => it also fails for reboot_timeout already, not only for splash_time.
>
> > So I think we can have following choose:
> >
> > 1. Don't consider the endianess, this is ok when emaulated target and
> > host target has the same endianess.
>
> Sorry, but that's not a real choice. qtests must also work when you e.g.
> run qemu-system-x86_64 on a big endian host.
>
> Thomas
>
next prev parent reply other threads:[~2019-04-24 14:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-20 10:00 [Qemu-devel] [PATCH 0/4] fw_cfg_test refactor and add two test cases Li Qiang
2019-04-20 10:00 ` Li Qiang
2019-04-20 10:00 ` [Qemu-devel] [PATCH 1/4] tests: refactor fw_cfg_test Li Qiang
2019-04-20 10:00 ` Li Qiang
2019-04-23 16:25 ` Thomas Huth
2019-04-23 16:25 ` Thomas Huth
2019-04-20 10:00 ` [Qemu-devel] [PATCH 2/4] tests: fw_cfg: add a function to get the fw_cfg file Li Qiang
2019-04-20 10:00 ` Li Qiang
2019-04-23 16:26 ` Thomas Huth
2019-04-23 16:26 ` Thomas Huth
2019-04-20 10:00 ` [Qemu-devel] [PATCH 3/4] tests: fw_cfg: add reboot_timeout test case Li Qiang
2019-04-20 10:00 ` Li Qiang
2019-04-23 16:29 ` Thomas Huth
2019-04-23 16:29 ` Thomas Huth
2019-04-24 1:16 ` Li Qiang
2019-04-24 1:16 ` Li Qiang
2019-04-24 7:30 ` Thomas Huth
2019-04-24 7:30 ` Thomas Huth
2019-04-24 7:41 ` Li Qiang
2019-04-24 7:41 ` Li Qiang
2019-04-24 14:08 ` Li Qiang [this message]
2019-04-24 14:08 ` Li Qiang
2019-04-25 8:15 ` Gerd Hoffmann
2019-04-25 8:15 ` Gerd Hoffmann
2019-04-25 8:29 ` Li Qiang
2019-04-25 8:29 ` Li Qiang
2019-04-25 10:23 ` Philippe Mathieu-Daudé
2019-04-25 10:23 ` Philippe Mathieu-Daudé
2019-04-26 16:57 ` Laszlo Ersek
2019-04-26 16:57 ` Laszlo Ersek
2019-04-26 16:53 ` Laszlo Ersek
2019-04-26 16:53 ` Laszlo Ersek
2019-04-20 10:00 ` [Qemu-devel] [PATCH 4/4] tests: fw_cfg: add splash time " Li Qiang
2019-04-20 10:00 ` Li Qiang
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='CAKXe6SJ5iqXTMZMKQG4X0r1dDKNCBq06hcDPVzzUupCD=nH4zw@mail.gmail.com' \
--to=liq3ea@gmail.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=liq3ea@163.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@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 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).