> On 29 Oct 2020, at 23:32, Stefano Stabellini wrote:
>
> On Thu, 29 Oct 2020, Bertrand Marquis wrote:
>> Hi Julien,
>>
>>> On 28 Oct 2020, at 18:39, Julien Grall wrote:
>>>
>>> Hi Bertrand,
>>>
>>> On 26/10/2020 16:21, Bertrand Marquis wrote:
When a Cortex A57 processor is affected b
On Thu, 29 Oct 2020, Bertrand Marquis wrote:
> Hi Julien,
>
> > On 28 Oct 2020, at 18:39, Julien Grall wrote:
> >
> > Hi Bertrand,
> >
> > On 26/10/2020 16:21, Bertrand Marquis wrote:
> >> When a Cortex A57 processor is affected by CPU errata 832075, a guest
> >> not implementing the workaround
Hi Julien,
> On 28 Oct 2020, at 18:39, Julien Grall wrote:
>
> Hi Bertrand,
>
> On 26/10/2020 16:21, Bertrand Marquis wrote:
>> When a Cortex A57 processor is affected by CPU errata 832075, a guest
>> not implementing the workaround for it could deadlock the system.
>> Add a warning during boot
On Wed, 28 Oct 2020, Julien Grall wrote:
> Hi Bertrand,
>
> On 26/10/2020 16:21, Bertrand Marquis wrote:
> > When a Cortex A57 processor is affected by CPU errata 832075, a guest
> > not implementing the workaround for it could deadlock the system.
> > Add a warning during boot informing the user
Hi Bertrand,
On 26/10/2020 16:21, Bertrand Marquis wrote:
When a Cortex A57 processor is affected by CPU errata 832075, a guest
not implementing the workaround for it could deadlock the system.
Add a warning during boot informing the user that only trusted guests
should be executed on the system
Hi,
On 28/10/2020 08:43, Bertrand Marquis wrote:
On 27 Oct 2020, at 22:44, Stefano Stabellini wrote:
On Mon, 26 Oct 2020, Bertrand Marquis wrote:
When a Cortex A57 processor is affected by CPU errata 832075, a guest
not implementing the workaround for it could deadlock the system.
Add a wa
Hi George,
> On 28 Oct 2020, at 09:43, George Dunlap wrote:
>
>
>
>> On Oct 28, 2020, at 8:43 AM, Bertrand Marquis
>> wrote:
>>
>>
>>
>>> On 27 Oct 2020, at 22:44, Stefano Stabellini wrote:
>>>
>>> On Mon, 26 Oct 2020, Bertrand Marquis wrote:
When a Cortex A57 processor is affected
> On Oct 28, 2020, at 8:43 AM, Bertrand Marquis
> wrote:
>
>
>
>> On 27 Oct 2020, at 22:44, Stefano Stabellini wrote:
>>
>> On Mon, 26 Oct 2020, Bertrand Marquis wrote:
>>> When a Cortex A57 processor is affected by CPU errata 832075, a guest
>>> not implementing the workaround for it coul
> On 27 Oct 2020, at 22:44, Stefano Stabellini wrote:
>
> On Mon, 26 Oct 2020, Bertrand Marquis wrote:
>> When a Cortex A57 processor is affected by CPU errata 832075, a guest
>> not implementing the workaround for it could deadlock the system.
>> Add a warning during boot informing the user t
On Mon, 26 Oct 2020, Bertrand Marquis wrote:
> When a Cortex A57 processor is affected by CPU errata 832075, a guest
> not implementing the workaround for it could deadlock the system.
> Add a warning during boot informing the user that only trusted guests
> should be executed on the system.
> An e
When a Cortex A57 processor is affected by CPU errata 832075, a guest
not implementing the workaround for it could deadlock the system.
Add a warning during boot informing the user that only trusted guests
should be executed on the system.
An equivalent warning is already given to the user by KVM o
11 matches
Mail list logo