On Tue, 19 Jun 2018, Andy Lutomirski wrote:
> On Jun 19, 2018, at 9:15 AM, Siarhei Liakh
> wrote:
>
> > On Mon, 18 Jun 2018, Andy Lutomirski wrote:
> >
> > > > On Thu, Jun 14, 2018 at 10:10 PM Siarhei Liakh
> > > > wrote:
> > > > >
> > > > > fpu__drop() has an explicit fwait which under so
> On Jun 18, 2018, at 11:23 PM, Thomas Gleixner wrote:
>
>> On Mon, 18 Jun 2018, Andy Lutomirski wrote:
>>
>> On Thu, Jun 14, 2018 at 10:10 PM Siarhei Liakh
>> wrote:
>>>
>>> fpu__drop() has an explicit fwait which under some conditions can trigger
>>> a fixable FPU exception while in kerne
On Mon, 18 Jun 2018, Andy Lutomirski wrote:
> On Thu, Jun 14, 2018 at 10:10 PM Siarhei Liakh
> wrote:
> >
> > fpu__drop() has an explicit fwait which under some conditions can trigger
> > a fixable FPU exception while in kernel. Thus, we should attempt to fixup
> > the exception first, and only c
On Thu, Jun 14, 2018 at 10:10 PM Siarhei Liakh
wrote:
>
> fpu__drop() has an explicit fwait which under some conditions can trigger
> a fixable FPU exception while in kernel. Thus, we should attempt to fixup
> the exception first, and only call notify_die() if the fixup failed just
> like in do_ge
fpu__drop() has an explicit fwait which under some conditions can trigger
a fixable FPU exception while in kernel. Thus, we should attempt to fixup
the exception first, and only call notify_die() if the fixup failed just
like in do_general_protection(). The original call sequence incorrectly
trigge
5 matches
Mail list logo