From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Kernel GPF in vmx_save_host_state() Date: Thu, 19 Mar 2009 12:30:22 +0200 Message-ID: <49C21EBE.5070305@redhat.com> References: <49C0313C.5010906@cs.cmu.edu> <20090319040440.GA2778@amit-x200.pnq.redhat.com> <49C216AD.7080206@redhat.com> <20090319101642.GA7924@amit-x200.pnq.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Benjamin Gilbert , kvm@vger.kernel.org, glommer@redhat.com To: Amit Shah Return-path: Received: from mx2.redhat.com ([66.187.237.31]:45596 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752271AbZCSKa3 (ORCPT ); Thu, 19 Mar 2009 06:30:29 -0400 In-Reply-To: <20090319101642.GA7924@amit-x200.pnq.redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Amit Shah wrote: > What action should the kernel take, though? If lm is advertised and we > don't let the guest enter long mode -- exit to userspace and close the > VM? > Since it should never happen, it doesn't really matter. #GP will be the natural action (setting reserved bit); userspace lied to the guest, and we can't recover from that. -- error compiling committee.c: too many arguments to function