On Mon, Feb 16, 2015 at 07:14:17PM +0100, Oleg Nesterov wrote:
> Should I resend?
No need, I've changed it before applying. :-)
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On 02/16, Rik van Riel wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 02/16/2015 12:04 PM, Borislav Petkov wrote:
>
> > ... and so by looking at the unlazy_fpu() call sites, I think this
> > makes sense.
> >
> > So how's that for a commit message instead:
> >
> > --- x86, fpu,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/16/2015 12:04 PM, Borislav Petkov wrote:
> ... and so by looking at the unlazy_fpu() call sites, I think this
> makes sense.
>
> So how's that for a commit message instead:
>
> --- x86, fpu, unlazy_fpu: Don't reset thread.fpu_counter
>
> The
On Fri, Feb 06, 2015 at 03:01:58PM -0500, r...@redhat.com wrote:
> From: Oleg Nesterov
>
> It is not clear why the "else" branch clears ->fpu_counter, this makes
> no sense.
See below for why.
> If use_eager_fpu() then this has no effect. Otherwise, if we actually
> wanted to prevent fpu
On Fri, Feb 06, 2015 at 03:01:58PM -0500, r...@redhat.com wrote:
From: Oleg Nesterov o...@redhat.com
It is not clear why the else branch clears -fpu_counter, this makes
no sense.
See below for why.
If use_eager_fpu() then this has no effect. Otherwise, if we actually
wanted to prevent fpu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/16/2015 12:04 PM, Borislav Petkov wrote:
... and so by looking at the unlazy_fpu() call sites, I think this
makes sense.
So how's that for a commit message instead:
--- x86, fpu, unlazy_fpu: Don't reset thread.fpu_counter
The else
On Mon, Feb 16, 2015 at 07:14:17PM +0100, Oleg Nesterov wrote:
Should I resend?
No need, I've changed it before applying. :-)
Thanks.
--
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
On 02/16, Rik van Riel wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/16/2015 12:04 PM, Borislav Petkov wrote:
... and so by looking at the unlazy_fpu() call sites, I think this
makes sense.
So how's that for a commit message instead:
--- x86, fpu, unlazy_fpu: Don't
From: Oleg Nesterov
It is not clear why the "else" branch clears ->fpu_counter, this makes
no sense.
If use_eager_fpu() then this has no effect. Otherwise, if we actually
wanted to prevent fpu preload after the context switch we would need to
reset it unconditionally, even if
From: Oleg Nesterov o...@redhat.com
It is not clear why the else branch clears -fpu_counter, this makes
no sense.
If use_eager_fpu() then this has no effect. Otherwise, if we actually
wanted to prevent fpu preload after the context switch we would need to
reset it unconditionally, even if
10 matches
Mail list logo