On Tue, Feb 26, 2019 at 03:59:40PM +, Julien Grall wrote:
> Hi Dave,
>
> On 26/02/2019 15:58, Dave Martin wrote:
> >On Tue, Feb 26, 2019 at 03:49:00PM +, Julien Grall wrote:
> >>Hi Dave,
> >>
> >>On 26/02/2019 12:07, Dave Martin wrote:
[...]
> >>>Does the code look reasonable to you? Th
Hi Dave,
On 26/02/2019 15:58, Dave Martin wrote:
On Tue, Feb 26, 2019 at 03:49:00PM +, Julien Grall wrote:
Hi Dave,
On 26/02/2019 12:07, Dave Martin wrote:
On Fri, Feb 22, 2019 at 03:26:51PM +, Julien Grall wrote:
Hi Dave,
On 18/02/2019 19:52, Dave Martin wrote:
The current FPSIMD/
On Tue, Feb 26, 2019 at 03:49:00PM +, Julien Grall wrote:
> Hi Dave,
>
> On 26/02/2019 12:07, Dave Martin wrote:
> >On Fri, Feb 22, 2019 at 03:26:51PM +, Julien Grall wrote:
> >>Hi Dave,
> >>
> >>On 18/02/2019 19:52, Dave Martin wrote:
> >>>The current FPSIMD/SVE context handling support f
Hi Dave,
On 26/02/2019 12:07, Dave Martin wrote:
On Fri, Feb 22, 2019 at 03:26:51PM +, Julien Grall wrote:
Hi Dave,
On 18/02/2019 19:52, Dave Martin wrote:
The current FPSIMD/SVE context handling support for non-task (i.e.,
KVM vcpu) contexts does not take SVE into account. This means th
On Fri, Feb 22, 2019 at 03:26:51PM +, Julien Grall wrote:
> Hi Dave,
>
> On 18/02/2019 19:52, Dave Martin wrote:
> >The current FPSIMD/SVE context handling support for non-task (i.e.,
> >KVM vcpu) contexts does not take SVE into account. This means that
>
> NIT: Double-space before "This".
Hi Dave,
On 18/02/2019 19:52, Dave Martin wrote:
The current FPSIMD/SVE context handling support for non-task (i.e.,
KVM vcpu) contexts does not take SVE into account. This means that
NIT: Double-space before "This".
only task contexts can safely use SVE at present.
In preparation for enab
The current FPSIMD/SVE context handling support for non-task (i.e.,
KVM vcpu) contexts does not take SVE into account. This means that
only task contexts can safely use SVE at present.
In preparation for enabling KVM guests to use SVE, it is necessary
to keep track of SVE state for non-task conte
