From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v3 1/8] ARM: KVM: Initial skeleton to compile KVM support Date: Sun, 05 Jun 2011 19:28:15 +0300 Message-ID: <4DEBAE9F.2010400@redhat.com> References: <20110603150318.17011.82777.stgit@ubuntu> <4DE8FE38.6030405@siemens.com> <4DE90397.5080801@siemens.com> <4DEB74DA.2040909@redhat.com> <4DEB8F22.1020802@web.de> <4DEB9033.9060109@redhat.com> <4DEB998E.1010805@web.de> <4DEB9C60.1030001@redhat.com> <4DEB9D4A.9060702@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , catalin.marinas@arm.com, android-virt@lists.cs.columbia.edu, s.raho@virtualopensystems.com, a.motakis@virtualopensystems.com, kvm@vger.kernel.org, a.costa@virtualopensystems.com To: Christoffer Dall Return-path: Received: from mx1.redhat.com ([209.132.183.28]:14358 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752533Ab1FEQ2j (ORCPT ); Sun, 5 Jun 2011 12:28:39 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 06/05/2011 07:25 PM, Christoffer Dall wrote: > >> > >> An additional advantage is that this is a vm ioctl, not a vcpu ioctl, so > >> no need to interrupt the vcpu thread in userspace in order to queue an > >> interrupt. Of course, it still happens in the kernel, but it's easier > >> for userspace to implement its device model this way. > > > > So supporting this over existing archs would have some benefits as well, > > though a bit smaller if in-kernel irqchip is already implemented. > > > > Could you elaborate what you mean here? I'm not really following. Are > you suggesting a new arch-generic interface? (Pardon my ignorance). Using KVM_IRQ_LINE everywhere except s390, not just in x86 and ARM. -- error compiling committee.c: too many arguments to function