From: Richard Henderson <richard.henderson@linaro.org>
To: Daniel Henrique Barboza <danielhb413@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, clg@kaod.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH v13 1/4] target/ppc: make power8-pmu.c CONFIG_TCG only
Date: Thu, 24 Feb 2022 11:32:18 -1000 [thread overview]
Message-ID: <b485cf47-32c5-fead-6aef-7e8c9ffbe558@linaro.org> (raw)
In-Reply-To: <20220224201900.1037465-2-danielhb413@gmail.com>
On 2/24/22 10:18, Daniel Henrique Barboza wrote:
> This is an exclusive TCG helper. Gating it with CONFIG_TCG and changing
> meson.build accordingly will prevent problems --disable-tcg and
> --disable-linux-user later on.
>
> We're also changing the uses of !kvm_enabled() to tcg_enabled() to avoid
> adding "defined(CONFIG_TCG)" ifdefs, since tcg_enabled() will be
> defaulted to false with --disable-tcg and the block will always be
> skipped.
>
> Signed-off-by: Daniel Henrique Barboza<danielhb413@gmail.com>
> ---
> target/ppc/cpu_init.c | 16 +++++++---------
> target/ppc/machine.c | 6 +++++-
> target/ppc/meson.build | 2 +-
> target/ppc/power8-pmu.h | 4 ++--
> 4 files changed, 15 insertions(+), 13 deletions(-)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2022-02-24 21:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 20:18 [PATCH v13 0/4] PMU-EBB support for PPC64 TCG Daniel Henrique Barboza
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 [this message]
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=b485cf47-32c5-fead-6aef-7e8c9ffbe558@linaro.org \
--to=richard.henderson@linaro.org \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--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).