All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [RFC PATCH 07/11] target/arm: Replace kvm_arm_pmu_supported by host_cpu_feature_supported
Date: Tue, 12 Aug 2025 22:42:59 +1000	[thread overview]
Message-ID: <9fd617db-8ea4-49b5-98f7-0b949b02f26a@linaro.org> (raw)
In-Reply-To: <cb6e02cc-1959-419a-bafa-5bb43818c159@linaro.org>

On 8/12/25 17:33, Philippe Mathieu-Daudé wrote:
>>>>> -    if (kvm_arm_pmu_supported()) {
>>>>> +    if (host_cpu_feature_supported(ARM_FEATURE_PMU, false)) {
>>>>
>>>> Why is false correct here?  Alternately, in the next patch, why is it correct to pass 
>>>> true for the EL2 test?
>>>
>>> I think I copied to KVM the HVF use, adapted on top of:
>>> https://lore.kernel.org/qemu-devel/20250808070137.48716-12- mohamed@unpredictable.fr/
>>>
>>>>
>>>> What is the purpose of the can_emulate parameter at all?
>>>
>>> When using split-accel on pre-M3, we might emulate EL2:
>>>
>>>         |   feat            |    can_emulate   |    retval
>>>         +   ----            +      -----       +     ----
>>  > M1/M2  |  ARM_FEATURE_EL2         false            false> M1/M2  | 
>> ARM_FEATURE_EL2         true             true
>>> M3/M4  |  ARM_FEATURE_EL2         any              true
>>
>> For example in hvf.c:
>>
>> static bool hvf_arm_get_host_cpu_features(ARMHostCPUFeatures *ahcf)
>> {
>>      ...
>>      if (host_cpu_feature_supported(ARM_FEATURE_EL2, true)) {
>>          ahcf->features |= 1ULL << ARM_FEATURE_EL2;
>>      }
>>
>> and then only when split-accel is not enabled:
>>
>> hv_return_t hvf_arch_vm_create(MachineState *ms, uint32_t pa_range)
>> {
>>      ...
>>      if (host_cpu_feature_supported(ARM_FEATURE_EL2, false)) {
>>          ret = hv_vm_config_set_el2_enabled(config, true);
>>          if (ret != HV_SUCCESS) {
>>              goto cleanup;
>>          }
>>      }
>>
> 
> What I'm looking for:
> 
> - Is this feature supported BY HW?
> 
>    -> hw_init_feature
> 
> - Is this feature supported BY SW?
> 
>    -> sw_init_feature
> 
> - Is this feature supported BY ANY?
> 
>    -> do smth with feature
> 
> With split-accel, this isn't specific to HVF/ARM.
> 
> I can use a tri-state enum { ANY, HW, SW }.

My point, I guess, is:  tcg_enabled() appears to be the only correct setting for 
can_emulate, and since that's the case, it's clearer to not have the parameter and simply 
test can_emulate within any subroutines.


r~


  reply	other threads:[~2025-08-12 12:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 17:06 [RFC PATCH 00/11] target/arm: Introduce host_cpu_feature_supported() API Philippe Mathieu-Daudé
2025-08-11 17:06 ` [RFC PATCH 01/11] accel/system: Introduce hwaccel_enabled() helper Philippe Mathieu-Daudé
2025-08-11 17:06 ` [RFC PATCH 02/11] target/arm: Use generic hwaccel_enabled() to check 'host' cpu type Philippe Mathieu-Daudé
2025-08-11 17:06 ` [RFC PATCH 03/11] target/arm: Restrict PMU to system mode Philippe Mathieu-Daudé
2025-08-12  0:02   ` Richard Henderson
2025-08-11 17:06 ` [RFC PATCH 04/11] target/arm: Factor hvf_psci_get_target_el() out Philippe Mathieu-Daudé
2025-08-12  0:26   ` Richard Henderson
2025-08-11 17:06 ` [RFC PATCH 05/11] target/arm: Introduce arm_hw_accel_cpu_feature_supported() Philippe Mathieu-Daudé
2025-08-12  0:35   ` Richard Henderson
2025-08-12  4:06     ` Philippe Mathieu-Daudé
2025-08-12  4:58     ` Philippe Mathieu-Daudé
2025-08-11 17:06 ` [RFC PATCH 06/11] target/arm: Introduce host_cpu_feature_supported() Philippe Mathieu-Daudé
2025-08-12  0:44   ` Richard Henderson
2025-08-12  4:30     ` Philippe Mathieu-Daudé
2025-08-11 17:06 ` [RFC PATCH 07/11] target/arm: Replace kvm_arm_pmu_supported by host_cpu_feature_supported Philippe Mathieu-Daudé
2025-08-12  0:48   ` Richard Henderson
2025-08-12  4:49     ` Philippe Mathieu-Daudé
2025-08-12  6:03       ` Philippe Mathieu-Daudé
2025-08-12  7:33         ` Philippe Mathieu-Daudé
2025-08-12 12:42           ` Richard Henderson [this message]
2025-08-12 13:12             ` Philippe Mathieu-Daudé
2025-08-11 17:06 ` [RFC PATCH 08/11] target/arm: Replace kvm_arm_el2_supported " Philippe Mathieu-Daudé
2025-08-11 17:06 ` [RFC PATCH 09/11] target/arm/hvf: Sync registers used at EL2 Philippe Mathieu-Daudé
2025-08-12  0:20   ` Richard Henderson
2025-08-13  7:20     ` Philippe Mathieu-Daudé
2025-08-11 17:06 ` [RFC PATCH 10/11] target/arm/hvf: Consider EL2 acceleration for Silicon M3+ chipsets Philippe Mathieu-Daudé
2025-08-11 17:06 ` [RFC PATCH 11/11] target/arm/hvf: Allow EL2/EL3 emulation on Silicon M1 / M2 Philippe Mathieu-Daudé
2025-08-12  0:23   ` Richard Henderson
2025-08-12  3:56     ` Philippe Mathieu-Daudé

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=9fd617db-8ea4-49b5-98f7-0b949b02f26a@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=philmd@linaro.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.