From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753510AbcHQW41 (ORCPT ); Wed, 17 Aug 2016 18:56:27 -0400 Received: from mail-lf0-f67.google.com ([209.85.215.67]:36588 "EHLO mail-lf0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752797AbcHQW4Z (ORCPT ); Wed, 17 Aug 2016 18:56:25 -0400 Reply-To: alex.popov@linux.com Subject: Re: [PATCH 1/1] x86/apic: Introduce paravirq irq_domain References: <1470924138-17825-1-git-send-email-alex.popov@linux.com> <1325048698.1236199.1470933872152.JavaMail.zimbra@redhat.com> <54704ec6-4b74-9aa3-cccc-1fb7e2412f9a@linux.com> <8cfa4c43-85d1-462b-176d-c14bf2a0afb5@linux.com> To: Jan Kiszka , Paolo Bonzini Cc: Thomas Gleixner , Christoph Hellwig , Ingo Molnar , Marc Zyngier , "H. Peter Anvin" , Andrew Morton , Kees Cook , Dmitry Vyukov , Jiang Liu , Jason Cooper , Radim Krcmar , Joerg Roedel , linux-kernel@vger.kernel.org, x86@kernel.org, kvm@vger.kernel.org From: Alexander Popov Message-ID: <5aaeb0ec-fd16-ab28-3892-3c6a18165a30@linux.com> Date: Thu, 18 Aug 2016 01:58:51 +0300 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 17.08.2016 17:36, Jan Kiszka wrote: > On 2016-08-15 14:37, Paolo Bonzini wrote: >> On 15/08/2016 13:51, Alexander Popov wrote: >>> It seems to me that the idea of an irq_domain for interrupts injected >>> by a hypervisor is quite generic. >> >> True, but all of Xen, KVM and VMware use PCI devices for this. > > So does Jailhouse. We have to have the code anyway because we need to > keep Linux alive after taking over control. Thus it is actually easier > to reuse the same logic for para-virtualized domains (non-root cells). Hello, Jan! Yes, I see. I can only say that Xen, KVM, VMware and Jailhouse happily use hypercalls, which are a valid interface between a hypervisor and its guests. Positive Technologies hypervisor called Gvandra (named after a big Caucasus mountain) tries to use only the hypercalls and avoid PCI device emulation to become slimmer. Best regards, Alexander