On Wed, 03 Feb, at 12:33:10PM, Ard Biesheuvel wrote:
> On 3 February 2016 at 11:58, Ingo Molnar wrote:
> >
> > * Ard Biesheuvel wrote:
> >
> >> > More fundamentally, this makes me nervous:
> >> >
> >> > > The UEFI spec allows Runtime Services to be invoked with interrupts
> >> > > enabled.
On 3 February 2016 at 11:58, Ingo Molnar wrote:
>
> * Ard Biesheuvel wrote:
>
>> > More fundamentally, this makes me nervous:
>> >
>> > > The UEFI spec allows Runtime Services to be invoked with interrupts
>> > > enabled. [...]
>> >
>> > So what really matters is not what the spec says, but
* Ard Biesheuvel wrote:
> > More fundamentally, this makes me nervous:
> >
> > > The UEFI spec allows Runtime Services to be invoked with interrupts
> > > enabled. [...]
> >
> > So what really matters is not what the spec says, but how Windows executes
> > UEFI firmware code in practice.
>
On 3 February 2016 at 10:43, Ingo Molnar wrote:
>
> * Matt Fleming wrote:
>
>> From: Ard Biesheuvel
>>
>> The UEFI spec allows Runtime Services to be invoked with interrupts
>> enabled. The only reason we were disabling interrupts was to prevent
>> recursive calls into the services on the same
* Matt Fleming wrote:
> From: Ard Biesheuvel
>
> The UEFI spec allows Runtime Services to be invoked with interrupts
> enabled. The only reason we were disabling interrupts was to prevent
> recursive calls into the services on the same CPU, which will lead to
> deadlock. However, the only
* Matt Fleming wrote:
> From: Ard Biesheuvel
>
> The UEFI spec allows Runtime Services to be invoked with interrupts
> enabled. The only reason we were disabling interrupts was to prevent
> recursive calls into the services on the same CPU,
On 3 February 2016 at 11:58, Ingo Molnar wrote:
>
> * Ard Biesheuvel wrote:
>
>> > More fundamentally, this makes me nervous:
>> >
>> > > The UEFI spec allows Runtime Services to be invoked with interrupts
>> > > enabled. [...]
>> >
>> > So what
On 3 February 2016 at 10:43, Ingo Molnar wrote:
>
> * Matt Fleming wrote:
>
>> From: Ard Biesheuvel
>>
>> The UEFI spec allows Runtime Services to be invoked with interrupts
>> enabled. The only reason we were disabling
* Ard Biesheuvel wrote:
> > More fundamentally, this makes me nervous:
> >
> > > The UEFI spec allows Runtime Services to be invoked with interrupts
> > > enabled. [...]
> >
> > So what really matters is not what the spec says, but how Windows executes
> > UEFI
On Wed, 03 Feb, at 12:33:10PM, Ard Biesheuvel wrote:
> On 3 February 2016 at 11:58, Ingo Molnar wrote:
> >
> > * Ard Biesheuvel wrote:
> >
> >> > More fundamentally, this makes me nervous:
> >> >
> >> > > The UEFI spec allows Runtime Services to be
From: Ard Biesheuvel
The UEFI spec allows Runtime Services to be invoked with interrupts
enabled. The only reason we were disabling interrupts was to prevent
recursive calls into the services on the same CPU, which will lead to
deadlock. However, the only context where such invocations may occur
From: Ard Biesheuvel
The UEFI spec allows Runtime Services to be invoked with interrupts
enabled. The only reason we were disabling interrupts was to prevent
recursive calls into the services on the same CPU, which will lead to
deadlock. However, the only context where
12 matches
Mail list logo