From: "Alex Bennée" <alex.bennee@linaro.org>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [RFC PATCH] includes: move tb_flush into its own header
Date: Thu, 15 Dec 2022 16:46:56 +0000 [thread overview]
Message-ID: <87r0x0ipfm.fsf@linaro.org> (raw)
In-Reply-To: <f0ae5daf-ec43-aede-12d1-a6dd4406c28b@linaro.org>
Richard Henderson <richard.henderson@linaro.org> writes:
> On 12/15/22 06:09, Alex Bennée wrote:
>> This aids subsystems (like gdbstub) that want to trigger a flush
>> without pulling target specific headers.
>> [AJB: RFC because this is part of a larger gdbstub series but I
>> wanted
>> to post for feedback in case anyone wants to suggest better naming].
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>> include/exec/exec-all.h | 1 -
>> linux-user/user-internals.h | 1 +
>> accel/tcg/tb-maint.c | 1 +
>> accel/tcg/translate-all.c | 1 +
>> cpu.c | 1 +
>> gdbstub/gdbstub.c | 1 +
>> hw/ppc/spapr_hcall.c | 1 +
>> plugins/core.c | 1 +
>> plugins/loader.c | 2 +-
>> target/alpha/sys_helper.c | 1 +
>> target/riscv/csr.c | 1 +
>> 11 files changed, 10 insertions(+), 2 deletions(-)
>
> It appears as if you forgot to add tb-common.h.
> That said, if this is intended to have exactly one thing, tb-flush.h
> might be better.
I'll rename and include when I send the gdbstub stuff. I don't know how
far you want to go to eliminate target specific handling from the rest
of TB maintenance - indeed I'm not sure anything else is possible?
>
>
> r~
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2022-12-15 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 14:09 [RFC PATCH] includes: move tb_flush into its own header Alex Bennée
2022-12-15 16:15 ` Richard Henderson
2022-12-15 16:46 ` Alex Bennée [this message]
2022-12-15 16:51 ` Richard Henderson
2022-12-15 17:39 ` Philippe Mathieu-Daudé
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=87r0x0ipfm.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.