From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, francesco.cagnin@gmail.com
Cc: qemu-devel@nongnu.org, dirty@apple.com, r.bolshakov@yadro.com,
peter.maydell@linaro.org, agraf@csgraf.de, pbonzini@redhat.com,
Francesco Cagnin <fcagnin@quarkslab.com>,
qemu-arm@nongnu.org
Subject: Re: [PATCH 1/3] arm: move KVM breakpoints helpers
Date: Mon, 7 Nov 2022 15:39:13 +0100 [thread overview]
Message-ID: <0a146956-a397-54c1-71dd-cd90a68218f7@linaro.org> (raw)
In-Reply-To: <87a652hmoe.fsf@linaro.org>
On 7/11/22 15:15, Alex Bennée wrote:
>
> francesco.cagnin@gmail.com writes:
>
>> From: Francesco Cagnin <fcagnin@quarkslab.com>
>>
>> These helpers will be also used for HVF. Aside from reformatting a
>> couple of comments for 'checkpatch.pl', this is just code motion.
>>
>> Signed-off-by: Francesco Cagnin <fcagnin@quarkslab.com>
>> ---
>> target/arm/debug_helper.c | 241 +++++++++++++++++++++++++++++++++
>> target/arm/internals.h | 50 +++++++
>
> Moving out of kvm64.c seems fine to me but I wonder if debug_helper.c is
> the best location. debug_helpers is currently very focused on just
> handling the TCG emulation case where as we are doing this tracking just
> for the VMM cases or KVM and now HVF.
>
> We are (slowly) trying to clean up the code in target/arm so we can
> support builds like --disable-tcg and to do that we want to avoid too
> much ifdef hackery in the individual compilation units.
I was planning to move hypervisor-specific code to
target/arm/$hypervisor/, but here Francesco wants to re-use the same code
between 2 hypervisors... Maybe move it to target/arm/hyp_gdbstub.c
and let meson add it conditionally?
>> target/arm/kvm64.c | 276 --------------------------------------
>> 3 files changed, 291 insertions(+), 276 deletions(-)
> <snip>
>
next prev parent reply other threads:[~2022-11-07 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 18:40 [PATCH 0/3] Add gdbstub support to HVF francesco.cagnin
2022-11-04 18:40 ` [PATCH 1/3] arm: move KVM breakpoints helpers francesco.cagnin
2022-11-07 13:00 ` Mads Ynddal
2022-11-07 14:15 ` Alex Bennée
2022-11-07 14:39 ` Philippe Mathieu-Daudé [this message]
2022-11-09 12:55 ` Francesco Cagnin
2022-11-04 18:41 ` [PATCH 2/3] hvf: implement guest debugging on Apple Silicon hosts francesco.cagnin
2022-11-07 12:38 ` Mads Ynddal
2022-11-07 13:28 ` Mads Ynddal
2022-11-08 10:09 ` Francesco Cagnin
2022-11-08 11:51 ` Mads Ynddal
2022-11-09 10:12 ` Mads Ynddal
2022-11-09 10:58 ` Peter Maydell
2022-11-09 11:34 ` Francesco Cagnin
2022-11-04 18:41 ` [PATCH 3/3] hvf: handle writes of MDSCR_EL1 and DBG*_EL1 francesco.cagnin
2022-11-07 13:00 ` Mads Ynddal
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=0a146956-a397-54c1-71dd-cd90a68218f7@linaro.org \
--to=philmd@linaro.org \
--cc=agraf@csgraf.de \
--cc=alex.bennee@linaro.org \
--cc=dirty@apple.com \
--cc=fcagnin@quarkslab.com \
--cc=francesco.cagnin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.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).