From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [kvm-devel] [RFC][PATCH 2/4] kvm: Arch-specifc KVM_EXIT_DEBUG payload Date: Thu, 22 May 2008 16:32:15 +0200 Message-ID: <483583EF.1010907@web.de> References: <482D9198.7040801@web.de> <482DAFF6.3050403@web.de> <48344820.60103@qumranet.com> <4835782F.60804@web.de> <48357C4D.9070400@qumranet.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA0C4022F1904DCAD3DF5521F" Cc: kvm-devel , Hollis Blanchard To: Avi Kivity Return-path: Received: from fmmailgate02.web.de ([217.72.192.227]:43244 "EHLO fmmailgate02.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751803AbYEVOcQ (ORCPT ); Thu, 22 May 2008 10:32:16 -0400 In-Reply-To: <48357C4D.9070400@qumranet.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA0C4022F1904DCAD3DF5521F Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Avi Kivity wrote: > Jan Kiszka wrote: >> >>> We need to handle branch tracing and last branch recording as well. = It >>> doesn't have to be in this patchset, though. >>> =20 >> >> IIRC, both features are fairly vendor specific. Do we have the same >> level of support on both AMD and Intel CPUs? Moreover, I doubt that th= e >> debug interface would be the right place for them. >> =20 >=20 > Branch tracing is common, and is very much related to debugging (it > modifies singlestep to trap only on branches, not on non-branching > insns). LBR is either common or very similar, and is also very > important for debugging. Well, might be useful. But then we would also have to teach this support to the gdb remote protocol and the gdb frontend, because neither of both seems to make use of it yet. And do other archs have it as well? If at all, I guess the way this is realized there varies a lot, and thus abstracting it is the real problem. However, we can keep it in mind for the time the basic feature set works perfectly. :) Jan --------------enigA0C4022F1904DCAD3DF5521F 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.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFINYPvniDOoMHTA+kRAvuXAJ9uM7OWt2vrWWzkD08nc4vg8dMV3gCfZcJv L8dGW7mc2IloynFWqD8TWLk= =mZFx -----END PGP SIGNATURE----- --------------enigA0C4022F1904DCAD3DF5521F--