From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36157) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UNfuU-0003bl-Db for qemu-devel@nongnu.org; Thu, 04 Apr 2013 04:52:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UNfuT-0003Gu-9L for qemu-devel@nongnu.org; Thu, 04 Apr 2013 04:52:42 -0400 Received: from cantor2.suse.de ([195.135.220.15]:56280 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UNfuT-0003Gl-3s for qemu-devel@nongnu.org; Thu, 04 Apr 2013 04:52:41 -0400 Message-ID: <515D3F55.7080205@suse.de> Date: Thu, 04 Apr 2013 10:52:37 +0200 From: =?ISO-8859-1?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <1364146041-27041-1-git-send-email-rabin@rab.in> <515039E6.1010004@suse.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCHv2 0/6] ARM dump-guest-memory support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Rabin Vincent , Jens Freimann Cc: Peter Maydell , qemu-devel@nongnu.org, Alexander Graf Am 29.03.2013 09:36, schrieb Rabin Vincent: > 2013/3/25 Andreas F=E4rber >> This still does not address the architectural issue that I brought up. >=20 > I guess you mean the CPUArchState stuff? AFAICS Wen Congyang (the > author of the dump code) had some answers/questions for you: >=20 > http://lists.gnu.org/archive/html/qemu-devel/2012-07/msg00382.html > http://lists.gnu.org/archive/html/qemu-devel/2012-07/msg00384.html Yes, that is what I'm referring to, and I don't see answers to my questions... If as I understand we are talking about a property that depends solely on the target CPU then it should be implemented on CPUClass level (which is the one above ARMCPU, S390CPU etc.) and not require changes to configure at all. CPUArchState is by contrast a per-target type. qom/cpu.c would implement the dummy versions and in your case target-arm/cpu.c (in Jens' case target-s390x/cpu.c) should override that behavior by setting cc->whatever to a static function that actually implements the functionality. I would supply you with a patch for that myself, but I am rather busy with downstream ATM and Igor is poking me for x86 CPU review, so if either of you or Wen Congyang could fix that design flaw before making it worse I would appreciate that! Regards, Andreas --=20 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe= rg