From: Jack Biggs <john.biggs@epfl.ch>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Question about gen_jmp_tb
Date: Mon, 02 Jun 2014 12:15:02 +0200 [thread overview]
Message-ID: <538C4EA6.6020306@epfl.ch> (raw)
In-Reply-To: <87wqczsll1.fsf@linaro.org>
> When you say arbitrary code what do you mean? Are you wanting to put
> backend specific code there or a common post-amble of tcg ops? Can you
> give a bit more detail about your use case?
I'm trying to add a clock-synchronization library so that I can have two
(or more) instances of QEMU run in a synchronized (deterministic)
fashion. The "arbitrary code" is more or less a function call (i.e.,
callq) instruction to a function that uses shared semaphores to block
execution.
Jack
next prev parent reply other threads:[~2014-06-02 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <538847AC.6040108@epfl.ch>
[not found] ` <5388B101.4010809@twiddle.net>
2014-06-02 8:16 ` [Qemu-devel] Question about gen_jmp_tb Jack Biggs
2014-06-02 9:32 ` Alex Bennée
2014-06-02 10:15 ` Jack Biggs [this message]
2014-06-02 10:47 ` Peter Maydell
2014-06-02 10:53 ` Jack Biggs
2014-06-02 10:56 ` 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=538C4EA6.6020306@epfl.ch \
--to=john.biggs@epfl.ch \
--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 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).