From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: KVM on Via Nano (Isaiah) CPUs? Date: Mon, 23 Mar 2009 20:41:02 +0200 Message-ID: <49C7D7BE.8040807@redhat.com> References: <200903180902.29139.andreas.tanz@kvt.de> <200903231439.34107.andreas.tanz@kvt.de> <49C797F6.8070308@redhat.com> <200903231833.46550.andreas.tanz@kvt.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: andreas.tanz@kvt.de Return-path: Received: from mx2.redhat.com ([66.187.237.31]:51864 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752303AbZCWSkd (ORCPT ); Mon, 23 Mar 2009 14:40:33 -0400 In-Reply-To: <200903231833.46550.andreas.tanz@kvt.de> Sender: kvm-owner@vger.kernel.org List-ID: Andreas Tanz wrote: > [ 3732.020033] returning from kvm_handle_exit, cause 3, retval = 1, exit_reason = 7 > Here, vmx tells us that the guest is ready to accept interrupts (having executed the sti instruction) > [ 3732.020044] vmx->vmx_vcpu_run() 00 : vmcs_read32(VM_ENTRY_INTR_INFO_FIELD) returned 0x80000408 > ... noticing that, kvm injects a timer interrupt that was previously blocked ... > [ 3732.020056] vmx->handle_exception 00 : giving some infos > [ 3732.020062] vmx->handle_exception 01 : vect_info: 0x0 > [ 3732.020067] vmx->handle_exception 02 : intr_info: 0x80000b0d, is_page_fault()==0 > ... and the Nano rewards us with a General Protection Fault instead of injecting the interrupt. Will talk to the specification and come up with further tests. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.