From: Alexander Popov <alex.popov@linux.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Marc Zyngier <marc.zyngier@arm.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
Dmitry Vyukov <dvyukov@google.com>,
Jiang Liu <jiang.liu@linux.intel.com>,
Jason Cooper <jason@lakedaemon.net>,
Radim Krcmar <rkrcmar@redhat.com>, Joerg Roedel <joro@8bytes.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
kvm@vger.kernel.org
Subject: Re: [PATCH 1/1] x86/apic: Introduce paravirq irq_domain
Date: Thu, 18 Aug 2016 01:58:51 +0300 [thread overview]
Message-ID: <5aaeb0ec-fd16-ab28-3892-3c6a18165a30@linux.com> (raw)
In-Reply-To: <e72b9d24-48ee-068b-cd70-6d1550f91538@siemens.com>
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
next prev parent reply other threads:[~2016-08-17 22:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 14:02 [PATCH 1/1] x86/apic: Introduce paravirq irq_domain Alexander Popov
2016-08-11 16:44 ` Paolo Bonzini
2016-08-12 10:56 ` Alexander Popov
2016-08-12 11:43 ` Paolo Bonzini
2016-08-12 22:07 ` Alexander Popov
2016-08-13 6:20 ` Paolo Bonzini
2016-08-15 11:51 ` Alexander Popov
2016-08-15 12:37 ` Paolo Bonzini
2016-08-16 20:00 ` Alexander Popov
2016-08-17 14:36 ` Jan Kiszka
2016-08-17 22:58 ` Alexander Popov [this message]
2016-08-19 10:47 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5aaeb0ec-fd16-ab28-3892-3c6a18165a30@linux.com \
--to=alex.popov@linux.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=jason@lakedaemon.net \
--cc=jiang.liu@linux.intel.com \
--cc=joro@8bytes.org \
--cc=keescook@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox