From: Alexander Graf <agraf@suse.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm-devel <kvm@vger.kernel.org>, qemu-arm <qemu-arm@nongnu.org>
Subject: [PATCH RFC v2 0/2] Enable cp15 timers with user space gic & kvm
Date: Mon, 14 Nov 2016 15:32:13 +0100 [thread overview]
Message-ID: <1479133935-63848-1-git-send-email-agraf@suse.de> (raw)
When running with KVM enabled, you can choose between emulating the
gic in kernel or user space. If the kernel supports in-kernel virtualization
of the interrupt controller, it will default to that. If not, if will
default to user space emulation.
Unfortunately when running in user mode gic emulation, we miss out on
timer events which are only available from kernel space.
This patch set leverages the new kernel/user space pending line synchronization
for those timer events.
rfc1 -> rfc2:
- use local variable for ARM_CPU
- remove bear trap
- move timer warning to gic device
Alexander Graf (2):
linux-headers: update
ARM: KVM: Enable in-kernel timers with user space gic
hw/intc/arm_gic.c | 7 +++++++
include/sysemu/kvm.h | 11 +++++++++++
kvm-all.c | 5 +++++
kvm-stub.c | 5 +++++
linux-headers/asm-arm/kvm.h | 1 +
linux-headers/asm-arm64/kvm.h | 1 +
linux-headers/linux/kvm.h | 6 ++++++
target-arm/cpu.h | 3 +++
target-arm/kvm.c | 20 ++++++++++++++++++++
9 files changed, 59 insertions(+)
--
1.8.5.6
next reply other threads:[~2016-11-14 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 14:32 Alexander Graf [this message]
2016-11-14 14:32 ` [PATCH RFC v2 1/2] linux-headers: update Alexander Graf
2016-11-14 14:32 ` [PATCH RFC v2 2/2] ARM: KVM: Enable in-kernel timers with user space gic Alexander Graf
2016-12-13 13:20 ` Peter Maydell
2017-06-26 15:03 ` [Qemu-devel] " Andrew Jones
2017-06-26 21:32 ` Alexander Graf
2017-06-27 12:40 ` Andrew Jones
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=1479133935-63848-1-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).