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 v10 0/3] PMU-EBB support for PPC64 TCG
Date: Tue, 8 Feb 2022 16:48:35 -0300 [thread overview]
Message-ID: <20220208194838.169257-1-danielhb413@gmail.com> (raw)
Hi,
This small series finalizes the pending PMU-EBB support for PPC64 TCG.
In theory this would be a re-send of patches 09 and 10 of the v9, but
those patches were so off the mark with the recent exception changes
that I ended up discarding them and doing from the start.
Patch 1 is a trivial indent fix. I've read a lot of code in excp_helper.c
and this mis-indent was being annoying.
Patch 2 is the last bits of the PMU specific code before triggering
EBBs. I chose to do it separately to not mix PMU specific code and
EBB logic.
Patch 3 is the re-implementation of what patches 09+10 of the v9 were
doing back then. The most significant change is that we're now gating
the exception before reaching powerpc_excp_books().
v9 link: https://lists.gnu.org/archive/html/qemu-devel/2021-12/msg00073.html
Daniel Henrique Barboza (3):
target/ppc: fix indent of function parameters
target/ppc: finalize pre-EBB PMU logic
target/ppc: EBB exception implementation
target/ppc/excp_helper.c | 59 +++++++++++++++++++++++++++++++++++-----
target/ppc/helper.h | 1 +
target/ppc/power8-pmu.c | 48 +++++++++++++++++++++++++++++---
3 files changed, 97 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2022-02-08 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 19:48 Daniel Henrique Barboza [this message]
2022-02-08 19:48 ` [PATCH v10 1/3] target/ppc: fix indent of function parameters Daniel Henrique Barboza
2022-02-10 2:20 ` David Gibson
2022-02-08 19:48 ` [PATCH v10 2/3] target/ppc: finalize pre-EBB PMU logic Daniel Henrique Barboza
2022-02-08 19:48 ` [PATCH v10 3/3] target/ppc: EBB exception implementation Daniel Henrique Barboza
2022-02-08 23:20 ` Fabiano Rosas
2022-02-09 12:40 ` 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=20220208194838.169257-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).