On Tue, Oct 15, 2019 at 12:30:15PM +0200, Ard Biesheuvel wrote:
> On Tue, 15 Oct 2019 at 12:25, Dave Martin wrote:
> >
> > On Mon, Oct 14, 2019 at 06:57:30PM +0200, Ard Biesheuvel wrote:
[...]
> > > All in-kernel NEON code checks whether the NEON is usable, so I'd
> > > expect that check to retu
On Tue, 15 Oct 2019 at 15:03, Suzuki K Poulose wrote:
>
>
>
> On 15/10/2019 11:30, Ard Biesheuvel wrote:
> > On Tue, 15 Oct 2019 at 12:25, Dave Martin wrote:
> >>
> >> On Mon, Oct 14, 2019 at 06:57:30PM +0200, Ard Biesheuvel wrote:
> >>> On Mon, 14 Oct 2019 at 17:50, Dave P Martin wrote:
>
On 15/10/2019 11:30, Ard Biesheuvel wrote:
On Tue, 15 Oct 2019 at 12:25, Dave Martin wrote:
On Mon, Oct 14, 2019 at 06:57:30PM +0200, Ard Biesheuvel wrote:
On Mon, 14 Oct 2019 at 17:50, Dave P Martin wrote:
On Mon, Oct 14, 2019 at 04:45:40PM +0100, Suzuki K Poulose wrote:
On 14/10/20
On Tue, 15 Oct 2019 at 12:25, Dave Martin wrote:
>
> On Mon, Oct 14, 2019 at 06:57:30PM +0200, Ard Biesheuvel wrote:
> > On Mon, 14 Oct 2019 at 17:50, Dave P Martin wrote:
> > >
> > > On Mon, Oct 14, 2019 at 04:45:40PM +0100, Suzuki K Poulose wrote:
> > > >
> > > >
> > > > On 14/10/2019 15:52, Da
On Mon, Oct 14, 2019 at 06:57:30PM +0200, Ard Biesheuvel wrote:
> On Mon, 14 Oct 2019 at 17:50, Dave P Martin wrote:
> >
> > On Mon, Oct 14, 2019 at 04:45:40PM +0100, Suzuki K Poulose wrote:
> > >
> > >
> > > On 14/10/2019 15:52, Dave Martin wrote:
> > > > On Fri, Oct 11, 2019 at 06:28:43PM +0100,
On Tue, 15 Oct 2019 at 11:44, Suzuki K Poulose wrote:
>
>
>
> On 14/10/2019 17:57, Ard Biesheuvel wrote:
> > On Mon, 14 Oct 2019 at 17:50, Dave P Martin wrote:
> >>
> >> On Mon, Oct 14, 2019 at 04:45:40PM +0100, Suzuki K Poulose wrote:
> >>>
> >>>
> >>> On 14/10/2019 15:52, Dave Martin wrote:
> >
On 14/10/2019 17:57, Ard Biesheuvel wrote:
On Mon, 14 Oct 2019 at 17:50, Dave P Martin wrote:
On Mon, Oct 14, 2019 at 04:45:40PM +0100, Suzuki K Poulose wrote:
On 14/10/2019 15:52, Dave Martin wrote:
On Fri, Oct 11, 2019 at 06:28:43PM +0100, Suzuki K Poulose wrote:
On 11/10/2019 15:2
On Mon, 14 Oct 2019 at 17:50, Dave P Martin wrote:
>
> On Mon, Oct 14, 2019 at 04:45:40PM +0100, Suzuki K Poulose wrote:
> >
> >
> > On 14/10/2019 15:52, Dave Martin wrote:
> > > On Fri, Oct 11, 2019 at 06:28:43PM +0100, Suzuki K Poulose wrote:
> > >>
> > >>
> > >> On 11/10/2019 15:21, Dave Martin
On Mon, Oct 14, 2019 at 04:45:40PM +0100, Suzuki K Poulose wrote:
>
>
> On 14/10/2019 15:52, Dave Martin wrote:
> > On Fri, Oct 11, 2019 at 06:28:43PM +0100, Suzuki K Poulose wrote:
> >>
> >>
> >> On 11/10/2019 15:21, Dave Martin wrote:
> >>> On Fri, Oct 11, 2019 at 01:13:18PM +0100, Suzuki K Poulo
On 14/10/2019 15:52, Dave Martin wrote:
On Fri, Oct 11, 2019 at 06:28:43PM +0100, Suzuki K Poulose wrote:
On 11/10/2019 15:21, Dave Martin wrote:
On Fri, Oct 11, 2019 at 01:13:18PM +0100, Suzuki K Poulose wrote: > Hi Dave
On 11/10/2019 12:36, Dave Martin wrote:
On Thu, Oct 10, 2019 at 0
On Fri, Oct 11, 2019 at 06:28:43PM +0100, Suzuki K Poulose wrote:
>
>
> On 11/10/2019 15:21, Dave Martin wrote:
> >On Fri, Oct 11, 2019 at 01:13:18PM +0100, Suzuki K Poulose wrote: > Hi Dave
> >>
> >>On 11/10/2019 12:36, Dave Martin wrote:
> >>>On Thu, Oct 10, 2019 at 06:15:15PM +0100, Suzuki K P
On 11/10/2019 15:21, Dave Martin wrote:
On Fri, Oct 11, 2019 at 01:13:18PM +0100, Suzuki K Poulose wrote: > Hi Dave
On 11/10/2019 12:36, Dave Martin wrote:
On Thu, Oct 10, 2019 at 06:15:15PM +0100, Suzuki K Poulose wrote:
The NO_FPSIMD capability is defined with scope SYSTEM, which implies
On Fri, Oct 11, 2019 at 01:13:18PM +0100, Suzuki K Poulose wrote: > Hi Dave
>
> On 11/10/2019 12:36, Dave Martin wrote:
> >On Thu, Oct 10, 2019 at 06:15:15PM +0100, Suzuki K Poulose wrote:
> >>The NO_FPSIMD capability is defined with scope SYSTEM, which implies
> >>that the "absence" of FP/SIMD on
Hi Dave
On 11/10/2019 12:36, Dave Martin wrote:
On Thu, Oct 10, 2019 at 06:15:15PM +0100, Suzuki K Poulose wrote:
The NO_FPSIMD capability is defined with scope SYSTEM, which implies
that the "absence" of FP/SIMD on at least one CPU is detected only
after all the SMP CPUs are brought up. Howeve
On Thu, Oct 10, 2019 at 06:15:15PM +0100, Suzuki K Poulose wrote:
> The NO_FPSIMD capability is defined with scope SYSTEM, which implies
> that the "absence" of FP/SIMD on at least one CPU is detected only
> after all the SMP CPUs are brought up. However, we use the status
> of this capability for
The NO_FPSIMD capability is defined with scope SYSTEM, which implies
that the "absence" of FP/SIMD on at least one CPU is detected only
after all the SMP CPUs are brought up. However, we use the status
of this capability for every context switch. So, let us change
the scop to LOCAL_CPU to allow the
16 matches
Mail list logo