From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pekka Enberg <penberg@cs.helsinki.fi>
Subject: KVM guest interrupts, traps, and, exceptions
Date: Sat, 27 Mar 2010 17:43:55 +0200
Message-ID: <4BAE27BB.8040000@cs.helsinki.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
To: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from courier.cs.helsinki.fi ([128.214.9.1]:37152 "EHLO
	mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753545Ab0C0Pn6 (ORCPT <rfc822;kvm@vger.kernel.org>);
	Sat, 27 Mar 2010 11:43:58 -0400
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Hi Avi,

I'm continuing my journey through the KVM API documentation and I'm now 
scratching my head on how interrupts, traps, and exceptions are 
supported by the API. I see KVM_CREATE_IRQCHIP and KVM_IRQ_LINE but I'm 
unable to work out how the host is notified of such events. For example, 
if the guest does

   int $0x10

is there some KVM_EXIT "exit reason" like we have for IO? Is there some 
other mechanism for that? As I haven't yet set up anything related to 
IRQs I can see the host just deadlock on user interrupts.

			Pekka