[PATCH v4 02/22] powerpc/pkeys: Check vma before returning key fault error to the user

2020-05-05 Thread Aneesh Kumar K.V
If multiple threads in userspace keep changing the protection keys mapping a range, there can be a scenario where kernel takes a key fault but the pkey value found in the siginfo struct is a permissive one. This can confuse the userspace as shown in the below test case. /* use this to control

[PATCH v4 01/22] powerpc/pkeys: Avoid using lockless page table walk

2020-05-05 Thread Aneesh Kumar K.V
Fetch pkey from vma instead of linux page table. Also document the fact that in some cases the pkey returned in siginfo won't be the same as the one we took keyfault on. Even with linux page table walk, we can end up in a similar scenario. Cc: Ram Pai Signed-off-by: Aneesh Kumar K.V ---

[PATCH v4 00/22] Avoid IPI while updating page table entries.

2020-05-05 Thread Aneesh Kumar K.V
Problem Summary: Slow termination of KVM guest with large guest RAM config due to a large number of IPIs that were caused by clearing level 1 PTE entries (THP) entries. This is shown in the stack trace below. - qemu-system-ppc [kernel.vmlinux][k] smp_call_function_many -

Re: [PATCH v7 26/28] powerpc: Support prefixed instructions in alignment handler

2020-05-05 Thread Alistair Popple
Reviewed-by: Alistair Popple On Friday, 1 May 2020 1:42:18 PM AEST Jordan Niethe wrote: > If a prefixed instruction results in an alignment exception, the > SRR1_PREFIXED bit is set. The handler attempts to emulate the > responsible instruction and then increment the NIP past it. Use >

Re: [PATCH v7 25/28] powerpc: Test prefixed instructions in feature fixups

2020-05-05 Thread Alistair Popple
Hmm, I was hoping to add a tested by but I'm seeing the following failure in Mambo: [1.475459] feature-fixups: test failed at line 730 Based on the name of the test it looks like you probably made a copy/paste error in ftr_fixup_prefix2_expected. I suspect you probably meant to use the

Re: [PATCH v7 04/28] powerpc/xmon: Use bitwise calculations in_breakpoint_table()

2020-05-05 Thread Michael Ellerman
Jordan Niethe writes: > A modulo operation is used for calculating the current offset from a > breakpoint within the breakpoint table. As instruction lengths are > always a power of 2, this can be replaced with a bitwise 'and'. The > current check for word alignment can be replaced with checking

Re: [PATCH v7 5/5] powerpc/hv-24x7: Update post_mobility_fixup() to handle migration

2020-05-05 Thread Michael Ellerman
kajoljain writes: > On 4/29/20 5:07 PM, Michael Ellerman wrote: >> Kajol Jain writes: >>> Function 'read_sys_info_pseries()' is added to get system parameter >>> values like number of sockets and chips per socket. >>> and it gets these details via rtas_call with token >>>

Re: [PATCH v7 5/5] powerpc/hv-24x7: Update post_mobility_fixup() to handle migration

2020-05-05 Thread kajoljain
On 4/29/20 5:07 PM, Michael Ellerman wrote: > Kajol Jain writes: >> Function 'read_sys_info_pseries()' is added to get system parameter >> values like number of sockets and chips per socket. >> and it gets these details via rtas_call with token >> "PROCESSOR_MODULE_INFO". >> >> Incase lpar

Re: [PATCH v2 2/2] clk: qoriq: add cpufreq platform device

2020-05-05 Thread Stephen Boyd
Quoting Mian Yousaf Kaukab (2020-04-21 01:30:00) > Add a platform device for qoirq-cpufreq driver for the compatible > clockgen blocks. > > Reviewed-by: Yuantian Tang > Acked-by: Viresh Kumar > Signed-off-by: Mian Yousaf Kaukab > --- Acked-by: Stephen Boyd

Re: [PATCH v7 24/28] powerpc: Test prefixed code patching

2020-05-05 Thread Alistair Popple
Reviewed-by: Alistair Popple On Friday, 1 May 2020 1:42:16 PM AEST Jordan Niethe wrote: > Expand the code-patching self-tests to includes tests for patching > prefixed instructions. > > Signed-off-by: Jordan Niethe > --- > v6: New to series > --- > arch/powerpc/lib/Makefile | 2

Re: [PATCH v7 23/28] powerpc: Add prefixed instructions to instruction data type

2020-05-05 Thread Alistair Popple
When reviewing earlier patches in this series I assumed the data type would eventually change size (on PPC64 at least) so I was looking for any possible side effects this may cause, but I didn't notice any so I think this should be ok: Reviewed-by: Alistair Popple However I haven't dug

<    1   2