All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: Access target TranslatorOps
Date: Wed, 20 Jul 2022 12:37:58 -0400	[thread overview]
Message-ID: <CAK7rcp-Ts=3JNoYRak-Zddb0NDjdgSqbGD32xFEguw0yLqydyw@mail.gmail.com> (raw)
In-Reply-To: <87y1woyxvo.fsf@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

That I know of, the TCG plugins do not allow me to feed the QEMU instance
dynamically changing opcodes. I wouldn't use TranslatorOps if I don't have
to. I want to facilitate a use case in which the contents of the target
being emulated are changing, but it is not a self modifying target. I have
to query and interact with the TCG to find out what opcodes are supported
or not.

On Wed, Jul 20, 2022 at 4:46 AM Alex Bennée <alex.bennee@linaro.org> wrote:

>
> Kenneth Adam Miller <kennethadammiller@gmail.com> writes:
>
> > Hello,
> >
> > I would like to be able to, from the linux-user/main.c, access the
> target's registered TranslatorOps instance. How would I
> > do that when 1) the TCG is correctly initialized and ready to run 2)
> > before QEMU starts to run or when it is safely paused?
>
> Why would you want to mess with the TranslatorOps?
>
> If you want to do some sort of analysis you might want to consider:
>
>   https://qemu.readthedocs.io/en/latest/devel/tcg-plugins.html
>
> At which point you can hook into any translation or individual
> instructions.
>
> --
> Alex Bennée
>

[-- Attachment #2: Type: text/html, Size: 1646 bytes --]

  reply	other threads:[~2022-07-20 16:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 19:37 Access target TranslatorOps Kenneth Adam Miller
2022-07-20  8:44 ` Alex Bennée
2022-07-20 16:37   ` Kenneth Adam Miller [this message]
2022-07-20 17:37     ` Peter Maydell
2022-07-22  5:08       ` Kenneth Adam Miller
2022-07-22  9:18         ` Alex Bennée
2022-07-22 13:48           ` Kenneth Adam Miller
2022-07-22 14:38             ` Alex Bennée
2022-07-25  9:07         ` Peter Maydell

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='CAK7rcp-Ts=3JNoYRak-Zddb0NDjdgSqbGD32xFEguw0yLqydyw@mail.gmail.com' \
    --to=kennethadammiller@gmail.com \
    --cc=alex.bennee@linaro.org \
    --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 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.