From: "Alex Bennée" <alex.bennee@linaro.org>
To: Yonggang Luo <luoyonggang@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v6 0/5] Enable plugin support on msys2/mingw
Date: Fri, 12 Mar 2021 17:15:00 +0000 [thread overview]
Message-ID: <874khge1j1.fsf@linaro.org> (raw)
In-Reply-To: <20201013002806.1447-1-luoyonggang@gmail.com>
Yonggang Luo <luoyonggang@gmail.com> writes:
> V5-V6=0D
> Skip merged patches=0D
Queued to 1 and 2 into plugins/next, thanks.
> =0D
> V3-V4=0D
> Split plugin: Fixes typo in qemu-plugin.h out=0D
> Trying to explain the design of=0D
> plugin: Getting qemu-plugin works under win32.=0D
> =0D
> V1-V2=0D
> 1. Fixes review comments=0D
> 2. Increase QEMU_PLUGIN_VERSION to 1 for compat QEMU_PLUGIN_VERSION 0=0D
> 3. Revise the loader to support for version 0 and 1=0D
> 4. By export function qemu_plugin_initialize in plugin, and call it in load=
> er=3D=0D
> , so=0D
> we have no need call it in every plugin. And also provide a standard impl=
> em=3D=0D
> entation,=0D
> anyway, use can also override it.=0D
> =0D
> Add this feature on msys2/mingw by using glib provided cross-platform dlsym=
> f=3D=0D
> unctional.=0D
> =0D
> Yonggang Luo (5):=0D
> plugins: getting qemu_plugin_get_hwaddr only expose one function=0D
> prototype=0D
> plugins: Fixes typo in qemu-plugin.h=0D
> plugins: Getting qemu-plugin works under win32.=0D
> plugins: Getting qemu-plugin.h can be included in multiple source file=0D
> cirrus: Enable plugins in cirrus for windows=0D
> =0D
> .cirrus.yml | 1 +=0D
> Makefile | 1 -=0D
> configure | 71 ------------=0D
> contrib/plugins/hotblocks.c | 1 +=0D
> contrib/plugins/hotpages.c | 1 +=0D
> contrib/plugins/howvec.c | 1 +=0D
> contrib/plugins/lockstep.c | 1 +=0D
> include/qemu/qemu-plugin.h | 208 +++++++++++++++++++++++++++--------=0D
> meson.build | 6 +-=0D
> plugins/api.c | 113 ++++++++++---------=0D
> plugins/core.c | 16 ++-=0D
> plugins/loader.c | 50 ++++++++-=0D
> plugins/meson.build | 10 +-=0D
> plugins/plugin.h | 1 +=0D
> plugins/qemu-plugins.symbols | 40 -------=0D
> tests/plugin/bb.c | 1 +=0D
> tests/plugin/empty.c | 1 +=0D
> tests/plugin/insn.c | 1 +=0D
> tests/plugin/mem.c | 1 +=0D
> 19 files changed, 298 insertions(+), 227 deletions(-)=0D
> delete mode 100644 plugins/qemu-plugins.symbols=0D
> =0D
> --=3D20=0D
> 2.28.0.windows.1=0D
> =0D
--
Alex Bennée
prev parent reply other threads:[~2021-03-12 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 0:28 [PATCH v6 0/5] Enable plugin support on msys2/mingw Yonggang Luo
2020-10-13 0:28 ` [PATCH v6 1/5] plugins: getting qemu_plugin_get_hwaddr only expose one function prototype Yonggang Luo
2020-10-13 0:28 ` [PATCH v6 2/5] plugins: Fixes typo in qemu-plugin.h Yonggang Luo
2020-10-13 0:28 ` [PATCH v6 3/5] plugins: Getting qemu-plugin works under win32 Yonggang Luo
2020-10-13 0:28 ` [PATCH v6 4/5] plugins: Getting qemu-plugin.h can be included in multiple source file Yonggang Luo
2020-10-13 0:28 ` [PATCH v6 5/5] cirrus: Enable plugins in cirrus for windows Yonggang Luo
2020-10-13 0:39 ` [PATCH v6 0/5] Enable plugin support on msys2/mingw no-reply
2021-03-12 17:15 ` 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=874khge1j1.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=luoyonggang@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).