From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Maydell Subject: Re: [Android-virt] [PATCH v5 05/13] ARM: KVM: Inject IRQs and FIQs from userspace Date: Sun, 11 Dec 2011 22:35:29 +0000 Message-ID: References: <20111211102403.21693.6887.stgit@localhost> <20111211102449.21693.12265.stgit@localhost> <4EE4C9D8.1010601@web.de> <-4744042178058961854@unknownmsgid> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: Christoffer Dall , "kvm@vger.kernel.org" , "Marc.Zyngier@arm.com" , Jan Kiszka , "avi@redhat.com" , "android-virt@lists.cs.columbia.edu" , "tech@virtualopensystems.com" To: Christoffer Dall Return-path: Received: from mail-qw0-f53.google.com ([209.85.216.53]:59153 "EHLO mail-qw0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752304Ab1LKWf3 (ORCPT ); Sun, 11 Dec 2011 17:35:29 -0500 Received: by qadb15 with SMTP id b15so4197713qad.19 for ; Sun, 11 Dec 2011 14:35:29 -0800 (PST) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 11 December 2011 22:12, Peter Maydell wrote: > (Actually what would be clearest would be if the ioctl took the > (interrupt-target, interrupt-line-for-that-target, value-of-line) > tuple as three separate values rather than encoding two of them into > a single integer, but I assume there's a reason we can't have that.) Have you thought about how this encoding scheme would be extended when we move to using the VGIC and an in-kernel interrupt controller implementation, incidentally? I haven't really looked into that at all, but I assume that then QEMU is going to start having to tell the kernel it wants to deliver interrupt 35 to the GIC, and so on... -- PMM