qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Christoph Muellner <cmuellner@linux.com>
Cc: Alexandre Iooss <erdnaxe@crans.org>,
	Mahmoud Mandour <ma.mandourr@gmail.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] docs/tcg-plugins: document QEMU_PLUGIN behaviour
Date: Wed, 16 Mar 2022 15:00:10 +0000	[thread overview]
Message-ID: <87sfri2b76.fsf@linaro.org> (raw)
In-Reply-To: <20220316124012.1413954-1-cmuellner@linux.com>


Christoph Muellner <cmuellner@linux.com> writes:

> QEMU plugins can be loaded via command line arguments or via
> the QEMU_PLUGIN environment variable. Currently, only the first method
> is documented. Let's document QEMU_PLUGIN.
>
> Signed-off-by: Christoph Muellner <cmuellner@linux.com>
> ---
>  docs/devel/tcg-plugins.rst | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/docs/devel/tcg-plugins.rst b/docs/devel/tcg-plugins.rst
> index f93ef4fe52..ba48be18d0 100644
> --- a/docs/devel/tcg-plugins.rst
> +++ b/docs/devel/tcg-plugins.rst
> @@ -34,6 +34,10 @@ Arguments are plugin specific and can be used to modify their
>  behaviour. In this case the howvec plugin is being asked to use inline
>  ops to count and break down the hint instructions by type.
>  
> +QEMU also evaluates the environment variable ``QEMU_PLUGIN``::

You should also make it clear this only works for *-user builds of QEMU.
For system emulation you still need to use the CLI interface. 

> +
> +  QEMU_PLUGIN="file=tests/plugin/libhowec.so,inline=on,count=hint" $QEMU
> +
>  Writing plugins
>  ---------------


-- 
Alex Bennée


  parent reply	other threads:[~2022-03-16 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 12:40 [PATCH] docs/tcg-plugins: document QEMU_PLUGIN behaviour Christoph Muellner
2022-03-16 13:43 ` Mahmoud Abumandour
2022-03-16 13:58   ` Christoph Müllner
2022-03-16 15:00 ` Alex Bennée [this message]
2022-03-16 18:13   ` Christoph Müllner

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=87sfri2b76.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=cmuellner@linux.com \
    --cc=erdnaxe@crans.org \
    --cc=ma.mandourr@gmail.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).