From: Aurelien Jarno <aurelien@aurel32.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paul Brook <paul@codesourcery.com>,
qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] target-arm: Minimal implementation of performance counters
Date: Tue, 26 Apr 2011 12:23:07 +0200 [thread overview]
Message-ID: <20110426102307.GA20532@volta.aurel32.net> (raw)
In-Reply-To: <BANLkTimuj6nhAuxOo+-dmJqYFhkSuXUcKg@mail.gmail.com>
On Mon, Apr 25, 2011 at 11:35:54PM +0100, Peter Maydell wrote:
> On 25 April 2011 23:31, Aurelien Jarno <aurelien@aurel32.net> wrote:
> > On Mon, Apr 25, 2011 at 10:59:52PM +0100, Peter Maydell wrote:
> >> On 25 April 2011 22:09, Aurelien Jarno <aurelien@aurel32.net> wrote:
> >> > Instead of having this complex test for all cp15 access, but only for
> >> > catching a few access to performance registers, wouldn't it make more
> >> > sense to have this test and an exception triggering directly in
> >> > helper.c?
> >>
> >> That was what my first design did, but in discussions on IRC
> >> with Paul Brook he basically said that you can't generate an
> >> exception in the helper routine, you have to either generate
> >> runtime code to do the test or throw away the TBs. Unfortunately
> >> I forget the exact rationale, so I've cc'd Paul to remind me :-)
> >
> > This is something strange, plenty of targets are raising exceptions from
> > helpers without any problem.
>
> You'd at minimum need to move the cp15 helper functions to a different
> file, they're currently in helper.c which doesn't get compiled
> with access to the global 'env' register. But I got the impression
> there was something more significant than that.
>
I agree, but it's something that has to be done sooner or later anyway.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2011-04-26 10:23 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 [this message]
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
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=20110426102307.GA20532@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.