Re: [PATCH 0/7] KVM: irqfd generalization prepare patch set

2013-04-25 Thread Alexander Graf
On 21.04.2013, at 12:51, Michael S. Tsirkin 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. >>

Re: [PATCH 0/7] KVM: irqfd generalization prepare patch set

2013-04-25 Thread Alexander Graf
On 25.04.2013, at 09:28, Gleb Natapov wrote: > 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 fa

Re: [PATCH 0/7] KVM: irqfd generalization prepare patch set

2013-04-25 Thread Gleb Natapov
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 > >

Re: [PATCH 0/7] KVM: irqfd generalization prepare patch set

2013-04-24 Thread Gleb Natapov
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 a

Re: [PATCH 0/7] KVM: irqfd generalization prepare patch set

2013-04-21 Thread Michael S. Tsirkin
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 a