From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Luis Pureza <pureza@student.dei.uc.pt>
Subject: Re: [Qemu-devel] Weird behavior while using the instruction counter
Date: Fri, 25 Jul 2008 00:59:47 +0100 [thread overview]
Message-ID: <200807250059.47619.paul@codesourcery.com> (raw)
In-Reply-To: <3e1533500807241058p4b8c3011r31a426a726b622d3@mail.gmail.com>
> One last try then... Would the invalidation of the original TB by
> cpu_exec_nocache() solve the problem (despite being terribly
> inefficient)?
Yes.
Paul
prev parent reply other threads:[~2008-07-24 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 10:42 [Qemu-devel] Weird behavior while using the instruction counter Luis Pureza
2008-07-24 12:44 ` Paul Brook
2008-07-24 13:54 ` Luis Pureza
2008-07-24 14:02 ` Paul Brook
[not found] ` <3e1533500807240742u488272b7x12c4429cbfbb9297@mail.gmail.com>
2008-07-24 14:49 ` Fwd: " Luis Pureza
[not found] ` <200807241556.48810.paul@codesourcery.com>
2008-07-24 15:17 ` Luis Pureza
2008-07-24 16:02 ` Paul Brook
2008-07-24 17:58 ` Luis Pureza
2008-07-24 23:59 ` Paul Brook [this message]
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=200807250059.47619.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=pureza@student.dei.uc.pt \
--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).