Ram Pai <linux...@us.ibm.com> writes: > The value of the AMR register at the time of exception > is made available in gp_regs[PT_AMR] of the siginfo. > > The value of the pkey, whose protection got violated, > is made available in si_pkey field of the siginfo structure.
Should the IAMR also be made available? Also, should the AMR and IAMR be accesible to userspace (e.g., to GDB) via ptrace and the core file? > --- a/arch/powerpc/kernel/signal_32.c > +++ b/arch/powerpc/kernel/signal_32.c > @@ -500,6 +500,11 @@ static int save_user_regs(struct pt_regs *regs, struct > mcontext __user *frame, > (unsigned long) &frame->tramp[2]); > } > > +#ifdef CONFIG_PPC64_MEMORY_PROTECTION_KEYS > + if (__put_user(get_paca()->paca_amr, &frame->mc_gregs[PT_AMR])) > + return 1; > +#endif /* CONFIG_PPC64_MEMORY_PROTECTION_KEYS */ > + > return 0; > } frame->mc_gregs[PT_AMR] has 32 bits, but paca_amr has 64 bits. Does this work as intended? > diff --git a/arch/powerpc/kernel/signal_64.c b/arch/powerpc/kernel/signal_64.c > index c83c115..86a4262 100644 > --- a/arch/powerpc/kernel/signal_64.c > +++ b/arch/powerpc/kernel/signal_64.c > @@ -174,6 +174,10 @@ static long setup_sigcontext(struct sigcontext __user > *sc, > if (set != NULL) > err |= __put_user(set->sig[0], &sc->oldmask); > > +#ifdef CONFIG_PPC64_MEMORY_PROTECTION_KEYS > + err |= __put_user(get_paca()->paca_amr, &sc->gp_regs[PT_AMR]); > +#endif /* CONFIG_PPC64_MEMORY_PROTECTION_KEYS */ > + > return err; > } Isn't a corresponding change needed in restore_sigcontext? And in the corresponding TM versions setup_tm_sigcontexts and restore_tm_sigcontexts? Ditto for the equivalent functions in signal_32.c. -- Thiago Jung Bauermann IBM Linux Technology Center
