linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Steven Price <steven.price@arm.com>
To: Joey Gouly <joey.gouly@arm.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev,
	Catalin Marinas <catalin.marinas@arm.com>,
	Marc Zyngier <maz@kernel.org>, Will Deacon <will@kernel.org>,
	James Morse <james.morse@arm.com>,
	Oliver Upton <oliver.upton@linux.dev>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	Christoffer Dall <christoffer.dall@arm.com>,
	Fuad Tabba <tabba@google.com>,
	linux-coco@lists.linux.dev,
	Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>,
	Gavin Shan <gshan@redhat.com>,
	Shanker Donthineni <sdonthineni@nvidia.com>,
	Alper Gun <alpergun@google.com>,
	"Aneesh Kumar K . V" <aneesh.kumar@kernel.org>,
	Emi Kisanuki <fj0570is@fujitsu.com>
Subject: Re: [PATCH v9 14/43] KVM: arm64: Support timers in realm RECs
Date: Wed, 9 Jul 2025 16:29:39 +0100	[thread overview]
Message-ID: <8757342e-26e6-467c-a469-0ac1120bcdd9@arm.com> (raw)
In-Reply-To: <20250709144939.GA2753450@e124191.cambridge.arm.com>

Hi Joey,

On 09/07/2025 15:49, Joey Gouly wrote:
> Hi Steven,
> 
> On Wed, Jun 11, 2025 at 11:48:11AM +0100, Steven Price wrote:
>> The RMM keeps track of the timer while the realm REC is running, but on
>> exit to the normal world KVM is responsible for handling the timers.
>>
>> The RMM doesn't provide a mechanism to set the counter offset, so don't
>> expose KVM_CAP_COUNTER_OFFSET for a realm VM.
>>
>> A later patch adds the support for propagating the timer values from the
>> exit data structure and calling kvm_realm_timers_update().
>>
>> Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>> Signed-off-by: Steven Price <steven.price@arm.com>
>> ---
>> Changes since v7:
>>  * Hide KVM_CAP_COUNTER_OFFSET for realm guests.
>> ---
>>  arch/arm64/kvm/arch_timer.c  | 48 +++++++++++++++++++++++++++++++++---
>>  arch/arm64/kvm/arm.c         |  2 +-
>>  include/kvm/arm_arch_timer.h |  2 ++
>>  3 files changed, 47 insertions(+), 5 deletions(-)
>>
>> diff --git a/arch/arm64/kvm/arch_timer.c b/arch/arm64/kvm/arch_timer.c
>> index fdbc8beec930..7f8705d6fdf5 100644
>> --- a/arch/arm64/kvm/arch_timer.c
>> +++ b/arch/arm64/kvm/arch_timer.c
>> @@ -148,6 +148,13 @@ static void timer_set_cval(struct arch_timer_context *ctxt, u64 cval)
>>  
>>  static void timer_set_offset(struct arch_timer_context *ctxt, u64 offset)
>>  {
>> +	struct kvm_vcpu *vcpu = ctxt->vcpu;
>> +
>> +	if (kvm_is_realm(vcpu->kvm)) {
>> +		WARN_ON(offset);
>> +		return;
>> +	}
>> +
>>  	if (!ctxt->offset.vm_offset) {
>>  		WARN(offset, "timer %ld\n", arch_timer_ctx_index(ctxt));
>>  		return;
>> @@ -462,6 +469,21 @@ static void kvm_timer_update_irq(struct kvm_vcpu *vcpu, bool new_level,
>>  			    timer_ctx);
>>  }
>>  
>> +void kvm_realm_timers_update(struct kvm_vcpu *vcpu)
>> +{
>> +	struct arch_timer_cpu *arch_timer = &vcpu->arch.timer_cpu;
>> +	int i;
>> +
>> +	for (i = 0; i < NR_KVM_EL0_TIMERS; i++) {
>> +		struct arch_timer_context *timer = &arch_timer->timers[i];
>> +		bool status = timer_get_ctl(timer) & ARCH_TIMER_CTRL_IT_STAT;
>> +		bool level = kvm_timer_irq_can_fire(timer) && status;
>> +
>> +		if (level != timer->irq.level)
>> +			kvm_timer_update_irq(vcpu, level, timer);
>> +	}
>> +}
>> +
>>  /* Only called for a fully emulated timer */
>>  static void timer_emulate(struct arch_timer_context *ctx)
>>  {
>> @@ -870,6 +892,8 @@ void kvm_timer_vcpu_load(struct kvm_vcpu *vcpu)
>>  	if (unlikely(!timer->enabled))
>>  		return;
>>  
>> +	kvm_timer_unblocking(vcpu);
>> +
>>  	get_timer_map(vcpu, &map);
>>  
>>  	if (static_branch_likely(&has_gic_active_state)) {
>> @@ -883,8 +907,6 @@ void kvm_timer_vcpu_load(struct kvm_vcpu *vcpu)
>>  		kvm_timer_vcpu_load_nogic(vcpu);
>>  	}
>>  
>> -	kvm_timer_unblocking(vcpu);
>> -
> 
> The change here to move kvm_timer_unblocking() looks unnecessary, as the change
> to add an early return in kvm_timer_enable() causes timer->enable to never be
> set to 1.  Since it is never set, kvm_timer_vcpu_load() will return early
> before this call to kvm_timer_unblocking().

Good spot.

Looking through the code it makes sense keeping the timer disabled
because that also disables all the code for loading/unloading the timer
state which we don't want for realms (because the RMM deals with that).
So I think just reverting the above change to move
kvm_timer_unblocking() is the correct approach.

Thanks,
Steve

> Thanks,
> Joey
> 
>>  	timer_restore_state(map.direct_vtimer);
>>  	if (map.direct_ptimer)
>>  		timer_restore_state(map.direct_ptimer);
>> @@ -1065,7 +1087,9 @@ static void timer_context_init(struct kvm_vcpu *vcpu, int timerid)
>>  
>>  	ctxt->vcpu = vcpu;
>>  
>> -	if (timerid == TIMER_VTIMER)
>> +	if (kvm_is_realm(vcpu->kvm))
>> +		ctxt->offset.vm_offset = NULL;
>> +	else if (timerid == TIMER_VTIMER)
>>  		ctxt->offset.vm_offset = &kvm->arch.timer_data.voffset;
>>  	else
>>  		ctxt->offset.vm_offset = &kvm->arch.timer_data.poffset;
>> @@ -1087,13 +1111,19 @@ static void timer_context_init(struct kvm_vcpu *vcpu, int timerid)
>>  void kvm_timer_vcpu_init(struct kvm_vcpu *vcpu)
>>  {
>>  	struct arch_timer_cpu *timer = vcpu_timer(vcpu);
>> +	u64 cntvoff;
>>  
>>  	for (int i = 0; i < NR_KVM_TIMERS; i++)
>>  		timer_context_init(vcpu, i);
>>  
>> +	if (kvm_is_realm(vcpu->kvm))
>> +		cntvoff = 0;
>> +	else
>> +		cntvoff = kvm_phys_timer_read();
>> +
>>  	/* Synchronize offsets across timers of a VM if not already provided */
>>  	if (!test_bit(KVM_ARCH_FLAG_VM_COUNTER_OFFSET, &vcpu->kvm->arch.flags)) {
>> -		timer_set_offset(vcpu_vtimer(vcpu), kvm_phys_timer_read());
>> +		timer_set_offset(vcpu_vtimer(vcpu), cntvoff);
>>  		timer_set_offset(vcpu_ptimer(vcpu), 0);
>>  	}
>>  
>> @@ -1633,6 +1663,13 @@ int kvm_timer_enable(struct kvm_vcpu *vcpu)
>>  		return -EINVAL;
>>  	}
>>  
>> +	/*
>> +	 * We don't use mapped IRQs for Realms because the RMI doesn't allow
>> +	 * us setting the LR.HW bit in the VGIC.
>> +	 */
>> +	if (vcpu_is_rec(vcpu))
>> +		return 0;
>> +
>>  	get_timer_map(vcpu, &map);
>>  
>>  	ret = kvm_vgic_map_phys_irq(vcpu,
>> @@ -1764,6 +1801,9 @@ int kvm_vm_ioctl_set_counter_offset(struct kvm *kvm,
>>  	if (offset->reserved)
>>  		return -EINVAL;
>>  
>> +	if (kvm_is_realm(kvm))
>> +		return -EINVAL;
>> +
>>  	mutex_lock(&kvm->lock);
>>  
>>  	if (!kvm_trylock_all_vcpus(kvm)) {
>> diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
>> index 0cdcc2ca4a88..6a5c9be4af2d 100644
>> --- a/arch/arm64/kvm/arm.c
>> +++ b/arch/arm64/kvm/arm.c
>> @@ -350,10 +350,10 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
>>  	case KVM_CAP_PTP_KVM:
>>  	case KVM_CAP_ARM_SYSTEM_SUSPEND:
>>  	case KVM_CAP_IRQFD_RESAMPLE:
>> -	case KVM_CAP_COUNTER_OFFSET:
>>  	case KVM_CAP_ARM_WRITABLE_IMP_ID_REGS:
>>  		r = 1;
>>  		break;
>> +	case KVM_CAP_COUNTER_OFFSET:
>>  	case KVM_CAP_SET_GUEST_DEBUG:
>>  		r = !kvm_is_realm(kvm);
>>  		break;
>> diff --git a/include/kvm/arm_arch_timer.h b/include/kvm/arm_arch_timer.h
>> index 681cf0c8b9df..f64e317c091b 100644
>> --- a/include/kvm/arm_arch_timer.h
>> +++ b/include/kvm/arm_arch_timer.h
>> @@ -113,6 +113,8 @@ int kvm_arm_timer_set_attr(struct kvm_vcpu *vcpu, struct kvm_device_attr *attr);
>>  int kvm_arm_timer_get_attr(struct kvm_vcpu *vcpu, struct kvm_device_attr *attr);
>>  int kvm_arm_timer_has_attr(struct kvm_vcpu *vcpu, struct kvm_device_attr *attr);
>>  
>> +void kvm_realm_timers_update(struct kvm_vcpu *vcpu);
>> +
>>  u64 kvm_phys_timer_read(void);
>>  
>>  void kvm_timer_vcpu_load(struct kvm_vcpu *vcpu);
>> -- 
>> 2.43.0
>>



  reply	other threads:[~2025-07-09 19:14 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 10:47 [PATCH v9 00/43] arm64: Support for Arm CCA in KVM Steven Price
2025-06-11 10:47 ` [PATCH v9 01/43] kvm: arm64: Include kvm_emulate.h in kvm/arm_psci.h Steven Price
2025-06-11 10:47 ` [PATCH v9 02/43] arm64: RME: Handle Granule Protection Faults (GPFs) Steven Price
2025-06-11 10:48 ` [PATCH v9 03/43] arm64: RME: Add SMC definitions for calling the RMM Steven Price
2025-06-11 10:48 ` [PATCH v9 04/43] arm64: RME: Add wrappers for RMI calls Steven Price
2025-06-11 10:48 ` [PATCH v9 05/43] arm64: RME: Check for RME support at KVM init Steven Price
2025-06-11 10:48 ` [PATCH v9 06/43] arm64: RME: Define the user ABI Steven Price
2025-07-01  6:29   ` Gavin Shan
2025-06-11 10:48 ` [PATCH v9 07/43] arm64: RME: ioctls to create and configure realms Steven Price
2025-06-16 10:47   ` Suzuki K Poulose
2025-06-23 13:17   ` zhuangyiwei
2025-06-23 14:45     ` Steven Price
2025-06-11 10:48 ` [PATCH v9 08/43] kvm: arm64: Don't expose debug capabilities for realm guests Steven Price
2025-06-11 10:48 ` [PATCH v9 09/43] KVM: arm64: Allow passing machine type in KVM creation Steven Price
2025-07-01  6:38   ` Gavin Shan
2025-06-11 10:48 ` [PATCH v9 10/43] arm64: RME: RTT tear down Steven Price
2025-06-16 10:41   ` Suzuki K Poulose
2025-06-23 14:45     ` Steven Price
2025-06-11 10:48 ` [PATCH v9 11/43] arm64: RME: Allocate/free RECs to match vCPUs Steven Price
2025-06-25  9:00   ` Joey Gouly
2025-06-27 10:37     ` Steven Price
2025-06-11 10:48 ` [PATCH v9 12/43] KVM: arm64: vgic: Provide helper for number of list registers Steven Price
2025-07-01 10:16   ` Suzuki K Poulose
2025-06-11 10:48 ` [PATCH v9 13/43] arm64: RME: Support for the VGIC in realms Steven Price
2025-07-01  6:41   ` Gavin Shan
2025-07-01 10:20   ` Suzuki K Poulose
2025-07-03 13:22   ` Suzuki K Poulose
2025-07-09 14:42     ` Steven Price
2025-06-11 10:48 ` [PATCH v9 14/43] KVM: arm64: Support timers in realm RECs Steven Price
2025-07-01  6:42   ` Gavin Shan
2025-07-09 14:49   ` Joey Gouly
2025-07-09 15:29     ` Steven Price [this message]
2025-06-11 10:48 ` [PATCH v9 15/43] arm64: RME: Allow VMM to set RIPAS Steven Price
2025-06-17 12:16   ` zhuangyiwei
2025-06-17 12:56   ` zhuangyiwei
2025-06-23 14:45     ` Steven Price
2025-06-18 12:33   ` Andre Przywara
2025-06-23 14:45     ` Steven Price
2025-07-02  0:37   ` Gavin Shan
2025-07-09 14:42     ` Steven Price
2025-07-10  5:24       ` Gavin Shan
2025-06-11 10:48 ` [PATCH v9 16/43] arm64: RME: Handle realm enter/exit Steven Price
2025-06-25  1:45   ` Emi Kisanuki (Fujitsu)
2025-07-02  0:41   ` Gavin Shan
2025-06-11 10:48 ` [PATCH v9 17/43] arm64: RME: Handle RMI_EXIT_RIPAS_CHANGE Steven Price
2025-07-02  0:44   ` Gavin Shan
2025-06-11 10:48 ` [PATCH v9 18/43] KVM: arm64: Handle realm MMIO emulation Steven Price
2025-06-11 10:48 ` [PATCH v9 19/43] arm64: RME: Allow populating initial contents Steven Price
2025-08-01  1:56   ` Vishal Annapurve
2025-08-13  9:30     ` Steven Price
2025-08-14 16:26       ` Vishal Annapurve
2025-08-15 15:48         ` Steven Price
2025-08-15 18:18           ` Vishal Annapurve
2025-08-16  1:56           ` Vishal Annapurve
2025-06-11 10:48 ` [PATCH v9 20/43] arm64: RME: Runtime faulting of memory Steven Price
2025-06-16 11:55   ` Gavin Shan
2025-06-23 16:04     ` Steven Price
2025-07-02  1:04   ` Gavin Shan
2025-06-11 10:48 ` [PATCH v9 21/43] KVM: arm64: Handle realm VCPU load Steven Price
2025-06-11 10:48 ` [PATCH v9 22/43] KVM: arm64: Validate register access for a Realm VM Steven Price
2025-06-24 15:10   ` Joey Gouly
2025-06-11 10:48 ` [PATCH v9 23/43] KVM: arm64: Handle Realm PSCI requests Steven Price
2025-06-11 10:48 ` [PATCH v9 24/43] KVM: arm64: WARN on injected undef exceptions Steven Price
2025-06-11 10:48 ` [PATCH v9 25/43] arm64: Don't expose stolen time for realm guests Steven Price
2025-06-11 10:48 ` [PATCH v9 26/43] arm64: RME: allow userspace to inject aborts Steven Price
2025-06-11 10:48 ` [PATCH v9 27/43] arm64: RME: support RSI_HOST_CALL Steven Price
2025-06-11 10:48 ` [PATCH v9 28/43] arm64: RME: Allow checking SVE on VM instance Steven Price
2025-06-24 12:50   ` Joey Gouly
2025-06-11 10:48 ` [PATCH v9 29/43] arm64: RME: Always use 4k pages for realms Steven Price
2025-06-11 10:48 ` [PATCH v9 30/43] arm64: RME: Prevent Device mappings for Realms Steven Price
2025-06-11 10:48 ` [PATCH v9 31/43] arm_pmu: Provide a mechanism for disabling the physical IRQ Steven Price
2025-06-11 10:48 ` [PATCH v9 32/43] arm64: RME: Enable PMU support with a realm guest Steven Price
2025-06-11 10:48 ` [PATCH v9 33/43] arm64: RME: Hide KVM_CAP_READONLY_MEM for realm guests Steven Price
2025-06-11 10:48 ` [PATCH v9 34/43] arm64: RME: Propagate number of breakpoints and watchpoints to userspace Steven Price
2025-07-24 10:20   ` Joey Gouly
2025-06-11 10:48 ` [PATCH v9 35/43] arm64: RME: Set breakpoint parameters through SET_ONE_REG Steven Price
2025-06-11 10:48 ` [PATCH v9 36/43] arm64: RME: Initialize PMCR.N with number counter supported by RMM Steven Price
2025-07-24 10:47   ` Joey Gouly
2025-06-11 10:48 ` [PATCH v9 37/43] arm64: RME: Propagate max SVE vector length from RMM Steven Price
2025-06-11 10:48 ` [PATCH v9 38/43] arm64: RME: Configure max SVE vector length for a Realm Steven Price
2025-06-11 10:48 ` [PATCH v9 39/43] arm64: RME: Provide register list for unfinalized RME RECs Steven Price
2025-06-11 10:48 ` [PATCH v9 40/43] arm64: RME: Provide accurate register list Steven Price
2025-06-11 10:48 ` [PATCH v9 41/43] KVM: arm64: Expose support for private memory Steven Price
2025-06-12 15:14   ` Joey Gouly
2025-06-12 15:32     ` Steven Price
2025-06-11 10:48 ` [PATCH v9 42/43] KVM: arm64: Expose KVM_ARM_VCPU_REC to user space Steven Price
2025-06-11 10:48 ` [PATCH v9 43/43] KVM: arm64: Allow activating realms Steven Price
2025-06-25  1:51 ` [PATCH v9 00/43] arm64: Support for Arm CCA in KVM Emi Kisanuki (Fujitsu)
2025-06-27 10:37   ` Steven Price
2025-07-04  4:58   ` Gavin Shan

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=8757342e-26e6-467c-a469-0ac1120bcdd9@arm.com \
    --to=steven.price@arm.com \
    --cc=alexandru.elisei@arm.com \
    --cc=alpergun@google.com \
    --cc=aneesh.kumar@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=fj0570is@fujitsu.com \
    --cc=gankulkarni@os.amperecomputing.com \
    --cc=gshan@redhat.com \
    --cc=james.morse@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=sdonthineni@nvidia.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.com \
    --cc=will@kernel.org \
    --cc=yuzenghui@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 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).