From: Aurelien Jarno <aurelien@aurel32.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: patches@linaro.org, Paul Brook <paul@codesourcery.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target-arm: Minimal implementation of performance counters
Date: Mon, 16 May 2011 19:29:26 +0200 [thread overview]
Message-ID: <20110516172926.GA6132@volta.aurel32.net> (raw)
In-Reply-To: <BANLkTinwsj9LUbU4Mk-JTCQac-bhD=izhA@mail.gmail.com>
On Mon, May 16, 2011 at 05:37:03PM +0100, Peter Maydell wrote:
> On 16 May 2011 17:10, Paul Brook <paul@codesourcery.com> wrote:
> >> > I just spoke with Paul on IRC about this. In summary:
> >> > * for a helper to cause an exception then it has (a) to make sure CPU
> >> >
> >> > state (pc, condflags) is sync'd before the call to the helper and (b)
> >> > the helper has to be in a file with access to global env, because it
> >> > needs to call cpu_loop_exit()
> >>
> >> I don't think (a) is true. It is possible to use the same way as for
> >> load/store operations, that is call cpu_restore_state() before calling
> >> cpu_loop_exit().
> >
> > To call cpu_restore_state you need to know searched_pc. To find that you need
> > to unwind the host stack all the way back to translated code.
>
> You can do this by calling GETPC() from the top level helper function
> though, right? [OK, we'd need to move the definition out of dyngen-exec.h.]
No we don't need to move it out of dyngen-exec.h. dyngen-exec.h is
included in target-*/exec.h, as the softmmu helpers, which are included
in target-*/op_helper.c, call cpu_restore_state().
For an actual usage of cpu_restore_state() outside of the softmmu
helpers, you can have a look at target-sh4/op-helper.c, which uses this
technique for raising most exceptions, and especially the FPU ones.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2011-05-16 17:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 16:01 [Qemu-devel] [PATCH] target-arm: Minimal implementation of performance counters Peter Maydell
2011-04-22 7:23 ` Brad Hards
2011-04-22 9:48 ` Peter Maydell
2011-04-22 10:32 ` Brad Hards
2011-04-25 21:09 ` Aurelien Jarno
2011-04-25 21:59 ` Peter Maydell
2011-04-25 22:31 ` Aurelien Jarno
2011-04-25 22:35 ` Peter Maydell
2011-04-26 10:23 ` Aurelien Jarno
2011-05-06 14:32 ` Peter Maydell
2011-05-14 21:32 ` Aurelien Jarno
2011-05-14 22:01 ` Blue Swirl
2011-05-14 22:10 ` Aurelien Jarno
2011-05-16 9:59 ` Peter Maydell
2011-05-16 17:29 ` Aurelien Jarno
2011-05-16 17:51 ` Peter Maydell
2011-06-15 17:39 ` Peter Maydell
2011-05-16 16:10 ` Paul Brook
2011-05-16 16:37 ` Peter Maydell
2011-05-16 17:29 ` Aurelien Jarno [this message]
2011-05-16 17:47 ` Peter Maydell
2011-05-16 18:06 ` Aurelien Jarno
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=20110516172926.GA6132@volta.aurel32.net \
--to=aurelien@aurel32.net \
--cc=patches@linaro.org \
--cc=paul@codesourcery.com \
--cc=peter.maydell@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).