From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: State of KVM guest debugging support on Power Date: Thu, 03 Nov 2011 20:14:42 +0100 Message-ID: <4EB2E822.3080702@web.de> References: <4EB000A7.3000501@web.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig32F4CD41749D242B6BD95D98" Cc: qemu-devel , Alexander Graf , kvm-ppc , kvm To: Stuart Yoder Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig32F4CD41749D242B6BD95D98 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2011-11-03 19:59, Stuart Yoder wrote: > On Tue, Nov 1, 2011 at 9:22 AM, Jan Kiszka wrote: >> Hi there, >> >> I'm generating some slides on guest debugging via kvm. What's the >> current state for Book-E and Book-S? Works out of box, mostly usable, = or >> to be implemented? Is anyone using it? >=20 > Are you talking about guest debug using the QEMU stub or using > the virtual CPU's debug registers and interrupts? For Freescale > Book E we have both approaches working, and patches to be sent upstream= > soon. It's good to see both features coming into mainline. I'll talk about the former, ie. debugging without guest help/awareness (virtual hardware debugger). Is gdb well prepared for it (all registers available, real-mode support, etc.)? Thanks, Jan --------------enig32F4CD41749D242B6BD95D98 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk6y6CMACgkQitSsb3rl5xT6sgCeLfBjQ3hAajkHRZZpt9Guk63R oqYAoIitOBMntC4lyEG54JBTAi5903w1 =vJxU -----END PGP SIGNATURE----- --------------enig32F4CD41749D242B6BD95D98--