From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Rework vm_state_change notifiers
Date: Thu, 22 Jan 2009 13:35:41 -0600 [thread overview]
Message-ID: <4978CA8D.1050205@us.ibm.com> (raw)
In-Reply-To: <4971076D.5030106@web.de>
Jan Kiszka wrote:
> [ Now tested and found working. ]
>
> Enhance the vm_state_change notifier API to pass also a change reason.
> This allows for replacing the vm_stop_cb with it and drop related code.
>
> Converting gdb_vm_stopped to gdb_vm_state_change also includes that this
> callback will now officially only handle EXCP_DEBUG and EXCP_INTERRUPT
> stop reasons. That allows to define and use new (non-zero) stop reasons
> without disturbing the gdbstub.
> ---
>
> audio/audio.c | 3 ++-
> gdbstub.c | 11 +++++------
> sysemu.h | 6 +-----
> vl.c | 29 ++++-------------------------
> 4 files changed, 12 insertions(+), 37 deletions(-)
>
>
Applied. Thanks.
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-01-22 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 22:17 [Qemu-devel] [PATCH] Rework vm_state_change notifiers Jan Kiszka
2009-01-22 17:18 ` Anthony Liguori
2009-01-22 19:35 ` Anthony Liguori [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=4978CA8D.1050205@us.ibm.com \
--to=aliguori@us.ibm.com \
--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 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).