From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Rafael K. V. Maeda" <rafaelkioji@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Guest application exit point.
Date: Fri, 26 Oct 2018 14:30:27 +0100 [thread overview]
Message-ID: <87efcc25u4.fsf@linaro.org> (raw)
In-Reply-To: <784f1213-282f-14ca-4126-145dead59a77@gmail.com>
Rafael K. V. Maeda <rafaelkioji@gmail.com> writes:
> Hi,
>
> I am implementing a plugin that allocates several resources. I need to
> cleanup some of these resources when QEMU finishes executing the guest
> application. Where is the best exit point to place my cleanup
> functions?
>
> I have tried registering a function call "atexit" but it does not seem
> to work. Any suggestions? At the moment, I am looking for a solution
> for x86_64 (user emulation mode).
For linux-user have a look at preexit_cleanup() in linux-user/exit.c
>
> Kind regards,
> Rafael
--
Alex Bennée
prev parent reply other threads:[~2018-10-26 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 4:20 [Qemu-devel] Guest application exit point Rafael K. V. Maeda
2018-10-26 13:30 ` Alex Bennée [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=87efcc25u4.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rafaelkioji@gmail.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 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.