From: Christoffer Dall <christoffer.dall@linaro.org>
To: Alexander Graf <agraf@suse.de>
Cc: linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Subject: Re: [PATCH v2] KVM: arm/arm64: Route vtimer events to user space
Date: Fri, 16 Sep 2016 11:44:33 +0200 [thread overview]
Message-ID: <20160916094433.GA4794@cbox> (raw)
In-Reply-To: <1474002553-30079-1-git-send-email-agraf@suse.de>
Alex,
On Fri, Sep 16, 2016 at 07:09:13AM +0200, Alexander Graf wrote:
> We have 2 modes for dealing with interrupts in the ARM world. We can either
> handle them all using hardware acceleration through the vgic or we can emulate
> a gic in user space and only drive CPU IRQ pins from there.
>
> Unfortunately, when driving IRQs from user space, we never tell user space
> about timer events that may result in interrupt line state changes, so we
> lose out on timer events if we run with user space gic emulation.
>
> This patch set fixes that by routing vtimer expiration events to user space.
> With this patch I can successfully run edk2 and Linux with user space gic
> emulation.
I have two versions of v2. Are there any differences or did it just go
out twice or got duplicated somehow on my end?
Thanks,
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] KVM: arm/arm64: Route vtimer events to user space
Date: Fri, 16 Sep 2016 11:44:33 +0200 [thread overview]
Message-ID: <20160916094433.GA4794@cbox> (raw)
In-Reply-To: <1474002553-30079-1-git-send-email-agraf@suse.de>
Alex,
On Fri, Sep 16, 2016 at 07:09:13AM +0200, Alexander Graf wrote:
> We have 2 modes for dealing with interrupts in the ARM world. We can either
> handle them all using hardware acceleration through the vgic or we can emulate
> a gic in user space and only drive CPU IRQ pins from there.
>
> Unfortunately, when driving IRQs from user space, we never tell user space
> about timer events that may result in interrupt line state changes, so we
> lose out on timer events if we run with user space gic emulation.
>
> This patch set fixes that by routing vtimer expiration events to user space.
> With this patch I can successfully run edk2 and Linux with user space gic
> emulation.
I have two versions of v2. Are there any differences or did it just go
out twice or got duplicated somehow on my end?
Thanks,
-Christoffer
next prev parent reply other threads:[~2016-09-16 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 5:09 [PATCH v2] KVM: arm/arm64: Route vtimer events to user space Alexander Graf
2016-09-16 5:09 ` Alexander Graf
2016-09-16 9:44 ` Christoffer Dall [this message]
2016-09-16 9:44 ` Christoffer Dall
2016-09-16 12:28 ` Alexander Graf
2016-09-16 12:28 ` Alexander Graf
-- strict thread matches above, loose matches on Subject: below --
2016-09-16 5:06 Alexander Graf
2016-09-16 5:06 ` Alexander Graf
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=20160916094433.GA4794@cbox \
--to=christoffer.dall@linaro.org \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.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 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.