linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Youngmin Nam <youngmin.nam@samsung.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, junhosj.choi@samsung.com,
	hajun.sung@samsung.com, joonki.min@samsung.com,
	d7271.choe@samsung.com, jkkkkk.choi@samsung.com,
	jt1217.kim@samsung.com, qperret@google.com,
	willdeacon@google.com, dhyun.cha@samsung.com,
	kn_hong.choi@samsung.com, mankyum.kim@samsung.com
Subject: Re: [QUESTION] arch_counter_register() restricts CNTPT access when booted in EL1, even if EL2 is supported
Date: Fri, 16 May 2025 10:28:56 +0100	[thread overview]
Message-ID: <86frh4gazr.wl-maz@kernel.org> (raw)
In-Reply-To: <aCbhBttvi8mvsyGE@perf>

On Fri, 16 May 2025 07:53:58 +0100,
Youngmin Nam <youngmin.nam@samsung.com> wrote:
> 
> [1  <text/plain; utf-8 (8bit)>]
> Hi arm arch timer experts,
> 
> While reviewing the arm_arch_timer code in Linux 6.12,
> I noticed that the function arch_counter_register() restricts the
> use of the physical counter (cntpct_el0) on systems where the kernel
> is running in EL1, even if EL2 is supported and cntpct_el0 is
> accessible.
> 
> In our case:
> - We are not using pKVM.
> - The kernel is booted in EL1.
> - We disabled VIRT_PPI and explicitly selected PHYS_NONSECURE_PPI for the timer refering to below code.

That's not legal. The architecture guarantees that there is a virtual
timer and a physical timer. No ifs, no buts.

[...]

> As I understand it, `is_hyp_mode_available()` checks whether the
> kernel booted into EL2 — not whether EL2 is *supported* by the
> hardware.
> 
> Therefore, even on systems where EL2 exists and `cntpct_el0` is
> accessible from EL1, the kernel still forces the use of `cntvct_el0`
> if the boot EL is EL1.

Yes, because it isn't architecturally valid to not have a virtual
timer. This isn't about EL2 being present of not. The switch to the
physical timer is purely an optimisation for KVM so that it doesn't
have to switch the virtual timer back and forth when running a guest,
as the virtual timer is the most likely used timer.

> Is this restriction to `cntvct_el0` in EL1 an architectural
> requirement, or simply a conservative default to avoid possible
> traps on some systems?

Both. Crucially, it isn't possible to trap the virtual timer on some
older implementations.

> If the hardware clearly supports EL2 and allows CNTPT access from
> EL1, could this restriction be relaxed?

Absolutely not. Having the virtual timer is a hard requirement from
both the architecture *and* Linux. Feel free to emulate it from EL2 if
you want (and can trap it).

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.


       reply	other threads:[~2025-05-16  9:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250516064924epcas2p24c8f3dc1860768b2b7bed30a41528770@epcas2p2.samsung.com>
     [not found] ` <aCbhBttvi8mvsyGE@perf>
2025-05-16  9:28   ` Marc Zyngier [this message]
2025-05-19  1:43     ` [QUESTION] arch_counter_register() restricts CNTPT access when booted in EL1, even if EL2 is supported Youngmin Nam
2025-05-19  7:12       ` Marc Zyngier
2025-05-19  7:53         ` Youngmin Nam

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=86frh4gazr.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=d7271.choe@samsung.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=dhyun.cha@samsung.com \
    --cc=hajun.sung@samsung.com \
    --cc=jkkkkk.choi@samsung.com \
    --cc=joonki.min@samsung.com \
    --cc=jt1217.kim@samsung.com \
    --cc=junhosj.choi@samsung.com \
    --cc=kn_hong.choi@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mankyum.kim@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=qperret@google.com \
    --cc=tglx@linutronix.de \
    --cc=willdeacon@google.com \
    --cc=youngmin.nam@samsung.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).