Re: [RFC V1 0/6] Generic Entry/Exit support for ppc64

2025-05-05 Thread Ankur Arora
Mukesh Kumar Chaurasiya writes: > This is a syscall only implementation of generic entry/exit framework > for framework for ppc. IRQ handling is not done in this RFC. > > This will break the ppc32 build as of now which will be fixed along with > IRQ handling. > > Below are the performance bench

Re: [RFC V1 0/6] Generic Entry/Exit support for ppc64

2025-05-05 Thread Ankur Arora
Ankur Arora writes: > Mukesh Kumar Chaurasiya writes: > >> This is a syscall only implementation of generic entry/exit framework >> for framework for ppc. IRQ handling is not done in this RFC. >> >> This will break the ppc32 build as of now which will be fi

Re: [PATCH v2 2/2] powerpc: Large user copy aware of full:rt:lazy preemption

2024-11-19 Thread Ankur Arora
Shrikanth Hegde writes: > Large user copy_to/from (more than 16 bytes) uses vmx instructions to > speed things up. Once the copy is done, it makes sense to try schedule > as soon as possible for preemptible kernels. So do this for > preempt=full/lazy and rt kernel. Note that this check will al

Re: [PATCH] powerpc: Add preempt lazy support

2024-11-15 Thread Ankur Arora
Shrikanth Hegde writes: > On 11/9/24 22:24, Shrikanth Hegde wrote: >> >> On 11/9/24 00:36, Ankur Arora wrote: >>> >>> Shrikanth Hegde writes: >>> >>>> Define preempt lazy bit for Powerpc. Use bit 9 which is free and within >>>&g

Re: [PATCH] powerpc: Add preempt lazy support

2024-11-08 Thread Ankur Arora
Shrikanth Hegde writes: > Define preempt lazy bit for Powerpc. Use bit 9 which is free and within > 16 bit range of NEED_RESCHED, so compiler can issue single andi. > > Since Powerpc doesn't use the generic entry/exit, add lazy check at exit > to user. CONFIG_PREEMPTION is defined for lazy/full