From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754881AbbDIMuk (ORCPT ); Thu, 9 Apr 2015 08:50:40 -0400 Received: from e28smtp03.in.ibm.com ([122.248.162.3]:55728 "EHLO e28smtp03.in.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752558AbbDIMui (ORCPT ); Thu, 9 Apr 2015 08:50:38 -0400 Message-ID: <55267595.9030202@linux.vnet.ibm.com> Date: Thu, 09 Apr 2015 18:20:29 +0530 From: Anshuman Khandual User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Michael Neuling , Ulrich Weigand CC: shuahkh@osg.samsung.com, james.hogan@imgtec.com, avagin@openvz.org, Paul.Clothier@imgtec.com, peterz@infradead.org, palves@redhat.com, linux-kernel@vger.kernel.org, Edjunior Barbosa Machado , dhowells@redhat.com, linuxppc-dev@ozlabs.org, kirjanov@gmail.com, tglx@linutronix.de, oleg@redhat.com, davej@redhat.com, akpm@linux-foundation.org, sukadev@linux.vnet.ibm.com, davem@davemloft.net, sam.bobroff@au1.ibm.com Subject: Re: [V6,1/9] elf: Add new powerpc specifc core note sections References: <20141203052204.9DA8F1400DD@ozlabs.org> <547EB253.5050307@linux.vnet.ibm.com> <548578A8.5020901@linux.vnet.ibm.com> <54947C64.4030206@linux.vnet.ibm.com> <54A50094.5070902@linux.vnet.ibm.com> <1421883597.30744.3.camel@neuling.org> <1421963049.30744.23.camel@neuling.org> <1422419289.9646.20.camel@neuling.org> <1424667110.16027.6.camel@neuling.org> <1426718702.4866.2.camel@neuling.org> <1426719027.4866.4.camel@neuling.org> <550FEC36.8080803@linux.vnet.ibm.com> <1428534695.4682.18.camel@neuling.org> In-Reply-To: <1428534695.4682.18.camel@neuling.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 15040912-0009-0000-0000-000004C6818F Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/09/2015 04:41 AM, Michael Neuling wrote: > On Wed, 2015-04-08 at 19:50 +0200, Ulrich Weigand wrote: >> Anshuman Khandual wrote on 23.03.2015 >> 11:34:30: >> >>>> 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. >>> >>> No, we dont have that yet. When ptracing in 32-bit mode the MSR value >>> which can be viewed or set from the user space through PTRACE_GETREGS >>> PTRACE_SETREGS call is it's lower 32 bits only. Either we can club >>> 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. >> >> I'm not sure I understand this. I thought we had the following: >> >> - 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. >> >> - 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. >> >> Is this not correct? > > I think you're correct. We should be right. I'd forgotten about the > GET/SETREGS64 interfaces. In that case, is the patch series complete and okay ? Is there any thing else we need to verify other than waiting for the GDB test results which Edjunior has been working on. But I am not aware of the status on the GDB test development front. Edjunior, Do you have any updates ? Regards Anshuman From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [IPv6:2401:3900:2:1::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id C92511A0145 for ; Thu, 9 Apr 2015 22:50:43 +1000 (AEST) Received: from e28smtp02.in.ibm.com (e28smtp02.in.ibm.com [122.248.162.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id EC6F21402E0 for ; Thu, 9 Apr 2015 22:50:42 +1000 (AEST) Received: from /spool/local by e28smtp02.in.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 9 Apr 2015 18:20:40 +0530 Received: from d28relay01.in.ibm.com (d28relay01.in.ibm.com [9.184.220.58]) by d28dlp02.in.ibm.com (Postfix) with ESMTP id 2E1733940062 for ; Thu, 9 Apr 2015 18:20:34 +0530 (IST) Received: from d28av01.in.ibm.com (d28av01.in.ibm.com [9.184.220.63]) by d28relay01.in.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id t39CoXOw9306116 for ; Thu, 9 Apr 2015 18:20:33 +0530 Received: from d28av01.in.ibm.com (localhost [127.0.0.1]) by d28av01.in.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id t39CoUrm003411 for ; Thu, 9 Apr 2015 18:20:33 +0530 Message-ID: <55267595.9030202@linux.vnet.ibm.com> Date: Thu, 09 Apr 2015 18:20:29 +0530 From: Anshuman Khandual MIME-Version: 1.0 To: Michael Neuling , Ulrich Weigand Subject: Re: [V6,1/9] elf: Add new powerpc specifc core note sections References: <20141203052204.9DA8F1400DD@ozlabs.org> <547EB253.5050307@linux.vnet.ibm.com> <548578A8.5020901@linux.vnet.ibm.com> <54947C64.4030206@linux.vnet.ibm.com> <54A50094.5070902@linux.vnet.ibm.com> <1421883597.30744.3.camel@neuling.org> <1421963049.30744.23.camel@neuling.org> <1422419289.9646.20.camel@neuling.org> <1424667110.16027.6.camel@neuling.org> <1426718702.4866.2.camel@neuling.org> <1426719027.4866.4.camel@neuling.org> <550FEC36.8080803@linux.vnet.ibm.com> <1428534695.4682.18.camel@neuling.org> In-Reply-To: <1428534695.4682.18.camel@neuling.org> Content-Type: text/plain; charset=UTF-8 Cc: james.hogan@imgtec.com, avagin@openvz.org, Paul.Clothier@imgtec.com, davem@davemloft.net, peterz@infradead.org, palves@redhat.com, shuahkh@osg.samsung.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, dhowells@redhat.com, linuxppc-dev@ozlabs.org, kirjanov@gmail.com, oleg@redhat.com, davej@redhat.com, tglx@linutronix.de, sukadev@linux.vnet.ibm.com, Edjunior Barbosa Machado , sam.bobroff@au1.ibm.com List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 04/09/2015 04:41 AM, Michael Neuling wrote: > On Wed, 2015-04-08 at 19:50 +0200, Ulrich Weigand wrote: >> Anshuman Khandual wrote on 23.03.2015 >> 11:34:30: >> >>>> 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. >>> >>> No, we dont have that yet. When ptracing in 32-bit mode the MSR value >>> which can be viewed or set from the user space through PTRACE_GETREGS >>> PTRACE_SETREGS call is it's lower 32 bits only. Either we can club >>> 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. >> >> I'm not sure I understand this. I thought we had the following: >> >> - 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. >> >> - 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. >> >> Is this not correct? > > I think you're correct. We should be right. I'd forgotten about the > GET/SETREGS64 interfaces. In that case, is the patch series complete and okay ? Is there any thing else we need to verify other than waiting for the GDB test results which Edjunior has been working on. But I am not aware of the status on the GDB test development front. Edjunior, Do you have any updates ? Regards Anshuman