diff for duplicates of <1428534695.4682.18.camel@neuling.org> diff --git a/a/1.txt b/N1/1.txt index a61ec60..8e8ee08 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ On Wed, 2015-04-08 at 19:50 +0200, Ulrich Weigand wrote: > Anshuman Khandual <khandual@linux.vnet.ibm.com> wrote on 23.03.2015 > 11:34:30: ->=20 +> > > > With that in mind, do we have a way to set the top 32bits of the MSR > > > (which contain the TM bits) when ptracing 32 bit processes? I can't > > > find anything like that in this patch set. @@ -12,21 +12,21 @@ On Wed, 2015-04-08 at 19:50 +0200, Ulrich Weigand wrote: > > the upper 32 bits of MSR as part of one of the ELF core notes we are > > adding in the patch series or we can create one more separate ELF core > > note for that purpose. Let me know your opinion on this. ->=20 +> > I'm not sure I understand this. I thought we had the following: ->=20 +> > - If the process calling ptrace is itself 64-bit (which is how GDB is > built on all current Linux distributions), then PTRACE_GETREGS etc. > will *always* operate on 64-bit register sets, even if the target > process is 32-bit. ->=20 +> > - If the process calling ptrace is 32-bit, then PTRACE_GETREGS will > operate on 32-bit register sets. However, there is a separate > PTRACE_GETREGS64 / PTRACE_SETREGS64 call that will also provide > the opportunity to operate on the full 64-bit register set. Both > apply independently of whether the target process is 32-bit or > 64-bit. ->=20 +> > Is this not correct? I think you're correct. We should be right. I'd forgotten about the diff --git a/a/content_digest b/N1/content_digest index d8f9569..7df4d05 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -18,31 +18,31 @@ "Subject\0Re: [V6,1/9] elf: Add new powerpc specifc core note sections\0" "Date\0Thu, 09 Apr 2015 09:11:35 +1000\0" "To\0Ulrich Weigand <Ulrich.Weigand@de.ibm.com>\0" - "Cc\0shuahkh@osg.samsung.com" - james.hogan@imgtec.com + "Cc\0Anshuman Khandual <khandual@linux.vnet.ibm.com>" + akpm@linux-foundation.org avagin@openvz.org - Paul.Clothier@imgtec.com - peterz@infradead.org - palves@redhat.com - linux-kernel@vger.kernel.org - Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com> + davej@redhat.com + davem@davemloft.net dhowells@redhat.com - linuxppc-dev@ozlabs.org + Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com> + james.hogan@imgtec.com kirjanov@gmail.com - tglx@linutronix.de + linux-kernel@vger.kernel.org + linuxppc-dev@ozlabs.org oleg@redhat.com - davej@redhat.com - akpm@linux-foundation.org - sukadev@linux.vnet.ibm.com - davem@davemloft.net + palves@redhat.com + Paul.Clothier@imgtec.com + peterz@infradead.org sam.bobroff@au1.ibm.com - " Anshuman Khandual <khandual@linux.vnet.ibm.com>\0" + shuahkh@osg.samsung.com + sukadev@linux.vnet.ibm.com + " tglx@linutronix.de\0" "\00:1\0" "b\0" "On Wed, 2015-04-08 at 19:50 +0200, Ulrich Weigand wrote:\n" "> Anshuman Khandual <khandual@linux.vnet.ibm.com> wrote on 23.03.2015\n" "> 11:34:30:\n" - ">=20\n" + "> \n" "> > > With that in mind, do we have a way to set the top 32bits of the MSR\n" "> > > (which contain the TM bits) when ptracing 32 bit processes? I can't\n" "> > > find anything like that in this patch set.\n" @@ -53,21 +53,21 @@ "> > the upper 32 bits of MSR as part of one of the ELF core notes we are\n" "> > adding in the patch series or we can create one more separate ELF core\n" "> > note for that purpose. Let me know your opinion on this.\n" - ">=20\n" + "> \n" "> I'm not sure I understand this. I thought we had the following:\n" - ">=20\n" + "> \n" "> - If the process calling ptrace is itself 64-bit (which is how GDB is\n" "> built on all current Linux distributions), then PTRACE_GETREGS etc.\n" "> will *always* operate on 64-bit register sets, even if the target\n" "> process is 32-bit.\n" - ">=20\n" + "> \n" "> - If the process calling ptrace is 32-bit, then PTRACE_GETREGS will\n" "> operate on 32-bit register sets. However, there is a separate\n" "> PTRACE_GETREGS64 / PTRACE_SETREGS64 call that will also provide\n" "> the opportunity to operate on the full 64-bit register set. Both\n" "> apply independently of whether the target process is 32-bit or\n" "> 64-bit.\n" - ">=20\n" + "> \n" "> Is this not correct?\n" "\n" "I think you're correct. We should be right. I'd forgotten about the\n" @@ -75,4 +75,4 @@ "\n" Mikey -f61c59bbb6b33dadd95d958923de02c4ca9a1de7307793d16ae35ad75d44b2b4 +2de43ae4a3a13cbc240428a8d6196a22aea6052672339c22c29cafe5653d6e79
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.