On Wed, Apr 10, 2024 at 08:27:07AM +0100, Marc Zyngier wrote:
> Mark Brown wrote:
> > On Tue, Apr 02, 2024 at 03:53:33PM +0100, Marc Zyngier wrote:
> > > Mark Brown wrote:
> > > Because it means this series assumes a different data life cycle, and
> > > the review effort spent on it will be
On Tue, 02 Apr 2024 17:20:36 +0100,
Mark Brown wrote:
>
> On Tue, Apr 02, 2024 at 03:53:33PM +0100, Marc Zyngier wrote:
> > Mark Brown wrote:
>
> > > Sure, those patches are still in flight though. It does seem reasonable
> > > to target the current code.
>
> > Sure, if your intent is for
On Tue, Apr 02, 2024 at 03:53:33PM +0100, Marc Zyngier wrote:
> Mark Brown wrote:
> > Sure, those patches are still in flight though. It does seem reasonable
> > to target the current code.
> Sure, if your intent is for this code not to be merged.
> Because it means this series assumes a
On Tue, 02 Apr 2024 15:34:27 +0100,
Mark Brown wrote:
>
> [1 ]
> On Sun, Mar 31, 2024 at 11:00:41AM +0100, Marc Zyngier wrote:
> > Mark Brown wrote:
>
> > > As part of the lazy FPSIMD state transitioning done by the hypervisor we
> > > currently share the userpsace FPSIMD state in
On Sun, Mar 31, 2024 at 11:00:41AM +0100, Marc Zyngier wrote:
> Mark Brown wrote:
> > As part of the lazy FPSIMD state transitioning done by the hypervisor we
> > currently share the userpsace FPSIMD state in thread->uw.fpsimd_state with
> > the host. Since this struct is non-extensible
On Fri, 29 Mar 2024 00:13:42 +,
Mark Brown wrote:
>
> As part of the lazy FPSIMD state transitioning done by the hypervisor we
> currently share the userpsace FPSIMD state in thread->uw.fpsimd_state with
> the host. Since this struct is non-extensible userspace ABI we have to keep
Using the
As part of the lazy FPSIMD state transitioning done by the hypervisor we
currently share the userpsace FPSIMD state in thread->uw.fpsimd_state with
the host. Since this struct is non-extensible userspace ABI we have to keep
the definition as is but the addition of FPMR in the 2023 dpISA means that
