From: Laszlo Ersek <lersek@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, pbonzini@redhat.com,
jljusten@gmail.com, afaerber@suse.de, marcel.a@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/4] i440fx-test: check firmware visibility
Date: Sat, 09 Nov 2013 02:26:02 +0100 [thread overview]
Message-ID: <527D8F2A.2000507@redhat.com> (raw)
In-Reply-To: <1383955451-20618-1-git-send-email-lersek@redhat.com>
On 11/09/13 01:04, Laszlo Ersek wrote:
> Laszlo Ersek (4):
> i440fx-test: qtest_start() should be paired with qtest_end()
> i440fx-test: give each GTest case its own qtest
> i440fx-test: generate temporary firmware blob
> i440fx-test: verify firmware under 4G and 1M, both -bios and -pflash
>
> tests/i440fx-test.c | 169 ++++++++++++++++++++++++++++++++++++++++++++++------
> 1 file changed, 152 insertions(+), 17 deletions(-)
Self-NAK
I'll have to send a new version, for at least two reasons:
- The original code (before patch #1) doesn't bother to free "data.bus"
(the retval of qpci_init_pc()). Therefore I assumed this function only
grabbed a (non-counted) reference. This is not the case: the original
code leaks it (although it exits soon after), and my patch #2 doubles
the leak.
- There's something fishy with g_assert() firing in the new test case. I
end up with a hung qemu process, reparented to init:
x86_64-softmmu/qemu-system-x86_64 \
-qtest unix:/tmp/qtest-26926.sock,nowait -qtest-log /dev/null \
-qmp unix:/tmp/qtest-26926.qmp,nowait \
-pidfile /tmp/qtest-26926.pid -machine accel=qtest \
-S -display none -pflash /tmp/fw_blob_553Y5W
I have no idea if this has to do with my unorthodox use of "-S" in
qtest, or if it's a general shortcoming of qtest (ie. aborting before
qtest_end()).
Anyway the series should be reviewable as-is, so I'll wait a bit for
comments.
Thanks!
Laszlo
prev parent reply other threads:[~2013-11-09 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 0:04 [Qemu-devel] [PATCH 0/4] i440fx-test: check firmware visibility Laszlo Ersek
2013-11-09 0:04 ` [Qemu-devel] [PATCH 1/4] i440fx-test: qtest_start() should be paired with qtest_end() Laszlo Ersek
2013-11-09 0:04 ` [Qemu-devel] [PATCH 2/4] i440fx-test: give each GTest case its own qtest Laszlo Ersek
2013-11-09 0:04 ` [Qemu-devel] [PATCH 3/4] i440fx-test: generate temporary firmware blob Laszlo Ersek
2013-11-09 0:04 ` [Qemu-devel] [PATCH 4/4] i440fx-test: verify firmware under 4G and 1M, both -bios and -pflash Laszlo Ersek
2013-11-09 1:26 ` Laszlo Ersek [this message]
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=527D8F2A.2000507@redhat.com \
--to=lersek@redhat.com \
--cc=afaerber@suse.de \
--cc=jljusten@gmail.com \
--cc=marcel.a@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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.