qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org,
	"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Marcelo Tosatti" <mtosatti@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Kevin Wolf" <kwolf@redhat.com>
Subject: Re: [RFC PATCH v4 2/3] target/i386: Restrict system-specific features from user emulation
Date: Tue, 12 Sep 2023 16:05:19 +0200	[thread overview]
Message-ID: <c33130ec-661a-a1ed-c285-eeaa52365358@redhat.com> (raw)
In-Reply-To: <20230911211317.28773-3-philmd@linaro.org>

On 9/11/23 23:13, Philippe Mathieu-Daudé wrote:
>   /*
>    * Only for builtin_x86_defs models initialized with x86_register_cpudef_types.
>    */
> @@ -6163,6 +6195,7 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index, uint32_t count,
>               }
>               *edx = env->features[FEAT_7_0_EDX]; /* Feature flags */
>   
> +#ifndef CONFIG_USER_ONLY
>               /*
>                * SGX cannot be emulated in software.  If hardware does not
>                * support enabling SGX and/or SGX flexible launch control,
> @@ -6181,6 +6214,7 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index, uint32_t count,
>                       CPUID_7_0_ECX_SGX_LC))) {
>                   *ecx &= ~CPUID_7_0_ECX_SGX_LC;
>               }
> +#endif

This can use a variant of x86_cpu_get_supported_cpuid that returns a 
single register; or it can be rewritten to use x86_cpu_get_supported_cpuid.

In general, a lot of checks for accel_uses_host_cpuid() are unnecessary, 
and the code can be modified to not depend on either KVM or HVF.

>           } else if (count == 1) {
>               *eax = env->features[FEAT_7_1_EAX];
>               *edx = env->features[FEAT_7_1_EDX];
> @@ -6876,6 +6910,8 @@ static void mce_init(X86CPU *cpu)
>       }
>   }
>   
> +#ifndef CONFIG_USER_ONLY
> +
>   static void x86_cpu_adjust_level(X86CPU *cpu, uint32_t *min, uint32_t value)
>   {
>       if (*min < value) {
> @@ -6948,6 +6984,8 @@ static void x86_cpu_enable_xsave_components(X86CPU *cpu)
>       env->features[FEAT_XSAVE_XSS_HI] = mask >> 32;
>   }
>   
> +#endif /* !CONFIG_USER_ONLY */

These functions should all be used in user-mode emulation as well.

>   /***** Steps involved on loading and filtering CPUID data
>    *
>    * When initializing and realizing a CPU object, the steps
> @@ -7040,6 +7078,7 @@ void x86_cpu_expand_features(X86CPU *cpu, Error **errp)
>           }
>       }
>   
> +#ifndef CONFIG_USER_ONLY
>       if (!kvm_enabled() || !cpu->expose_kvm) {
>           env->features[FEAT_KVM] = 0;
>       }

This is "!kvm_enabled()" so it should be kept for user-mode emulation.

> @@ -7111,6 +7150,8 @@ void x86_cpu_expand_features(X86CPU *cpu, Error **errp)
>           return;
>       }
>   
> +#endif /* !CONFIG_USER_ONLY */
>       /* Set cpuid_*level* based on cpuid_min_*level, if not explicitly set */
>       if (env->cpuid_level_func7 == UINT32_MAX) {
>           env->cpuid_level_func7 = env->cpuid_min_level_func7;
> @@ -7152,6 +7193,7 @@ static void x86_cpu_filter_features(X86CPU *cpu, bool verbose)
>           mark_unavailable_features(cpu, w, unavailable_features, prefix);
>       }
>   
> +#ifndef CONFIG_USER_ONLY
>       if ((env->features[FEAT_7_0_EBX] & CPUID_7_0_EBX_INTEL_PT) &&
>           kvm_enabled()) {
>           KVMState *s = CPU(cpu)->kvm_state;
> @@ -7179,6 +7221,7 @@ static void x86_cpu_filter_features(X86CPU *cpu, bool verbose)
>               mark_unavailable_features(cpu, FEAT_7_0_EBX, CPUID_7_0_EBX_INTEL_PT, prefix);
>           }
>       }
> +#endif

This need not be limited to KVM, it can likewise use 
x86_cpu_get_supported_cpuid.

Paolo

>   }
>   
>   static void x86_cpu_hyperv_realize(X86CPU *cpu)



  reply	other threads:[~2023-09-12 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 21:13 [PATCH v4 0/3] target/i386: Restrict system-specific features from user emulation Philippe Mathieu-Daudé
2023-09-11 21:13 ` [PATCH v4 1/3] target/i386: Check kvm_hyperv_expand_features() return value Philippe Mathieu-Daudé
2023-09-11 21:13 ` [RFC PATCH v4 2/3] target/i386: Restrict system-specific features from user emulation Philippe Mathieu-Daudé
2023-09-12 14:05   ` Paolo Bonzini [this message]
2023-09-13  9:02     ` Philippe Mathieu-Daudé
2023-09-11 21:13 ` [PATCH v4 3/3] target/i386: Prohibit target specific KVM prototypes on " Philippe Mathieu-Daudé
2023-09-12 14:07 ` [PATCH v4 0/3] target/i386: Restrict system-specific features from " Paolo Bonzini
2023-09-12 16:44   ` Philippe Mathieu-Daudé
2023-09-12 17:25     ` Paolo Bonzini
2023-09-13  9:26       ` 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=c33130ec-661a-a1ed-c285-eeaa52365358@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=mtosatti@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@redhat.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).