From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39906) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbED1-00032V-KU for qemu-devel@nongnu.org; Mon, 06 Oct 2014 15:44:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XbECs-0007TA-J1 for qemu-devel@nongnu.org; Mon, 06 Oct 2014 15:44:39 -0400 Received: from e06smtp12.uk.ibm.com ([195.75.94.108]:58777) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbECs-0007St-9o for qemu-devel@nongnu.org; Mon, 06 Oct 2014 15:44:30 -0400 Received: from /spool/local by e06smtp12.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 6 Oct 2014 20:44:28 +0100 Received: from b06cxnps3074.portsmouth.uk.ibm.com (d06relay09.portsmouth.uk.ibm.com [9.149.109.194]) by d06dlp03.portsmouth.uk.ibm.com (Postfix) with ESMTP id 563641B08023 for ; Mon, 6 Oct 2014 20:45:41 +0100 (BST) Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com [9.149.37.212]) by b06cxnps3074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id s96JiQv957147586 for ; Mon, 6 Oct 2014 19:44:26 GMT Received: from d06av01.portsmouth.uk.ibm.com (localhost [127.0.0.1]) by d06av01.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s96JiP5s002249 for ; Mon, 6 Oct 2014 13:44:26 -0600 Date: Mon, 6 Oct 2014 21:44:22 +0200 From: David Hildenbrand Message-ID: <20141006214422.5267a089@thinkpad-w530> In-Reply-To: References: <1412090627-18709-1-git-send-email-jfrei@linux.vnet.ibm.com> <1412090627-18709-2-git-send-email-jfrei@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] gdb: provide the name of the architecture in the target.xml List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Alexander Graf , QEMU Developers , Christian Borntraeger , Jens Freimann , "Vassili Karpov (malc)" , Cornelia Huck , Edgar Iglesias , Richard Henderson > On 30 September 2014 16:23, Jens Freimann wrote: > > From: David Hildenbrand > > > > This patch provides the name of the architecture in the target.xml if available. > > > > This allows the remote gdb to detect the target architecture on its own - so > > there is no need to specify it manually (e.g. if gdb is started without a > > binary) using "set arch *arch_name*". > > > > The name of the architecture has been added to all archs that provide a > > target.xml (by supplying a gdb_core_xml_file) and have a unique architecture > > name in gdb's feature xml files. > > gdb seems to support more than one powerpc architecture > name. Do we need to report "powerpc:e500" for > our e500 cpu models, for instance? > > -- PMM > Hi Peter, good point. I was hoping for more feedback from the powerpc folks. My gdb multi-arch seems to support the following architectures: (gdb) set arch Requires an argument. Valid arguments are i386, i386:x86-64, i386:x64-32, i8086, i386:intel, i386:x86-64:intel, i386:x64-32:intel, i386:nacl, i386:x86-64:nacl, i386:x64-32:nacl, s390:64-bit, rs6000:6000, rs6000:rs1, rs6000:rsc, rs6000:rs2, powerpc:common64, powerpc:common, powerpc:603, powerpc:EC603e, powerpc:604, powerpc:403, powerpc:601, powerpc:620, powerpc:630, powerpc:a35, powerpc:rs64ii, powerpc:rs64iii, powerpc:7400, powerpc:e500, powerpc:e500mc, powerpc:e500mc64, powerpc:MPC8XX, powerpc:750, powerpc:titan, powerpc:vle, powerpc:e5500, powerpc:e6500, arm, armv2, armv2a, armv3, armv3m, armv4, armv4t, armv5, armv5t, armv5te, xscale, ep9312, iwmmxt, iwmmxt2, aarch64, aarch64:ilp32, auto. However I am not sure if there are duplicates / compatible ones among them. The available registers are all defined in the XML supplied by the gdbserver - so I am not sure if they are "part" of the more specific architecture names. Maybe it makes sense to leave powerpc and arm out of this patch. So I would just set s390:64-bit in the first shot (unless there are any experts saying that e.g. powerpc:common always works). At least for s390:64-bit I am very sure :) Of course, the mechanism to set the name should be flexible enough (if we find the existing one to be too strict). Thanks! David