From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [RFC PATCH] s390x-linux-user
Date: Fri, 26 Jun 2009 19:18:12 +0100 [thread overview]
Message-ID: <200906261918.13448.paul@codesourcery.com> (raw)
In-Reply-To: <200906261859.03172.paul@codesourcery.com>
> No. You need the whole instruction. Which is fetched from memory, so is not
> easily available when you're checking TB flags.
> To do it this way, I think you'd need to split the instruction in two. The
> first part would load the whole instruciton from memory, or with r0, then
> store the result in an internal CPU pseudo-register to the whole
> instruction, and cuse annother TB lookup. The second would generate code
> that cleared the pseudo-register then executed the code that was stored in
> it.
>You'd have to include the whole of the pseudo-register in TB_FLAGS, and I
>doubt you've got enough bits for that.
On second reading I've spotted a way around this. Start with the two-phase
generation as described above, but make sure the TB is invalidated before the
next EXECUTE instruction is run. This means that instead of the whole
instruction in the TB flags you just need a "half way through EXECUTE" bit.
Reliably invalidating the TB may get a bit hairy, but I'm pretty sure it's
doable.
Paul
next prev parent reply other threads:[~2009-06-26 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 16:49 [Qemu-devel] [RFC PATCH] s390x-linux-user Ulrich Hecht
2009-06-26 17:17 ` Blue Swirl
2009-06-26 17:40 ` Paul Brook
2009-06-26 17:46 ` Blue Swirl
2009-06-26 17:59 ` Paul Brook
2009-06-26 18:18 ` Paul Brook [this message]
2009-06-26 18:22 ` Blue Swirl
2009-06-26 18:39 ` Paul Brook
2009-06-26 19:07 ` Stuart Brady
2009-06-26 19:24 ` Paul Brook
2009-07-03 15:11 ` Ulrich Hecht
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=200906261918.13448.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blauwirbel@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).