All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
	"Marcin Juszkiewicz" <marcin.juszkiewicz@linaro.org>,
	"Leif Lindholm" <quic_llindhol@quicinc.com>,
	"Radoslaw Biernacki" <rad@semihalf.com>,
	qemu-stable@nongnu.org, "Andrei Homescu" <ahomescu@google.com>,
	"Arve Hjønnevåg" <arve@google.com>,
	"Rémi Denis-Courmont" <remi.denis.courmont@huawei.com>
Subject: Re: [PATCH 3/3] target/arm: implement SEL2 physical and virtual timers
Date: Mon, 16 Dec 2024 19:32:46 +0000	[thread overview]
Message-ID: <877c7z1l0h.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAFEAcA8mi=gTBvh9FqyMFeyqAHqirkah84sW4m8axKPqwMZDkQ@mail.gmail.com> (Peter Maydell's message of "Mon, 16 Dec 2024 18:14:55 +0000")

Peter Maydell <peter.maydell@linaro.org> writes:

> On Fri, 6 Dec 2024 at 16:02, Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> When FEAT_SEL2 was implemented the SEL2 timers where missed. This
>> shows up when building the latest Hafnium with SPMC_AT_EL=2. The
>> actual implementation utilises the same logic as the rest of the
>> timers so all we need to do is:
>>
>>   - define the timers and their access functions
>>   - conditionally add the correct system registers
>>   - create a new accessfn as the rules are subtly different to the
>>     existing secure timer
>>
>> Fixes: e9152ee91c (target/arm: add ARMv8.4-SEL2 system registers)
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> Cc: qemu-stable@nongnu.org
>> Cc: Andrei Homescu <ahomescu@google.com>
>> Cc: Arve Hjønnevåg <arve@google.com>
>> Cc: Rémi Denis-Courmont <remi.denis.courmont@huawei.com>
>>
>> ---
>> v1
>>   - add better comments to GTIMER descriptions
>>   - also define new timers for sbsa-ref
>>   - don't conditionally gate qemu_timer creation on the feature
>>   - take cntvoff_el2 int account for SEC_VEL2 in gt_recalc/g_tval_[read|write]
>> ---
>>  include/hw/arm/bsa.h |   2 +
>>  target/arm/cpu.h     |   2 +
>>  target/arm/gtimer.h  |   4 +-
>>  hw/arm/sbsa-ref.c    |   2 +
>>  hw/arm/virt.c        |   2 +
>
> I would put the board changes in their own patch(es).

Won't that break bisection?

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro

  reply	other threads:[~2024-12-16 19:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 16:02 [PATCH 0/3] target/arm: implement SEL2 physical and virtual timers Alex Bennée
2024-12-06 16:02 ` [PATCH 1/3] target/arm: document the architectural names of our GTIMERs Alex Bennée
2024-12-16 14:08   ` Peter Maydell
2024-12-06 16:02 ` [PATCH 2/3] target/arm: ensure cntvoff_el2 also used for EL2 virt timer Alex Bennée
2024-12-06 16:02 ` [PATCH 3/3] target/arm: implement SEL2 physical and virtual timers Alex Bennée
2024-12-16 18:14   ` Peter Maydell
2024-12-16 19:32     ` Alex Bennée [this message]
2024-12-17 10:26       ` Peter Maydell
2024-12-17 13:34   ` Peter Maydell
2024-12-18 17:07     ` Alex Bennée

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=877c7z1l0h.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=ahomescu@google.com \
    --cc=arve@google.com \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=quic_llindhol@quicinc.com \
    --cc=rad@semihalf.com \
    --cc=remi.denis.courmont@huawei.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 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.