From: Cornelia Huck <cohuck@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
Eric Auger <eric.auger@redhat.com>
Subject: Re: [PATCH for-11.0] arm: add DCZID_EL0 to idregs array
Date: Tue, 25 Nov 2025 17:09:41 +0100 [thread overview]
Message-ID: <87see2ozzu.fsf@redhat.com> (raw)
In-Reply-To: <CAFEAcA8r7_6fbEFtkEL4vi-wqABewcPU3P73RWh08RRQnQ5Baw@mail.gmail.com>
On Mon, Nov 24 2025, Peter Maydell <peter.maydell@linaro.org> wrote:
> On Wed, 19 Nov 2025 at 13:44, Cornelia Huck <cohuck@redhat.com> wrote:
>>
>> This requires a bit of care, since we still have to handle the EL
>> specific part (DCZID_EL0.DZP). Callers can set/access dcz_blocksize
>> via a wrapper working on DCZID_EL.BS.
>>
>> KVM currently does not support DCZID_EL0 via ONE_REG, and actually
>> does not need to work with it, so provide a dummy value for now.
>
> That seems like an odd (unintended?) omission -- is it worth
> adding? (We would need to handle older kernels that don't
> expose it anyway, of course.)
I'm not sure whether there's actually a usecase for KVM exposing this to
the VMM - AFAICS, KVM doesn't do anything special for DC ZVA and
friends, and doesn't tweak HCR_EL2.TDZ which would change behaviour.
next prev parent reply other threads:[~2025-11-25 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 13:44 [PATCH for-11.0] arm: add DCZID_EL0 to idregs array Cornelia Huck
2025-11-20 18:04 ` Eric Auger
2025-11-21 14:47 ` Cornelia Huck
2025-11-24 17:00 ` Peter Maydell
2025-11-25 16:09 ` Cornelia Huck [this message]
2025-11-25 16:49 ` Peter Maydell
2025-11-26 12:59 ` Cornelia Huck
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=87see2ozzu.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@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 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.