From: Aaron Lindsay <aclindsa@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Aaron Lindsay <aaron@amperecomputing.com>,
qemu-arm <qemu-arm@nongnu.org>,
Alistair Francis <alistair.francis@xilinx.com>,
Wei Huang <wei@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Michael Spradling <michael.spradling@amperecomputing.com>
Subject: Re: [Qemu-devel] [PATCH v5 12/13] target/arm: Mark PMINTENSET accesses as possibly doing IO
Date: Mon, 27 Aug 2018 10:48:17 -0400 [thread overview]
Message-ID: <20180827144809.GA3671@okra.localdomain> (raw)
In-Reply-To: <CAFEAcA-dBq8vTB8sqxJ7_FjeHrteS58J-+2i_iYFH6iH6GWXMw@mail.gmail.com>
On Jun 28 17:25, Peter Maydell wrote:
> Shouldn't PMINTENCLR and PMINTENCLR_EL1 also be ARM_CP_IO ?
Yes, that was an oversight - I've added a patch addressing this for v6.
-Aaron
next prev parent reply other threads:[~2018-08-27 14:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 20:32 [Qemu-devel] [PATCH v5 00/13] More fully implement ARM PMUv3 Aaron Lindsay
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 01/13] target/arm: Reorganize PMCCNTR accesses Aaron Lindsay
2018-06-28 16:40 ` Peter Maydell
2018-08-28 20:03 ` Aaron Lindsay
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 02/13] target/arm: Filter cycle counter based on PMCCFILTR_EL0 Aaron Lindsay
2018-07-17 15:49 ` Peter Maydell
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 03/13] target/arm: Allow AArch32 access for PMCCFILTR Aaron Lindsay
2018-06-28 16:30 ` Peter Maydell
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 04/13] target/arm: Add ARM_FEATURE_V7VE for v7 Virtualization Extensions Aaron Lindsay
2018-06-28 16:20 ` Peter Maydell
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 05/13] target/arm: Remove redundant DIV detection for KVM Aaron Lindsay
2018-06-28 16:21 ` Peter Maydell
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 06/13] target/arm: Implement PMOVSSET Aaron Lindsay
2018-06-28 16:23 ` Peter Maydell
2018-08-28 20:29 ` Aaron Lindsay
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 07/13] target/arm: Add array for supported PMU events, generate PMCEID[01] Aaron Lindsay
2018-07-17 16:06 ` Peter Maydell
2018-08-29 15:18 ` Aaron Lindsay
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 08/13] target/arm: Finish implementation of PM[X]EVCNTR and PM[X]EVTYPER Aaron Lindsay
2018-07-17 16:17 ` Peter Maydell
2018-08-29 15:31 ` Aaron Lindsay
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 09/13] target/arm: PMU: Add instruction and cycle events Aaron Lindsay
2018-07-17 16:11 ` Peter Maydell
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 10/13] target/arm: PMU: Set PMCR.N to 4 Aaron Lindsay
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 11/13] target/arm: Implement PMSWINC Aaron Lindsay
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 12/13] target/arm: Mark PMINTENSET accesses as possibly doing IO Aaron Lindsay
2018-06-28 16:25 ` Peter Maydell
2018-08-27 14:48 ` Aaron Lindsay [this message]
2018-06-22 20:32 ` [Qemu-devel] [PATCH v5 13/13] target/arm: Send interrupts on PMU counter overflow Aaron Lindsay
2018-07-17 16:28 ` Peter Maydell
2018-06-28 16:42 ` [Qemu-devel] [PATCH v5 00/13] More fully implement ARM PMUv3 Peter Maydell
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=20180827144809.GA3671@okra.localdomain \
--to=aclindsa@gmail.com \
--cc=aaron@amperecomputing.com \
--cc=alistair.francis@xilinx.com \
--cc=crosthwaite.peter@gmail.com \
--cc=michael.spradling@amperecomputing.com \
--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).