All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
	Kevin Tian <kevin.tian@intel.com>,
	Jun Nakajima <jun.nakajima@intel.com>
Subject: Re: [PATCH v3 02/12] x86/HVM: improve CET-IBT pruning of ENDBR
Date: Thu, 23 Jan 2025 13:41:51 +0100	[thread overview]
Message-ID: <Z5I5D_uVxijLF6sK@macbook.local> (raw)
In-Reply-To: <537b0d9c-1936-4cf5-a012-d50b1097a22d@suse.com>

On Mon, Feb 26, 2024 at 05:42:20PM +0100, Jan Beulich wrote:
> __init{const,data}_cf_clobber can have an effect only for pointers
> actually populated in the respective tables. While not the case for SVM
> right now, VMX installs a number of pointers only under certain
> conditions. Hence the respective functions would have their ENDBR purged
> only when those conditions are met. Invoke "pruning" functions after
> having copied the respective tables, for them to install any "missing"
> pointers.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> ---
> This is largely cosmetic for present hardware, which when supporting
> CET-IBT likely also supports all of the advanced VMX features for which
> hook pointers are installed conditionally. The only case this would make
> a difference there is when use of respective features was suppressed via
> command line option (where available). For future hooks it may end up
> relevant even by default, and it also would be if AMD started supporting
> CET-IBT; right now it matters only for .pi_update_irte, as iommu_intpost
> continues to default to off.
> 
> Originally I had meant to put the SVM and VMX functions in presmp-
> initcalls, but hvm/{svm,vmx}/built_in.o are linked into hvm/built_in.o
> before hvm/hvm.o. And I don't think I want to fiddle with link order
> here.
> ---
> v3: Re-base.
> v2: Use cpu_has_xen_ibt in prune_{svm,vmx}().
> 
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -161,10 +161,15 @@ static int __init cf_check hvm_enable(vo
>      else if ( cpu_has_svm )
>          fns = start_svm();
>  
> +    if ( fns )
> +        hvm_funcs = *fns;
> +
> +    prune_vmx();
> +    prune_svm();

Isn't it actually the opposite of pruning.  What the helpers do is
fill all the pointers in the structure.  I would rather name them
{vmx,svm}_fill_hvm_funcs() or similar.  And possibly pull the
cpu_has_xen_ibt check outside the functions:

if ( cpu_has_xen_ibt )
{
    /*
     * Now that svm_function_table was copied, populate all function pointers
     * which may have been left at NULL, for __initdata_cf_clobber to have as
     * much of an effect as possible.
     */
    vmx_fill_hvm_funcs();
    svm_fill_hvm_funcs();
}

I would be nice to avoid directly exporting more vmx and smv specific
helpers, as if we ever want to compile out vmx or svm it would be more
churn to deal with those.  I however cannot think of any good way to
do this here, so it's fine to export those functions.

Thanks, Roger.


  reply	other threads:[~2025-01-23 12:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 16:40 [PATCH v3 00/12] x86/HVM: misc tidying Jan Beulich
2024-02-26 16:42 ` [PATCH v3 01/12] VMX: don't run with CR4.VMXE set when VMX could not be enabled Jan Beulich
2025-01-24 10:25   ` Roger Pau Monné
2024-02-26 16:42 ` [PATCH v3 02/12] x86/HVM: improve CET-IBT pruning of ENDBR Jan Beulich
2025-01-23 12:41   ` Roger Pau Monné [this message]
2025-01-23 13:18     ` Jan Beulich
2025-01-23 14:24       ` Roger Pau Monné
2025-01-23 16:14         ` Jan Beulich
2025-01-24  9:16           ` Roger Pau Monné
2024-02-26 16:42 ` [PATCH v3 03/12] VMX: drop vmcs_revision_id Jan Beulich
2025-01-24 10:51   ` Roger Pau Monné
2025-01-24 11:02     ` Roger Pau Monné
2024-02-26 16:43 ` [PATCH v3 04/12] VMX: convert vmx_basic_msr Jan Beulich
2025-01-24 10:57   ` Roger Pau Monné
2024-02-26 16:43 ` [PATCH v3 05/12] VMX: convert vmx_pin_based_exec_control Jan Beulich
2024-02-26 16:43 ` [PATCH v3 06/12] VMX: convert vmx_cpu_based_exec_control Jan Beulich
2024-02-26 16:44 ` [PATCH v3 07/12] VMX: convert vmx_secondary_exec_control Jan Beulich
2024-02-26 16:44 ` [PATCH v3 08/12] VMX: convert vmx_tertiary_exec_control Jan Beulich
2024-02-26 16:45 ` [PATCH v3 09/12] VMX: convert vmx_vmexit_control Jan Beulich
2024-02-26 16:45 ` [PATCH v3 10/12] VMX: convert vmx_vmentry_control Jan Beulich
2024-02-26 16:45 ` [PATCH v3 11/12] VMX: convert vmx_ept_vpid_cap Jan Beulich
2024-02-26 16:46 ` [PATCH v3 12/12] VMX: convert vmx_vmfunc Jan Beulich
2025-01-24 11:09 ` [PATCH v3 00/12] x86/HVM: misc tidying Roger Pau Monné

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=Z5I5D_uVxijLF6sK@macbook.local \
    --to=roger.pau@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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.