Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1286841 > unrolled thread

x86 fpu: command-line parameters broken post-FPU-rewrite

Back to article view | Back to linux.kernel

Contents

  x86 fpu: command-line parameters broken post-FPU-rewrite Dave Hansen <dave.hansen@intel.com> - 2015-12-08 21:50 +0100
    Re: x86 fpu: command-line parameters broken post-FPU-rewrite Ingo Molnar <mingo@kernel.org> - 2015-12-09 09:40 +0100
      Re: x86 fpu: command-line parameters broken post-FPU-rewrite Borislav Petkov <bp@alien8.de> - 2015-12-09 20:20 +0100

#1286841 — x86 fpu: command-line parameters broken post-FPU-rewrite

Hey Ingo,

We were starting to look at reenabling XSAVES support and tried to use
the 'noxsave' and 'noxsaves' kernel command-line options.  The rewrite
moved the FPU initialization to before we even are parsing command-line
options, even the early_param()s.

Do you have any preferences on how it gets fixed?

The most obvious thing would be to just defer as much of the FPU setup
as we can until after parse_early_param() has happened.  The only other
think I can think of doing would be to try to do some *really* early,
simple, command-line parsing to look for 'noxsave' and friends.

Thoughts?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1287191

* Dave Hansen <dave.hansen@intel.com> wrote:

> Hey Ingo,
> 
> We were starting to look at reenabling XSAVES support and tried to use the 
> 'noxsave' and 'noxsaves' kernel command-line options.  The rewrite moved the FPU 
> initialization to before we even are parsing command-line options, even the 
> early_param()s.
> 
> Do you have any preferences on how it gets fixed?
> 
> The most obvious thing would be to just defer as much of the FPU setup as we can 
> until after parse_early_param() has happened.  The only other think I can think 
> of doing would be to try to do some *really* early, simple, command-line parsing 
> to look for 'noxsave' and friends.
> 
> Thoughts?

Hm, so given that having the FPU operational is key to a functioning kernel (and 
other kernel subsystems may make use of FPU functionality), I'd rather bring 
option parsing earlier than change the FPU setup sequence. FPU setup should be 
done when we identify the CPU - not 'very late' as we used to.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]

#1287752

On Wed, Dec 09, 2015 at 09:32:10AM +0100, Ingo Molnar wrote:
> 
> * Dave Hansen <dave.hansen@intel.com> wrote:
> 
> > Hey Ingo,
> > 
> > We were starting to look at reenabling XSAVES support and tried to use the 
> > 'noxsave' and 'noxsaves' kernel command-line options.  The rewrite moved the FPU 
> > initialization to before we even are parsing command-line options, even the 
> > early_param()s.
> > 
> > Do you have any preferences on how it gets fixed?
> > 
> > The most obvious thing would be to just defer as much of the FPU setup as we can 
> > until after parse_early_param() has happened.  The only other think I can think 
> > of doing would be to try to do some *really* early, simple, command-line parsing 
> > to look for 'noxsave' and friends.
> > 
> > Thoughts?
> 
> Hm, so given that having the FPU operational is key to a functioning kernel (and 
> other kernel subsystems may make use of FPU functionality), I'd rather bring 
> option parsing earlier than change the FPU setup sequence. FPU setup should be 
> done when we identify the CPU - not 'very late' as we used to.

We already have early cmdline parsing: arch/x86/lib/cmdline.c

See users for examples.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web