From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:35721) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RIdB4-0001dF-UQ for qemu-devel@nongnu.org; Tue, 25 Oct 2011 05:20:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RIdAy-0007eq-Nk for qemu-devel@nongnu.org; Tue, 25 Oct 2011 05:20:10 -0400 Received: from thoth.sbs.de ([192.35.17.2]:33666) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RIdAy-0007do-Az for qemu-devel@nongnu.org; Tue, 25 Oct 2011 05:20:04 -0400 Message-ID: <4EA67F33.5070806@siemens.com> Date: Tue, 25 Oct 2011 11:19:47 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <54c9dc1d-3104-4f42-9a20-d7f4da516bdc@zmail05.collab.prod.int.phx2.redhat.com> <4EA58488.50306@redhat.com> <4EA66E1E.90502@cn.fujitsu.com> <4EA67216.3050309@redhat.com> <4EA674EF.9010308@redhat.com> <4EA678B6.6090804@redhat.com> <4EA679CC.2080301@redhat.com> In-Reply-To: <4EA679CC.2080301@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Question] dump memory when host pci device is used by guest List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Tom Tromey , "Richard W.M. Jones" , qemu-devel , Luiz Capitulino , Anthony Eden , Dave Anderson , Avi Kivity , KAMEZAWA Hiroyuki On 2011-10-25 10:56, Paolo Bonzini wrote: > On 10/25/2011 10:52 AM, Avi Kivity wrote: >>>> Crash uses a heuristic based on the IDT base to identify the base from >>>> migrate-to-file output. It also needs CR3 in order to read from >>>> virtual address. >> Does elf not store cr3? Perhaps a note with the contents of the >> privileged cpu registers is needed. > > Yes. It would be nice if this note could be somewhat standardized. > > Jan, is there a code sample somewhere for the x86-gdb summer of code > project? I'm not aware of a public repos, CC'ing Anthony and Tom. We definitely need all x86 system registers handled by gdb long-term, already for live debugging and for segmented guests / proper real mode support. But if crash depends on those values already today, we should head for its current format in a first step, then enhance gdb, and finally check how to integrate that information best with vanilla gdb. For me it is important that we agree on consolidating over (enhanced) gdb on the long run, both /wrt features and supported core formats. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux