From: Richard Henderson <richard.henderson@linaro.org>
To: Aaron Lindsay OS <aaron@os.amperecomputing.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>,
Alistair Francis <alistair.francis@xilinx.com>,
Wei Huang <wei@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Michael Spradling <mspradli@codeaurora.org>,
Digant Desai <digantd@codeaurora.org>
Subject: Re: [Qemu-devel] [PATCH v11 2/2] target/arm: Add a timer to predict PMU counter overflow
Date: Wed, 23 Jan 2019 15:38:22 -0800 [thread overview]
Message-ID: <1627fb0b-b2a0-1cb5-71b3-ddeb1f07bf8c@linaro.org> (raw)
In-Reply-To: <20190123213227.17077-3-aaron@os.amperecomputing.com>
On 1/23/19 1:32 PM, Aaron Lindsay OS wrote:
> Make PMU overflow interrupts more accurate by using a timer to predict
> when they will overflow rather than waiting for an event to occur which
> allows us to otherwise check them.
>
> Signed-off-by: Aaron Lindsay <aaron@os.amperecomputing.com>
> ---
> target/arm/cpu.c | 12 ++++++++
> target/arm/cpu.h | 10 +++++++
> target/arm/helper.c | 72 +++++++++++++++++++++++++++++++++++++++++++--
> 3 files changed, 92 insertions(+), 2 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
prev parent reply other threads:[~2019-01-23 23:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 21:32 [Qemu-devel] [PATCH v11 0/2] More fully implement ARM PMUv3 Aaron Lindsay OS
2019-01-23 21:32 ` [Qemu-devel] [PATCH v11 1/2] target/arm: Send interrupts on PMU counter overflow Aaron Lindsay OS
2019-01-23 23:37 ` Richard Henderson
2019-01-24 15:53 ` Aaron Lindsay OS
2019-01-23 21:32 ` [Qemu-devel] [PATCH v11 2/2] target/arm: Add a timer to predict " Aaron Lindsay OS
2019-01-23 23:38 ` Richard Henderson [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=1627fb0b-b2a0-1cb5-71b3-ddeb1f07bf8c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=aaron@os.amperecomputing.com \
--cc=alistair.francis@xilinx.com \
--cc=crosthwaite.peter@gmail.com \
--cc=digantd@codeaurora.org \
--cc=mspradli@codeaurora.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wei@redhat.com \
/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).