This is a note to let you know that I've just added the patch titled
x86/cpu: Fix SMAP check in PVOPS environments
to the 4.3-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
x86-cpu-fi
This is a note to let you know that I've just added the patch titled
x86/cpu: Fix SMAP check in PVOPS environments
to the 4.2-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
x86-cpu-fi
This is a note to let you know that I've just added the patch titled
x86/cpu: Fix SMAP check in PVOPS environments
to the 3.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
x86-cpu-f
This is a note to let you know that I've just added the patch titled
x86/cpu: Fix SMAP check in PVOPS environments
to the 3.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
x86-cpu-f
This is a note to let you know that I've just added the patch titled
x86/cpu: Fix SMAP check in PVOPS environments
to the 4.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
x86-cpu-fi
Ping?
None of the discussion on this thread altered the contents of this
patch, and the bug is still present.
~Andrew
On 03/06/15 10:31, Andrew Cooper wrote:
> There appears to be no formal statement of what pv_irq_ops.save_fl() is
> supposed to return precisely. Native returns the full flags,
On 05/06/15 03:58, Rusty Russell wrote:
>
> Subject: x86: rename save_fl/restore_fl paravirt ops to highlight eflags.
> From: Rusty Russell
>
> As the comment in arch/x86/include/asm/paravirt_types.h says:
>
>* Get/set interrupt state. save_fl and restore_fl are only
>* expecte
* Rusty Russell wrote:
> As the comment in arch/x86/include/asm/paravirt_types.h says:
>
>* Get/set interrupt state. save_fl and restore_fl are only
>* expected to use X86_EFLAGS_IF; all other bits
>* returned from save_fl are undefined, and may be ignored by
>*
"H. Peter Anvin" writes:
> On 06/04/2015 12:55 PM, Rusty Russell wrote:
>>
>> Yeah, hard cases make bad law.
>>
>> I'm not too unhappy with this fix; ideally we'd rename save_fl and
>> restore_fl to save_eflags_if and restore_eflags_if too.
>>
>
> I would be fine with this... but please documen
On 06/04/2015 12:55 PM, Rusty Russell wrote:
>
> Yeah, hard cases make bad law.
>
> I'm not too unhappy with this fix; ideally we'd rename save_fl and
> restore_fl to save_eflags_if and restore_eflags_if too.
>
I would be fine with this... but please document what the bloody
semantics of pvops
Andrew Cooper writes:
> On 04/06/15 07:38, H. Peter Anvin wrote:
>> On 06/03/2015 02:31 AM, Andrew Cooper wrote:
>>> There appears to be no formal statement of what pv_irq_ops.save_fl() is
>>> supposed to return precisely. Native returns the full flags, while lguest
>>> and
>>> Xen only return t
On 04/06/15 07:38, H. Peter Anvin wrote:
> On 06/03/2015 02:31 AM, Andrew Cooper wrote:
>> There appears to be no formal statement of what pv_irq_ops.save_fl() is
>> supposed to return precisely. Native returns the full flags, while lguest
>> and
>> Xen only return the Interrupt Flag, and both ha
On 06/03/2015 02:31 AM, Andrew Cooper wrote:
> There appears to be no formal statement of what pv_irq_ops.save_fl() is
> supposed to return precisely. Native returns the full flags, while lguest and
> Xen only return the Interrupt Flag, and both have comments by the
> implementations stating that
There appears to be no formal statement of what pv_irq_ops.save_fl() is
supposed to return precisely. Native returns the full flags, while lguest and
Xen only return the Interrupt Flag, and both have comments by the
implementations stating that only the Interrupt Flag is looked at. This may
have
14 matches
Mail list logo