qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vacha Bhavsar <vacha.bhavsar@oss.qualcomm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v5 3/4] target/arm: Added support for SME register exposure to
Date: Tue, 26 Aug 2025 14:52:06 -0400	[thread overview]
Message-ID: <CAEWVDms-Ttx_P6WePjsxRt-=rAmr2aLVFOZEhC4mitdypWMcxg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA_BV1ThJ_2L5pDd8WQhSPKd2WKbW1eb1Owrr4YswOg9Bg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1950 bytes --]

Hi,

I have sent a new version of this patch series addressing
these comments.

Looking forward to your feedback.

Thanks,
Vacha

On Fri, Aug 22, 2025 at 8:27 AM Peter Maydell <peter.maydell@linaro.org>
wrote:

> On Thu, 21 Aug 2025 at 22:37, Vacha Bhavsar
> <vacha.bhavsar@oss.qualcomm.com> wrote:
> >
> > Hi,
> >
> > Regarding having the SME check inside the "if we have SVE" check, we
> were looking the the
> > Arm ARM, specifically the following excerpt from section A1.4:
> >
> > The architecture provides the following:
> >
> > - A general-purpose register file.
> > - A SIMD&FP register file.
> > - If FEAT_SVE or FEAT_SME is implemented, an SVE scalable vector
> register file and an
> > SVE scalable predicate register file.
> > - if FEAT_SME is implemented, the scalable ZA storage.
> >
> > Based on this, we were considering the following update to the change in
> gdbstub64.c and
> > we wanted to get your input.
> >
> > if (isar_feature_aa64_sve(&cpu->isar) ||
> isar_feature_aa64_sme(&cpu->isar)) {
> >             GDBFeature *feature = arm_gen_dynamic_svereg_feature(cs,
> cs->gdb_num_regs);
> >             gdb_register_coprocessor(cs, aarch64_gdb_get_sve_reg,
> >                                      aarch64_gdb_set_sve_reg, feature,
> 0);
> > } else {
> >             gdb_register_coprocessor(cs, aarch64_gdb_get_fpu_reg,
> >                                      aarch64_gdb_set_fpu_reg,
> >
> gdb_find_static_feature("aarch64-fpu.xml"),
> >                                      0);
> > }
> >
> > if (isar_feature_aa64_sme(&cpu->isar)) {
> >               GDBFeature *sme_feature =
> arm_gen_dynamic_smereg_feature(cs,
> >                     cs->gdb_num_regs);
> >               gdb_register_coprocessor(cs, aarch64_gdb_get_sme_reg,
> >                     aarch64_gdb_set_sme_reg, sme_feature, 0);
> > }
>
> Yes, I think that will be right.
>
> thanks
> -- PMM
>

[-- Attachment #2: Type: text/html, Size: 2724 bytes --]

  reply	other threads:[~2025-08-26 18:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 19:36 [PATCH v5 0/4] target/arm: Added support for SME register exposure to GDB Vacha Bhavsar
2025-08-11 19:36 ` [PATCH v5 1/4] target/arm: Increase MAX_PACKET_LENGTH for SME ZA Vacha Bhavsar
2025-08-19  9:14   ` Peter Maydell
2025-08-11 19:36 ` [PATCH v5 2/4] target/arm: Change GDBState's line_buf to a GString Vacha Bhavsar
2025-08-12 11:32   ` Peter Maydell
2025-08-12 19:31     ` Vacha Bhavsar
2025-08-11 19:36 ` [PATCH v5 3/4] target/arm: Added support for SME register exposure to Vacha Bhavsar
2025-08-19  9:04   ` Peter Maydell
2025-08-21 21:37     ` Vacha Bhavsar
2025-08-22 12:27       ` Peter Maydell
2025-08-26 18:52         ` Vacha Bhavsar [this message]
2025-08-11 19:36 ` [PATCH v5 4/4] target/arm: Added test case for SME register exposure Vacha Bhavsar
2025-08-19  9:13   ` Peter Maydell
2025-08-22 17:32     ` Vacha Bhavsar
2025-08-23 18:13       ` Peter Maydell
2025-08-26 18:51         ` Vacha Bhavsar

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='CAEWVDms-Ttx_P6WePjsxRt-=rAmr2aLVFOZEhC4mitdypWMcxg@mail.gmail.com' \
    --to=vacha.bhavsar@oss.qualcomm.com \
    --cc=alex.bennee@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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).