From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] Update qemu-tech.texi, needs verification
Date: Mon, 6 Oct 2008 21:09:26 +0200 [thread overview]
Message-ID: <fb249edb0810061209y861a311h105e5d6718e9f680@mail.gmail.com> (raw)
In-Reply-To: <761ea48b0810061119y1d64b16cp4180bfa0b917567c@mail.gmail.com>
I believe this piece is still valid:
-The most portable code uses an indirect jump. An indirect jump makes
-it easier to make the jump target modification atomic. On some host
-architectures (such as x86 or PowerPC), the @code{JUMP} opcode is
-directly patched so that the block chaining has no overhead.
-
BTW I wouldn't avoid the term TCG ops, it's sometimes clearer than operations.
Cheers
next prev parent reply other threads:[~2008-10-06 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 8:44 [Qemu-devel] [PATCH, RFC] Update qemu-tech.texi, needs verification Blue Swirl
2008-10-05 12:26 ` Edgar E. Iglesias
2008-10-05 12:55 ` Thiemo Seufer
2008-10-05 17:28 ` malc
2008-10-06 13:26 ` Paul Brook
2008-10-06 17:53 ` Blue Swirl
2008-10-06 18:02 ` Paul Brook
2008-10-06 18:19 ` Laurent Desnogues
2008-10-06 19:09 ` andrzej zaborowski [this message]
2008-10-10 6:56 ` Kirill A. Shutemov
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=fb249edb0810061209y861a311h105e5d6718e9f680@mail.gmail.com \
--to=balrogg@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).