From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: [PATCH 0/7] KVM: irqfd generalization prepare patch set Date: Thu, 25 Apr 2013 10:28:14 +0300 Message-ID: <20130425072814.GV12401@redhat.com> References: <1366133175-23986-1-git-send-email-agraf@suse.de> <20130424102031.GK12401@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: kvm-ppc@vger.kernel.org, "kvm@vger.kernel.org mailing list" , Scott Wood , Marcelo Tosatti To: Alexander Graf Return-path: Content-Disposition: inline In-Reply-To: <20130424102031.GK12401@redhat.com> Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Wed, Apr 24, 2013 at 01:20:31PM +0300, Gleb Natapov wrote: > On Tue, Apr 16, 2013 at 07:26:08PM +0200, Alexander Graf wrote: > > The concept of an irqfd and interrupt routing are nothing particularly tied > > into the IOAPIC implementation. In fact, most of the code already is perfectly > > generic. > > > > This patch set decouples most bits of the existing irqchip and irqfd > > implementation to make it reusable for non-IOAPIC platforms, like the PPC MPIC. > > > > I also have a patch that implements working irqfd support on top of these, > > but that requires the in-kernel MPIC implementation to go upstream first, so > > I'm holding off on it until we settled everything there, so the concept > > certainly does work. > > > > Alex > > > Nice cleanup, thanks! Should expect a new series with "ifdef > kvm_irqchip" and ia64 compilation fixed. The fixes are minor enough for > me to fix them while applying. > Actually the series does not apply any more and has to be rebased on top of the current queue. -- Gleb.