qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Robert Henry <robhenry@microsoft.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"erdnaxe@crans.org" <erdnaxe@crans.org>,
	"qemu-discuss@nongnu.org" <qemu-discuss@nongnu.org>,
	"ma.mandourr@gmail.com" <ma.mandourr@gmail.com>,
	"Julio Gago Alonso" <Julio.Gago@microsoft.com>,
	"Vinson Young" <Vinson.Young@microsoft.com>,
	"Toni Juan" <Toni.Juan@microsoft.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>
Subject: Re: QEMU plugin past, present and future examples
Date: Wed, 12 Jun 2024 14:27:10 +0200	[thread overview]
Message-ID: <ef483031-499e-40ed-a2e4-67350a702069@linaro.org> (raw)
In-Reply-To: <DS0PR21MB3907C54A543A8540AAD1DA8CD6C72@DS0PR21MB3907.namprd21.prod.outlook.com>

Hi Robert,

On 11/6/24 18:53, Robert Henry wrote:
> QEMU plugin experts:
> 
> A few years I wrote a plugin for QEMU that saves the instruction stream 
> to a file for offline analysis.  QEMU could fly along at about 10MIPS 
> and the disk would soon fill up with large protobuf files.  The offline 
> analysis runs at about 50kIPS, and does a variety of analyses, such as 
> simple disassembly that includes kernel source file name and line 
> number, popcount analyses of displacements, Markov chain probabilities, 
> etc.
> 
> To get the speed up, I narrowed the scope of the plugin to only work 
> with ARM64, although there's still a lot of support for x86_64.
> 
>   I have not kept pace with the QEMU plugin API changes, if any, to 
> support vectors, masks, and so forth.
> 
>   *
>     I did this work for my current employer, Microsoft.
>   *
>     I will retire in 3 weeks.`
>   *
>     Nobody in Microsoft seems interested in picking up this work.
>   *
>     I'm working with our open source office to get this more widely
>     released.
> 
> The plugin code that runs in QEMU is complex, but relatively 
> straightforward. The offline analysis code is idiosyncratic and somewhat 
> fragile.

Thanks for trying to share your work with the community!

> Do the QEMU plugin experts (cc'ed here mostly) have a suggestion for 
> which public git repository service has worked "best" for other plugins 
> that are not currently part of the QEMU source tree?

Cc'ing few more developer familiar with plugins and the source code
organisation.

> I will try to get a repo in github.com/microsoft/ but I do not know what 
> is involved.
> 
> Robert Henry
> robhenry@microsoft.com
> rrh.henry@gmail.com
> https://github.com/robertHenry6bev <https://github.com/robertHenry6bev>

Regards,

Phil.


           reply	other threads:[~2024-06-12 12:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <DS0PR21MB3907C54A543A8540AAD1DA8CD6C72@DS0PR21MB3907.namprd21.prod.outlook.com>]

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=ef483031-499e-40ed-a2e4-67350a702069@linaro.org \
    --to=philmd@linaro.org \
    --cc=Julio.Gago@microsoft.com \
    --cc=Toni.Juan@microsoft.com \
    --cc=Vinson.Young@microsoft.com \
    --cc=alex.bennee@linaro.org \
    --cc=erdnaxe@crans.org \
    --cc=ma.mandourr@gmail.com \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=robhenry@microsoft.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 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).