From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [RFC PATCH 4/5] APIC/IOAPIC EOI callback Date: Sun, 11 Jul 2010 23:12:46 +0300 Message-ID: <20100711201246.GA12544@redhat.com> References: <20100711180910.20121.93313.stgit@localhost6.localdomain6> <20100711180936.20121.35376.stgit@localhost6.localdomain6> <4C3A09F3.8010304@redhat.com> <1278872784.20397.18.camel@x201> <4C3A0DE3.8010806@redhat.com> <20100711185456.GA11048@redhat.com> <1278876078.20397.79.camel@x201> <20100711192330.GA11491@redhat.com> <1278878614.20397.128.camel@x201> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , kvm@vger.kernel.org, qemu-devel@nongnu.org, pugs@cisco.com, chrisw@redhat.com To: Alex Williamson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:19351 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754101Ab0GKUSX (ORCPT ); Sun, 11 Jul 2010 16:18:23 -0400 Content-Disposition: inline In-Reply-To: <1278878614.20397.128.camel@x201> Sender: kvm-owner@vger.kernel.org List-ID: On Sun, Jul 11, 2010 at 02:03:34PM -0600, Alex Williamson wrote: > > What about threaded interrupts? Just to make the point, imagine a nested virt situation which uses current kvm device assignment in guest. Look at the interrupt handler we have there. -- Alex