On 01/14, Oleg Nesterov wrote:
>
> On 01/11, r...@redhat.com wrote:
> >
> > --- a/arch/x86/kernel/i387.c
> > +++ b/arch/x86/kernel/i387.c
> > @@ -89,13 +89,11 @@ void __kernel_fpu_end(void)
> > if (use_eager_fpu()) {
> > /*
> > * For eager fpu, most the time,
On 01/11, r...@redhat.com wrote:
>
> --- a/arch/x86/kernel/i387.c
> +++ b/arch/x86/kernel/i387.c
> @@ -89,13 +89,11 @@ void __kernel_fpu_end(void)
> if (use_eager_fpu()) {
> /*
>* For eager fpu, most the time, tsk_used_math() is true.
> - * Restore
On 01/14, Oleg Nesterov wrote:
On 01/11, r...@redhat.com wrote:
--- a/arch/x86/kernel/i387.c
+++ b/arch/x86/kernel/i387.c
@@ -89,13 +89,11 @@ void __kernel_fpu_end(void)
if (use_eager_fpu()) {
/*
* For eager fpu, most the time, tsk_used_math() is true.
On 01/11, r...@redhat.com wrote:
--- a/arch/x86/kernel/i387.c
+++ b/arch/x86/kernel/i387.c
@@ -89,13 +89,11 @@ void __kernel_fpu_end(void)
if (use_eager_fpu()) {
/*
* For eager fpu, most the time, tsk_used_math() is true.
- * Restore the user
From: Rik van Riel
Tasks may have multiple invocations of kernel_fpu_start and kernel_fpu_end
in sequence without ever hitting userspace in-between.
Delaying the restore of the user FPU state until the task returns to
userspace means the kernel only has to save the user FPU state on the
first
From: Rik van Riel r...@redhat.com
Tasks may have multiple invocations of kernel_fpu_start and kernel_fpu_end
in sequence without ever hitting userspace in-between.
Delaying the restore of the user FPU state until the task returns to
userspace means the kernel only has to save the user FPU state
6 matches
Mail list logo
