From: "Emilio G. Cota" <cota@braap.org>
To: qemu-devel@nongnu.org
Cc: "Lluís Vilanova" <vilanova@ac.upc.edu>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [RFC 2/6] plugin: add initial plugin support
Date: Wed, 6 Sep 2017 16:41:02 -0400 [thread overview]
Message-ID: <20170906204102.GA25558@flamenco> (raw)
In-Reply-To: <1504729728-23279-3-git-send-email-cota@braap.org>
On Wed, Sep 06, 2017 at 16:28:44 -0400, Emilio G. Cota wrote:
> --- /dev/null
> +++ b/plugin.c
> @@ -0,0 +1,519 @@
(snip)
> + /*
> + * @lock protects the struct as well as ctx->uninstalling.
> + * The lock must be acquired by all API ops. Since some API ops
> + * call plugin code repeatedly (e.g. vcpu_for_each), we keep
> + * a counter to allow for recursive acquisitions.
> + */
> + QemuMutex lock;
This comment is outdated. The lock is not recursive anymore (it used to be).
E.
next prev parent reply other threads:[~2017-09-06 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 20:28 [Qemu-devel] [RFC 0/6] initial plugin support Emilio G. Cota
2017-09-06 20:28 ` [Qemu-devel] [RFC 1/6] tcg: keep a pointer to the current TB in TCGContext Emilio G. Cota
2017-09-06 20:28 ` [Qemu-devel] [RFC 2/6] plugin: add initial plugin support Emilio G. Cota
2017-09-06 20:41 ` Emilio G. Cota [this message]
2017-09-26 4:27 ` Thomas Huth
2017-09-06 20:28 ` [Qemu-devel] [RFC 3/6] configure: add --enable-plugins Emilio G. Cota
2017-09-06 20:28 ` [Qemu-devel] [RFC 4/6] Makefile: install qemu-api.h as include/qemu-plugin.h Emilio G. Cota
2017-09-06 20:28 ` [Qemu-devel] [RFC 5/6] vl: support -plugin option Emilio G. Cota
2017-09-06 20:28 ` [Qemu-devel] [RFC 6/6] linux-user: " Emilio G. Cota
2017-09-14 14:33 ` [Qemu-devel] [RFC 0/6] initial plugin support Peter Maydell
2017-09-18 14:59 ` Stefan Hajnoczi
2017-09-18 15:05 ` Peter Maydell
2017-09-19 9:51 ` Stefan Hajnoczi
2017-09-25 18:12 ` Lluís Vilanova
2017-09-26 4:22 ` Thomas Huth
2017-09-26 9:32 ` Stefan Hajnoczi
2017-09-26 16:15 ` Emilio G. Cota
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=20170906204102.GA25558@flamenco \
--to=cota@braap.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vilanova@ac.upc.edu \
/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.