From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH v4 2/2] KVM: VMX: Add Posted Interrupt supporting
Date: Mon, 25 Feb 2013 21:01:02 +0200
Message-ID: <20130225190102.GL21422@redhat.com>
References: <CAEbWaiqodRXAa89WmeSvj0c2k-hKS7hwhSTTE_roUq2zqCNVOg@mail.gmail.com>
 <A9667DDFB95DB7438FA9D7D576C3D87E099BBBBF@SHSMSX101.ccr.corp.intel.com>
 <20130225110159.GA12299@redhat.com>
 <A9667DDFB95DB7438FA9D7D576C3D87E099BBE8E@SHSMSX101.ccr.corp.intel.com>
 <20130225110702.GA12726@redhat.com>
 <A9667DDFB95DB7438FA9D7D576C3D87E099BBEE3@SHSMSX101.ccr.corp.intel.com>
 <20130225133419.GH21422@redhat.com>
 <CAEbWaip14XFVYRzjTbJUS0smO2Q_-Xfi6ngWxBO45KPeZuZsXg@mail.gmail.com>
 <20130225174327.GJ21422@redhat.com>
 <CAEbWaiqKPpaN8vZytOAkwBCb5obGAj-o3M-OM7YFrMbYV-6J-g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Zhang, Xiantao" <xiantao.zhang@intel.com>
To: Avi Kivity <avi.kivity@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:36084 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1759762Ab3BYUxm (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 25 Feb 2013 15:53:42 -0500
Content-Disposition: inline
In-Reply-To: <CAEbWaiqKPpaN8vZytOAkwBCb5obGAj-o3M-OM7YFrMbYV-6J-g@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Mon, Feb 25, 2013 at 08:56:07PM +0200, Avi Kivity wrote:
> On Mon, Feb 25, 2013 at 7:43 PM, Gleb Natapov <gleb@redhat.com> wrote:
> >
> >> > 3. Do not report KVM_IRQ_LINE_STATUS capability and move RTC to use EOI
> >> > notifiers for interrupt reinjection. This requires us to add interface
> >> > for reporting EOI to userspace. This is not in the scope of this
> >> > patchset. Cons: need to introduce new interface (and the one that will
> >> > not work on AMD BTW)
> >> >
> >> > Other ideas?
> >>
> >> 1. inject RTC interrupt
> >> 2. not see EOI
> >> 3. inject RTC interrupt
> >> 4. due to 2, report coalesced
> >>
> > That's the 3 in my list, no?
> 
> 
> No, this idea doesn't involve user interface changes.  We still report
> through KVM_IRQ_LINE_STATUS or whatever it's called.
Interesting idea!

--
			Gleb.