From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-ppc@nongnu.org, clg@kaod.org, david@gibson.dropbear.id.au
Subject: [PATCH v13 0/4] PMU-EBB support for PPC64 TCG
Date: Thu, 24 Feb 2022 17:18:56 -0300 [thread overview]
Message-ID: <20220224201900.1037465-1-danielhb413@gmail.com> (raw)
Hi,
This new version contains a change in patch 1 (former 2) that was
proposed by Richard in the v12 review.
Changes from v12:
- former patch 1: dropped, no longer applicable
- patch 1 (former 2):
* use tcg_enabled() instead of !kvm_enabled() to avoid defined(CONFIG_TCG)
ifdefs
- v12 link: https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg03622.html
Daniel Henrique Barboza (4):
target/ppc: make power8-pmu.c CONFIG_TCG only
target/ppc: finalize pre-EBB PMU logic
target/ppc: add PPC_INTERRUPT_EBB and EBB exceptions
target/ppc: trigger PERFM EBBs from power8-pmu.c
target/ppc/cpu.h | 5 ++-
target/ppc/cpu_init.c | 20 +++++-----
target/ppc/excp_helper.c | 81 ++++++++++++++++++++++++++++++++++++++++
target/ppc/helper.h | 1 +
target/ppc/machine.c | 6 ++-
target/ppc/meson.build | 2 +-
target/ppc/power8-pmu.c | 39 +++++++++++++++++--
target/ppc/power8-pmu.h | 4 +-
8 files changed, 140 insertions(+), 18 deletions(-)
--
2.35.1
next reply other threads:[~2022-02-24 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 20:18 Daniel Henrique Barboza [this message]
2022-02-24 20:18 ` [PATCH v13 1/4] target/ppc: make power8-pmu.c CONFIG_TCG only Daniel Henrique Barboza
2022-02-24 21:32 ` Richard Henderson
2022-02-24 20:18 ` [PATCH v13 2/4] target/ppc: finalize pre-EBB PMU logic Daniel Henrique Barboza
2022-02-24 20:18 ` [PATCH v13 3/4] target/ppc: add PPC_INTERRUPT_EBB and EBB exceptions Daniel Henrique Barboza
2022-02-24 20:19 ` [PATCH v13 4/4] target/ppc: trigger PERFM EBBs from power8-pmu.c Daniel Henrique Barboza
2022-02-24 21:45 ` Richard Henderson
2022-02-25 10:10 ` Daniel Henrique Barboza
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=20220224201900.1037465-1-danielhb413@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).