From: Pavel Fedin <p.fedin@samsung.com>
To: kvm@vger.kernel.org
Cc: Marc Zyngier <marc.zyngier@arm.com>
Subject: [RFC 0/2] Propagate virtual timer interrupts to userspace
Date: Fri, 24 Jul 2015 18:23:33 +0300 [thread overview]
Message-ID: <cover.1437750590.git.p.fedin@samsung.com> (raw)
This patchset allows virtual timer to function without vGIC. In this case
the interrupt should be handled by userspace GIC emulation.
In order to signal an interrupt a VM exit is performed with KVM_EXIT_IRQ
return code. Together with the code, IRQ number and level is returned.
'level' is actually reserved for possible future level-sensitive interrupts.
For them KVM_EXIT_IRQ code would be generated upon line state transition
to the specified level. For edge-sensitive interrupts actually only 'irq'
number is meaningful, signalling trigger condition on the specified IRQ.
However, 'level' still denotes active state (1 for low-to-high edge or 0
for high-to-low edge).
Currently there's no additional API to specify how to treate particular
IRQs in the userspace. The userspace is assumed just to know it. On ARM
architecture all interrupts are processed by KVM as if they were
edge-sensitive, therefore timer interrupt as signalled as edge-sensitive,
active high.
This patch set is to be applied on top of "Allow to use KVM without
in-kernel irqchip" one.
Pavel Fedin (2):
Introduce KVM_EXIT_IRQ
Send KVM_EXIT_IRQ from timer if irqchip is not used
arch/arm/kvm/arm.c | 18 +++++++++++-------
include/linux/kvm_host.h | 7 +++++++
include/uapi/linux/kvm.h | 3 +++
virt/kvm/arm/arch_timer.c | 6 ++++++
4 files changed, 27 insertions(+), 7 deletions(-)
--
2.4.4
next reply other threads:[~2015-07-24 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 15:23 Pavel Fedin [this message]
2015-07-24 15:23 ` [RFC 1/2] Introduce KVM_EXIT_IRQ Pavel Fedin
2015-07-24 15:23 ` [RFC 2/2] Send KVM_EXIT_IRQ from timer if irqchip is not used Pavel Fedin
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=cover.1437750590.git.p.fedin@samsung.com \
--to=p.fedin@samsung.com \
--cc=kvm@vger.kernel.org \
--cc=marc.zyngier@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.