qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add exit notifiers.
Date: Fri, 4 Jun 2010 11:14:15 +0100	[thread overview]
Message-ID: <AANLkTilfa2xQSav4bP0VeuFBvlfYI-BOAsWKXW0gPNc5@mail.gmail.com> (raw)
In-Reply-To: <1275644132-22176-1-git-send-email-kraxel@redhat.com>

On Fri, Jun 4, 2010 at 10:35 AM, Gerd Hoffmann <kraxel@redhat.com> wrote:
> Hook up any cleanup work which needs to be done here.  Advantages over
> using atexit(3):
>
>  (1) You get passed in a pointer to the notifier.  If you embed that
>      into your state struct you can use container_of() to get get your
>      state info.
>  (2) You can unregister, say when un-plugging a device.

This looks useful to me.  Just yesterday I added an atexit(3) case for
some local hacking.

> diff --git a/roms/seabios b/roms/seabios
> index 8f469b9..7d09d0e 160000
> --- a/roms/seabios
> +++ b/roms/seabios
> @@ -1 +1 @@
> -Subproject commit 8f469b9676127ba6bb52609d89ec774e61db0ee1
> +Subproject commit 7d09d0e3ba11310e973d4302c7fcc3fc2184e04c

This hunk seems unrelated to your commit.

> diff --git a/vl.c b/vl.c
> index ac1a998..1577566 100644
> --- a/vl.c
> +++ b/vl.c
> @@ -2127,6 +2130,21 @@ static BOOL WINAPI qemu_ctrl_handler(DWORD type)
>
>  #ifndef _WIN32
>
> +void qemu_add_exit_notifier(Notifier *notify)

Why #ifndef _WIN32?  I think this patch will break _WIN32 builds.

Stefan

  reply	other threads:[~2010-06-04 10:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04  9:35 [Qemu-devel] [PATCH] Add exit notifiers Gerd Hoffmann
2010-06-04 10:14 ` Stefan Hajnoczi [this message]
2010-06-04 12:10   ` Gerd Hoffmann
  -- strict thread matches above, loose matches on Subject: below --
2010-06-04 12:08 Gerd Hoffmann
2010-06-14 20:57 ` Anthony Liguori

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=AANLkTilfa2xQSav4bP0VeuFBvlfYI-BOAsWKXW0gPNc5@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=kraxel@redhat.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).