From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Exception handling between QEMU and KVM Date: Wed, 01 Jul 2009 12:00:16 +0300 Message-ID: <4A4B25A0.70800@redhat.com> References: <7d08b87d0906302028q4bd7c9efifd399be9529fdc5b@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Andreas Nilsson To: Christoffer Dall Return-path: In-Reply-To: <7d08b87d0906302028q4bd7c9efifd399be9529fdc5b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> Sender: kvm-ppc-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: kvm.vger.kernel.org On 07/01/2009 06:28 AM, Christoffer Dall wrote: > Hi all. > > We are still working on our ARM port of KVM and we are managing to let > the guest decompress the kernel image and run from relocated address > and we can support enabling MMU before this. > > Howver, to debug relocated micro-hypervisor for exception handling, we > are trying to implement some NOT_IMPLEMENTED() macros and ASSERT() > macros. > > What we have done so far is simply to exit QEMU roughly after > returning -EINVAL from the KVM_RUN system call, but before we start > supporting an interrupt cycle we have to improve on this. Setting > kvm_run->exit_reason = KVM_EXIT_EXCEPTION or kvm_run->exit_reason = > KVM_EXIT_SHUTDOWN just results in QEMU looping in the cpu execution > loop. > > Can someone point us in the direction of what we're missing here in > order to exit the whole QEMU process from an exception occurring > inside the guest? > Not sure I understand. Can't you call exit() or abort() after kvm returns an error? -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html