All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Ott <sebott@redhat.com>
To: Eric Auger <eauger@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	 Jonathan Cameron <jonathan.cameron@huawei.com>,
	 Alireza Sanaee <alireza.sanaee@huawei.com>,
	 Richard Henderson <richard.henderson@linaro.org>,
	 Cornelia Huck <cohuck@redhat.com>,
	qemu-arm@nongnu.org,  qemu-devel@nongnu.org
Subject: Re: [PATCH v4 3/3] arm/kvm: get demuxed ID registers from kvm
Date: Fri, 10 Jul 2026 15:01:20 +0200 (CEST)	[thread overview]
Message-ID: <0a463fde-b206-cafb-8625-e03bb5d1ce58@redhat.com> (raw)
In-Reply-To: <7ab742c2-2354-4316-a727-a56175a321b9@redhat.com>

Hej Eric,

On Tue, 7 Jul 2026, Eric Auger wrote:
> On 7/2/26 3:36 PM, Sebastian Ott wrote:
>> From: Cornelia Huck <cohuck@redhat.com>
>>
>> We now have the infrastructure in place to handle demuxed ID registers
>> from kvm. Use it to get the values that kvm emulates for CCSIDR_EL1.
>
> I wonder whether that patch is needed at this point. Were previous
> ccsidr[i] initialized from KVM before? What is the actual motivation to
> read them in this series. Doesn't it bring the risk to expose new values
> to the guest?
>
> For instance, in [RFC PATCH v6 11/17] arm/kvm: Initialize all writable
> ID registers from host, I generalized the initialization of all writable
> id regs and I noticed that the new initialization of CLIDR from KVM
> broke the execution (which is not the case for the CCSIDR because I did
> it a try) because CLIDR was previously uninitialized and null.

The issue is holes in arm64_id_regs[] and we stumble over that in
get_host_cpu_idregs(). Maybe we could skip the demuxed regs when we
iterate over that array.

Sebastian



  parent reply	other threads:[~2026-07-10 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 13:36 [PATCH v4 0/3] arm: demuxed ID registers (CCSIDR_EL1) Sebastian Ott
2026-07-02 13:36 ` [PATCH v4 1/3] arm: handle demuxed ID registers Sebastian Ott
2026-07-02 13:36 ` [PATCH v4 2/3] arm: handle CCSIDR_EL1 as a demuxed register Sebastian Ott
2026-07-07  9:55   ` Eric Auger
2026-07-02 13:36 ` [PATCH v4 3/3] arm/kvm: get demuxed ID registers from kvm Sebastian Ott
2026-07-07 10:24   ` Eric Auger
2026-07-08 14:17     ` Sebastian Ott
2026-07-10 13:01     ` Sebastian Ott [this message]
2026-07-03 13:00 ` [PATCH v4 0/3] arm: demuxed ID registers (CCSIDR_EL1) Peter Maydell
2026-07-06 11:55   ` Sebastian Ott

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=0a463fde-b206-cafb-8625-e03bb5d1ce58@redhat.com \
    --to=sebott@redhat.com \
    --cc=alireza.sanaee@huawei.com \
    --cc=cohuck@redhat.com \
    --cc=eauger@redhat.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.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.