On Sun, Feb 21 2021 at 10:56, Chang S. Bae wrote:
> "xstate.disable=0x60000" will disable AMX on a system that has AMX compiled
> into XFEATURE_MASK_USER_ENABLED.
>
> "xstate.enable=0x60000" will enable AMX on a system that does NOT have AMX
> compiled into XFEATURE_MASK_USER_ENABLED (assuming the kernel is new enough
> to support this feature).
This makes no sense at all.
> Rename XFEATURE_MASK_USER_SUPPORTED to XFEATURE_MASK_USER_ENABLED to be
> aligned with the new parameters.
>
> While this cmdline is currently enabled only for AMX, it is intended to be
> easily enabled to be useful for future XSAVE-enabled features.
I have a hard time to map this changelog to the actual code.
> +/* All currently enabled user features */
> +#define XFEATURE_MASK_USER_ENABLED (XFEATURE_MASK_FP | \
> + XFEATURE_MASK_SSE | \
> + XFEATURE_MASK_YMM | \
> + XFEATURE_MASK_OPMASK | \
> + XFEATURE_MASK_ZMM_Hi256 | \
> + XFEATURE_MASK_Hi16_ZMM | \
> + XFEATURE_MASK_PKRU | \
> + XFEATURE_MASK_BNDREGS | \
> + XFEATURE_MASK_BNDCSR | \
> + XFEATURE_MASK_XTILE)
> +
> +static u64 xstate_enable;
> +static u64 xstate_disable;
This needs to be kept around forever because it's used where outside of
__init code?
> u64 __init fpu__get_supported_xfeatures_mask(void)
> {
> - u64 mask = XFEATURE_MASK_USER_SUPPORTED | XFEATURE_MASK_SUPERVISOR_SUPPORTED;
> -
> - if (!IS_ENABLED(CONFIG_X86_64))
> - mask &= ~(XFEATURE_MASK_XTILE);
> + u64 mask = XFEATURE_MASK_USER_ENABLED | XFEATURE_MASK_SUPERVISOR_SUPPORTED;
> +
> + if (!IS_ENABLED(CONFIG_X86_64)) {
> + mask &= ~(XFEATURE_MASK_XTILE);
> + } else if (xstate_enable || xstate_disable) {
> + u64 custom = mask;
> + u64 unknown;
> +
> + custom |= xstate_enable;
> + custom &= ~xstate_disable;
> +
> + unknown = custom & ~mask;
> + if (unknown) {
> + /*
> + * User should fully understand the result of using undocumented
> + * xstate component.
> + */
What is to understand here? Absolutely nothing. This has been tried to
be smuggled into the kernel ever so often and it's again in something
which claims to do something else and the changelog is silent about it.
The argument 'it allows easier testing of new features' is absolutely
not true simply because the rest of the kernel knows absolutely nothing
about the feature and stuff would go south anyway.
We won't enable features which are unknown ever. Keep that presilicon
test gunk where it belongs: In the Intel poison cabinet along with the
rest of the code which nobody ever want's to see.
> + }
> +
> + if ((custom & XFEATURE_MASK_XTILE) != XFEATURE_MASK_XTILE) {
> + pr_warn("x86/fpu: Error in xstate.disable. Additionally disabling 0x%x components.\n",
> + XFEATURE_MASK_XTILE);
What?
If the user added: xstate.disable=0x60000 to the command line, then the
code above:
> + custom &= ~xstate_disable;
has cleared XFEATURE_MASK_XTILE in custom which makes that check true,
the warning emitted and then
> + custom &= ~(XFEATURE_MASK_XTILE);
this part clears out XFEATURE_MASK_XTILE once more.
> + }
What the heck.
> +/*
> + * Longest parameter of 'xstate.enable=' is 22 octal number characters with '0' prefix and
> + * an extra '\0' for termination.
> + */
> +#define MAX_XSTATE_MASK_CHARS 24
> +/*
> + * We parse xstate parameters early because fpu__init_system() is executed before
> + * parse_early_param().
> + */
> +static void __init fpu__init_parse_early_param(void)
> +{
> + char arg[MAX_XSTATE_MASK_CHARS];
> +
> + if (cmdline_find_option(boot_command_line, "xstate.enable", arg, sizeof(arg)) &&
> + !kstrtoull(arg, 0, &xstate_enable))
> + xstate_enable &= XFEATURE_MASK_CONFIGURABLE;
This enable thing is not going to happen.
> + if (cmdline_find_option(boot_command_line, "xstate.disable", arg, sizeof(arg)) &&
> + !kstrtoull(arg, 0, &xstate_disable))
> + xstate_disable &= XFEATURE_MASK_CONFIGURABLE;
> +}
> +
This parser needs to be called for X86_32 because?
Thanks,
tglx
