From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752202AbaHSKEt (ORCPT ); Tue, 19 Aug 2014 06:04:49 -0400 Received: from mail-lb0-f178.google.com ([209.85.217.178]:44083 "EHLO mail-lb0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750767AbaHSKEr (ORCPT ); Tue, 19 Aug 2014 06:04:47 -0400 Date: Tue, 19 Aug 2014 12:04:58 +0200 From: Christoffer Dall To: Eric Auger Cc: eric.auger@st.com, marc.zyngier@arm.com, linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, patches@linaro.org, will.deacon@arm.com, a.motakis@virtualopensystems.com, a.rigo@virtualopensystems.com, paulus@samba.org Subject: Re: [RFC PATCH] ARM: KVM: add irqfd support Message-ID: <20140819100458.GA31086@cbox> References: <1407154102-26459-1-git-send-email-eric.auger@linaro.org> <20140813145523.GR10550@cbox> <53F3107C.6060404@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53F3107C.6060404@linaro.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 19, 2014 at 10:53:16AM +0200, Eric Auger wrote: > On 08/13/2014 04:55 PM, Christoffer Dall wrote: > > On Mon, Aug 04, 2014 at 02:08:22PM +0200, Eric Auger wrote: > >> This patch enables irqfd on ARM. > >> > >> irqfd framework enables to inject a virtual IRQ into a guest upon an > >> eventfd trigger. User-side uses KVM_IRQFD VM ioctl to provide KVM with > >> a kvm_irqfd struct that associates a VM, an eventfd, an IRQ number > >> (aka. the gsi). When an actor signals the eventfd (typically a VFIO > >> platform driver), the kvm irqfd subsystem injects the provided virtual > >> IRQ into the guest. > >> > >> The gsi must correspond to a shared peripheral interrupt (SPI), ie the > >> GIC interrupt ID is gsi+32. > > > > Why can't we support PPIs? > Hi Christoffer, > > Well, in case we want to support PPI at irqfd level, we would need to > change the semantic of the GSI value and use the same as KVM_IRQ_LINE, > to specify the target vcpu. This is obviously feasible but this also > induces changes in currently generic user parts, vfio, vhost. is PPI > injection though irqfd a valid use case? I don't see why you wouldn't want to be able to support PPIs as passthrough interrupts to a guest? [...] > >> + > >> +/* MSI not implemented yet */ > > > > yet? What is an MSI on ARM? > Well some MSI support comes with GICv2m and GICv3. My current > understanding is it makes sense to inject an MSI from an irqfd trigger. > Don't you share this understanding? > Doh, I read GSI and wrote MSI, of course, complete brain meltdown on my side. -Christoffer