From: Paul Durrant <xadimgnik@gmail.com>
To: "'Maximilian Heyne'" <mheyne@amazon.de>,
<xen-devel@lists.xenproject.org>
Cc: 'Ian Jackson' <ian.jackson@citrix.com>
Subject: RE: [PATCH 2/3] Add exit notifiers.
Date: Wed, 8 Apr 2020 15:57:40 +0100 [thread overview]
Message-ID: <004d01d60db6$0dab56f0$290204d0$@xen.org> (raw)
In-Reply-To: <20200313123316.122003-3-mheyne@amazon.de>
> -----Original Message-----
> From: Maximilian Heyne <mheyne@amazon.de>
> Sent: 13 March 2020 12:33
> To: xen-devel@lists.xenproject.org
> Cc: Ian Jackson <ian.jackson@citrix.com>; Paul Durrant <paul@xen.org>
> Subject: [PATCH 2/3] Add exit notifiers.
>
> From: Gerd Hoffmann <kraxel@redhat.com>
>
> 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.
>
> [ v2: move code out of #ifndef _WIN32 ]
>
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> (cherry picked from commit fd42deeb4cb42f90084046e3ebdb4383953195e3)
> Signed-off-by: Maximilian Heyne <mheyne@amazon.de>
Reviewed-by: Paul Durrant <paul@xen.org>
next prev parent reply other threads:[~2020-04-08 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 12:33 [Xen-devel] [PATCH 0/3] Cleanup IOREQ server on exit Maximilian Heyne
2020-03-13 12:33 ` [Xen-devel] [PATCH 1/3] Add support for generic notifier lists Maximilian Heyne
2020-04-08 14:58 ` Paul Durrant
2020-03-13 12:33 ` [Xen-devel] [PATCH 2/3] Add exit notifiers Maximilian Heyne
2020-04-08 14:57 ` Paul Durrant [this message]
2020-03-13 12:33 ` [Xen-devel] [PATCH 3/3] xen: cleanup IOREQ server on exit Maximilian Heyne
2020-04-08 14:56 ` Paul Durrant
2020-04-07 9:16 ` [PATCH 0/3] Cleanup " Maximilian Heyne
2020-04-08 8:40 ` Paul Durrant
2020-04-21 16:35 ` Paul Durrant
2020-04-24 14:50 ` Ian Jackson
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='004d01d60db6$0dab56f0$290204d0$@xen.org' \
--to=xadimgnik@gmail.com \
--cc=ian.jackson@citrix.com \
--cc=mheyne@amazon.de \
--cc=paul@xen.org \
--cc=xen-devel@lists.xenproject.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.