Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Chang S. Bae" <chang.seok.bae@intel.com>
Cc: luto@kernel.org, tglx@linutronix.de, mingo@kernel.org,
	x86@kernel.org, len.brown@intel.com, dave.hansen@intel.com,
	thiago.macieira@intel.com, jing2.liu@intel.com,
	ravi.v.shankar@intel.com, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org
Subject: Re: [PATCH v9 05/26] x86/fpu/xstate: Add new variables to indicate dynamic XSTATE buffer size
Date: Thu, 12 Aug 2021 17:03:15 +0200	[thread overview]
Message-ID: <YRU4M6FO0OHc67Wx@zn.tnic> (raw)
In-Reply-To: <20210730145957.7927-6-chang.seok.bae@intel.com>

On Fri, Jul 30, 2021 at 07:59:36AM -0700, Chang S. Bae wrote:
> @@ -167,8 +158,10 @@ static void __init fpu__init_task_struct_size(void)
>  	/*
>  	 * Add back the dynamically-calculated register state
>  	 * size.
> +	 *
> +	 * Use the minimum size as embedded to task_struct.

embedded in...

> diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/x86/kernel/fpu/xstate.c
> index 74e608c6ad6c..12caf1a56ce0 100644
> --- a/arch/x86/kernel/fpu/xstate.c
> +++ b/arch/x86/kernel/fpu/xstate.c
> @@ -77,12 +77,51 @@ static unsigned int xstate_comp_offsets[XFEATURE_MAX] __ro_after_init =
>  static unsigned int xstate_supervisor_only_offsets[XFEATURE_MAX] __ro_after_init =
>  	{ [ 0 ... XFEATURE_MAX - 1] = -1};
>  
> -/*
> - * The XSAVE area of kernel can be in standard or compacted format;
> - * it is always in standard format for user mode. This is the user
> - * mode standard format size used for signal and ptrace frames.
> +/**
> + * struct fpu_xstate_buffer_config - xstate buffer configuration
> + * @max_size:			The CPUID-enumerated all-feature "maximum" size
> + *				for xstate per-task buffer.
> + * @min_size:			The size to fit into the statically-allocated
> + *				buffer. With dynamic states, this buffer no longer
> + *				contains all the enabled state components.
> + * @user_size:			The size of user-space buffer for signal and
> + *				ptrace frames, in the non-compacted format.
>   */
> -unsigned int fpu_user_xstate_size __ro_after_init;
> +struct fpu_xstate_buffer_config {
> +	unsigned int min_size, max_size;
> +	unsigned int user_size;
> +};
> +
> +static struct fpu_xstate_buffer_config buffer_config __ro_after_init;

I know I had asked for the accessors below but if this is going to be
read-only after init and is not going to change for duration of the
system lifetime, then you don't really need those accessors.

I.e., you can do

struct fpu_xstate_buffer_config {
	unsigned int min_size, max_size;
	unsigned int user_size;
};

static struct fpu_xstate_buffer_config fpu_buf_cfg __ro_after_init;

and then access those values through fpu_buf_cfg.<value>

Thx.

> +
> +unsigned int get_xstate_config(enum xstate_config cfg)
> +{
> +	switch (cfg) {
> +	case XSTATE_MIN_SIZE:
> +		return buffer_config.min_size;
> +	case XSTATE_MAX_SIZE:
> +		return buffer_config.max_size;
> +	case XSTATE_USER_SIZE:
> +		return buffer_config.user_size;
> +	default:
> +		return 0;
> +	}
> +}
> +EXPORT_SYMBOL_GPL(get_xstate_config);
> +
> +void set_xstate_config(enum xstate_config cfg, unsigned int value)
> +{
> +	switch (cfg) {
> +	case XSTATE_MIN_SIZE:
> +		buffer_config.min_size = value;
> +		break;
> +	case XSTATE_MAX_SIZE:
> +		buffer_config.max_size = value;
> +		break;
> +	case XSTATE_USER_SIZE:
> +		buffer_config.user_size = value;
> +	}
> +}

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2021-08-12 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210730145957.7927-1-chang.seok.bae@intel.com>
2021-07-30 14:59 ` [PATCH v9 01/26] x86/fpu/xstate: Modify the initialization helper to handle both static and dynamic buffers Chang S. Bae
2021-07-30 14:59 ` [PATCH v9 03/26] x86/fpu/xstate: Modify address finders " Chang S. Bae
2021-07-30 14:59 ` [PATCH v9 05/26] x86/fpu/xstate: Add new variables to indicate dynamic XSTATE buffer size Chang S. Bae
2021-08-12 15:03   ` Borislav Petkov [this message]
2021-07-30 14:59 ` [PATCH v9 07/26] x86/fpu/xstate: Convert the struct fpu 'state' field to a pointer Chang S. Bae
2021-08-12 17:09   ` Borislav Petkov
2021-07-30 14:59 ` [PATCH v9 09/26] x86/fpu/xstate: Update the XSTATE save function to support dynamic states Chang S. Bae

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=YRU4M6FO0OHc67Wx@zn.tnic \
    --to=bp@alien8.de \
    --cc=chang.seok.bae@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=jing2.liu@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=ravi.v.shankar@intel.com \
    --cc=tglx@linutronix.de \
    --cc=thiago.macieira@intel.com \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox