From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 2/5] KVM: New guest debug interface Date: Mon, 08 Dec 2008 16:57:58 +0200 Message-ID: <493D35F6.10002@redhat.com> References: <20081127114342.10901.31992.stgit@mchn012c.ww002.siemens.net> <20081127114343.10901.26107.stgit@mchn012c.ww002.siemens.net> <493B9DAE.7050007@redhat.com> <493CE546.2030507@siemens.com> <493CEA10.2000104@redhat.com> <493D255B.908@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Hollis Blanchard , Joerg Roedel To: Jan Kiszka Return-path: Received: from mx2.redhat.com ([66.187.237.31]:43679 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753021AbYLHO6J (ORCPT ); Mon, 8 Dec 2008 09:58:09 -0500 In-Reply-To: <493D255B.908@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: Jan Kiszka wrote: > FYI: I just passed the kgdbts test with some Linux guest on an Opteron > 2216. Also using hbreak with gdb inside the guest appears to work. There > are just a few to-be-analyzed guest lockups/kernel panics that may > relate to the fact that the kernels were build for Intel CPUs. On the > other hand, it would be far too simple if it worked already - compared > to the pain I went through with VMX... > So long as it doesn't crash, this functionality is far enough from mainstream use. btw, is it possible to emulate the old interface on top of the new implementation? I feel unconfortable with dropping an interface (albeit an unused one) without even a warning. -- error compiling committee.c: too many arguments to function