From: Christoffer Dall <cdall@linaro.org>
To: Alexander Graf <agraf@suse.de>
Cc: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
kvm-devel <kvm@vger.kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>,
Pekka Enberg <penberg@iki.fi>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [PATCH v2 2/5] KVM: arm/arm64: Add ARM user space interrupt signaling ABI
Date: Tue, 21 Feb 2017 12:41:53 +0100 [thread overview]
Message-ID: <20170221114153.GA26976@cbox> (raw)
In-Reply-To: <CAFEAcA-HMZnjbnhDC-13rWuQP-X2pk-W-6DvSR8n9_f-e4R=cA@mail.gmail.com>
Hi Alex,
On Fri, Feb 03, 2017 at 05:51:18PM +0000, Peter Maydell wrote:
> On 3 February 2017 at 14:56, Christoffer Dall <cdall@linaro.org> wrote:
> > From: Christoffer Dall <christoffer.dall@linaro.org>
> >
> > 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 events from devices emulated inside the kernel, which may
> > result in interrupt line state changes, so we lose out on for example
> > timer and PMU events if we run with user space gic emulation.
> >
> > Define an ABI to publish such device output levels to userspace.
> >
> > Signed-off-by: Alexander Graf <agraf@suse.de>
> > Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
>
>
> Acked-by: Peter Maydell <peter.maydell@linaro.org>
>
> for the userspace ABI/docs part.
>
Given Peter's ack on this ABI, any chance you could take a look at
fixing the userspace SMP issue and respinning the userspace patches for
this series?
Thanks,
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: cdall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/5] KVM: arm/arm64: Add ARM user space interrupt signaling ABI
Date: Tue, 21 Feb 2017 12:41:53 +0100 [thread overview]
Message-ID: <20170221114153.GA26976@cbox> (raw)
In-Reply-To: <CAFEAcA-HMZnjbnhDC-13rWuQP-X2pk-W-6DvSR8n9_f-e4R=cA@mail.gmail.com>
Hi Alex,
On Fri, Feb 03, 2017 at 05:51:18PM +0000, Peter Maydell wrote:
> On 3 February 2017 at 14:56, Christoffer Dall <cdall@linaro.org> wrote:
> > From: Christoffer Dall <christoffer.dall@linaro.org>
> >
> > 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 events from devices emulated inside the kernel, which may
> > result in interrupt line state changes, so we lose out on for example
> > timer and PMU events if we run with user space gic emulation.
> >
> > Define an ABI to publish such device output levels to userspace.
> >
> > Signed-off-by: Alexander Graf <agraf@suse.de>
> > Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
>
>
> Acked-by: Peter Maydell <peter.maydell@linaro.org>
>
> for the userspace ABI/docs part.
>
Given Peter's ack on this ABI, any chance you could take a look at
fixing the userspace SMP issue and respinning the userspace patches for
this series?
Thanks,
-Christoffer
next prev parent reply other threads:[~2017-02-21 11:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 14:56 [PATCH v2 0/5] Support userspace irqchip with arch timers Christoffer Dall
2017-02-03 14:56 ` Christoffer Dall
2017-02-03 14:56 ` [PATCH v2 1/5] KVM: arm/arm64: Cleanup the arch timer code's irqchip checking Christoffer Dall
2017-02-03 14:56 ` Christoffer Dall
2017-02-03 14:56 ` [PATCH v2 2/5] KVM: arm/arm64: Add ARM user space interrupt signaling ABI Christoffer Dall
2017-02-03 14:56 ` Christoffer Dall
2017-02-03 17:51 ` Peter Maydell
2017-02-03 17:51 ` Peter Maydell
2017-02-21 11:41 ` Christoffer Dall [this message]
2017-02-21 11:41 ` Christoffer Dall
2017-04-05 0:14 ` Alexander Graf
2017-04-05 0:14 ` Alexander Graf
2017-04-05 8:12 ` Christoffer Dall
2017-04-05 8:12 ` Christoffer Dall
2017-02-03 14:56 ` [PATCH v2 3/5] KVM: arm/arm64: Support arch timers with a userspace gic Christoffer Dall
2017-02-03 14:56 ` Christoffer Dall
2017-02-03 14:56 ` [PATCH v2 4/5] KVM: arm/arm64: Report PMU overflow interrupts to userspace irqchip Christoffer Dall
2017-02-03 14:56 ` Christoffer Dall
2017-02-03 14:56 ` [PATCH v2 5/5] KVM: arm/arm64: Advertise support for KVM_CAP_ARM_USER_IRQ Christoffer Dall
2017-02-03 14:56 ` Christoffer Dall
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=20170221114153.GA26976@cbox \
--to=cdall@linaro.org \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=penberg@iki.fi \
--cc=peter.maydell@linaro.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.