From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] KVM: ARM: Enable vtimers with user space gic
Date: Fri, 16 Sep 2016 14:30:39 +0200 [thread overview]
Message-ID: <20160916123039.GB14140@cbox> (raw)
In-Reply-To: <7beb406b-6194-8451-2d92-9a4394ef91dd@redhat.com>
On Fri, Sep 16, 2016 at 02:18:45PM +0200, Paolo Bonzini wrote:
>
>
> On 16/09/2016 12:20, Marc Zyngier wrote:
> > > This patch set allows user space to receive vtimer events as well as mask
> > > them, so that we can handle all vtimer related interrupt injection from user
> > > space, enabling us to use architected timer with user space gic emulation.
> >
> > I have already voiced my concerns in the past, including face to face,
> > and I'm going to repeat it: I not keen at all on adding a new userspace
> > interface that is going to bitrot extremely quickly.
>
> You don't have automated tests set up? It's not going to bitrot if you
> test it, either with kvm-unit-tests or just by smoke-testing Linux.
> It's _for_ the raspi, but it's not limited to it.
>
Our automated testing situation is not great, no. Something we're
looking at, but have resource problems with.
-Christoffer
next prev parent reply other threads:[~2016-09-16 12:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 6:26 [PATCH v3 0/2] KVM: ARM: Enable vtimers with user space gic Alexander Graf
2016-09-16 6:26 ` [PATCH v3 1/2] KVM: arm/arm64: Add vcpu ENABLE_CAP functionality Alexander Graf
2016-09-16 6:26 ` [PATCH v3 2/2] KVM: arm/arm64: Route vtimer events to user space Alexander Graf
2016-09-16 9:11 ` Peter Maydell
2016-09-16 9:18 ` Alexander Graf
2016-09-16 10:20 ` [PATCH v3 0/2] KVM: ARM: Enable vtimers with user space gic Marc Zyngier
2016-09-16 12:18 ` Paolo Bonzini
2016-09-16 12:30 ` Christoffer Dall [this message]
2016-09-16 12:31 ` Paolo Bonzini
2016-09-16 13:30 ` Christoffer Dall
2016-09-16 13:46 ` Andrew Jones
2016-09-16 15:45 ` Paolo Bonzini
2016-09-16 19:36 ` Alexander Graf
2016-09-19 7:52 ` Andrew Jones
2016-09-19 11:45 ` Alexander Graf
2016-09-16 13:50 ` Gerd Hoffmann
2016-09-19 10:51 ` Alexander Graf
2016-09-19 11:41 ` Christoffer Dall
2016-09-16 12:25 ` Alexander Graf
2016-09-16 12:29 ` Christoffer Dall
2016-09-16 12:40 ` Paolo Bonzini
2016-09-16 12:44 ` Alexander Graf
2016-09-16 12:54 ` Paolo Bonzini
2016-09-17 15:28 ` Ard Biesheuvel
2016-09-17 15:38 ` Peter Maydell
2016-09-17 16:47 ` Ard Biesheuvel
2016-09-16 12:43 ` 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=20160916123039.GB14140@cbox \
--to=christoffer.dall@linaro.org \
--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 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).