From: "Andreas Färber" <afaerber@suse.de>
To: Marcel Apfelbaum <marcel.a@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] qtest: fix SIGABRT handler for multiple qtest instances
Date: Thu, 27 Mar 2014 18:22:52 +0100 [thread overview]
Message-ID: <53345E6C.1090507@suse.de> (raw)
In-Reply-To: <1395930607.19041.14.camel@localhost.localdomain>
Am 27.03.2014 15:30, schrieb Marcel Apfelbaum:
> On Thu, 2014-03-27 at 15:09 +0100, Stefan Hajnoczi wrote:
>> I didn't realize some test cases use multiple qtest instances. This means we
>> need to know about all instances in order to kill our QEMU processes.
>>
>> Stefan Hajnoczi (2):
>> Revert "qtest: Fix crash if SIGABRT during qtest_init()"
>> qtest: keep list of qtest instances for SIGABRT handler
>>
>> tests/libqtest.c | 50 ++++++++++++++++++++++++++++++++++++++------------
>> tests/libqtest.h | 4 +++-
>> 2 files changed, 41 insertions(+), 13 deletions(-)
>>
>
> Looks OK to me,
>
> Reviewed-by: Marcel Apfelbaum <marcel.a@redhat.com>
Thanks, applied to qom-next:
https://github.com/afaerber/qemu-cpu/commits/qom-next
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2014-03-27 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 14:09 [Qemu-devel] [PATCH 0/2] qtest: fix SIGABRT handler for multiple qtest instances Stefan Hajnoczi
2014-03-27 14:09 ` [Qemu-devel] [PATCH 1/2] Revert "qtest: Fix crash if SIGABRT during qtest_init()" Stefan Hajnoczi
2014-03-27 14:09 ` [Qemu-devel] [PATCH 2/2] qtest: keep list of qtest instances for SIGABRT handler Stefan Hajnoczi
2014-03-27 14:30 ` [Qemu-devel] [PATCH 0/2] qtest: fix SIGABRT handler for multiple qtest instances Marcel Apfelbaum
2014-03-27 17:22 ` Andreas Färber [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=53345E6C.1090507@suse.de \
--to=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=marcel.a@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).