All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
	linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
	kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v3 0/2] KVM: ARM: Enable vtimers with user space gic
Date: Fri, 16 Sep 2016 15:30:27 +0200	[thread overview]
Message-ID: <20160916133027.GA27036@cbox> (raw)
In-Reply-To: <da8191ca-6fb1-f960-872c-d6bc27172db8@redhat.com>

On Fri, Sep 16, 2016 at 02:31:42PM +0200, Paolo Bonzini wrote:
> 
> 
> On 16/09/2016 14:30, Christoffer Dall 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.
> 
> But it's not a good reason to hold back a feature...
> 

I didn't say that exactly, but choosing not to merge something we cannot
maintain and which we're not paid to look after and where there's a
minimal interest, is not entirely unreasonable.

That being said, I'm not categorically against these patches, but I
share Marc's view that we've already seen that non-vgic support had been
broken for multiple versions without anyone complaining, and without
automated testing or substantial interest in the work, the patches
really are likely to bit-rot.

But I haven't even looked at the patches in detail, I was just replying
to the comment about testing.

-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 v3 0/2] KVM: ARM: Enable vtimers with user space gic
Date: Fri, 16 Sep 2016 15:30:27 +0200	[thread overview]
Message-ID: <20160916133027.GA27036@cbox> (raw)
In-Reply-To: <da8191ca-6fb1-f960-872c-d6bc27172db8@redhat.com>

On Fri, Sep 16, 2016 at 02:31:42PM +0200, Paolo Bonzini wrote:
> 
> 
> On 16/09/2016 14:30, Christoffer Dall 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.
> 
> But it's not a good reason to hold back a feature...
> 

I didn't say that exactly, but choosing not to merge something we cannot
maintain and which we're not paid to look after and where there's a
minimal interest, is not entirely unreasonable.

That being said, I'm not categorically against these patches, but I
share Marc's view that we've already seen that non-vgic support had been
broken for multiple versions without anyone complaining, and without
automated testing or substantial interest in the work, the patches
really are likely to bit-rot.

But I haven't even looked at the patches in detail, I was just replying
to the comment about testing.

-Christoffer

  reply	other threads:[~2016-09-16 13:21 UTC|newest]

Thread overview: 54+ 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 ` 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   ` 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  6:26   ` Alexander Graf
2016-09-16  9:11   ` Peter Maydell
2016-09-16  9:11     ` Peter Maydell
2016-09-16  9:18     ` Alexander Graf
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 10:20   ` Marc Zyngier
2016-09-16 12:18   ` Paolo Bonzini
2016-09-16 12:18     ` Paolo Bonzini
2016-09-16 12:30     ` Christoffer Dall
2016-09-16 12:30       ` Christoffer Dall
2016-09-16 12:31       ` Paolo Bonzini
2016-09-16 12:31         ` Paolo Bonzini
2016-09-16 13:30         ` Christoffer Dall [this message]
2016-09-16 13:30           ` Christoffer Dall
2016-09-16 13:46           ` Andrew Jones
2016-09-16 13:46             ` Andrew Jones
2016-09-16 15:45             ` Paolo Bonzini
2016-09-16 15:45               ` Paolo Bonzini
2016-09-16 19:36             ` Alexander Graf
2016-09-16 19:36               ` Alexander Graf
2016-09-19  7:52               ` Andrew Jones
2016-09-19  7:52                 ` Andrew Jones
2016-09-19 11:45                 ` Alexander Graf
2016-09-19 11:45                   ` Alexander Graf
2016-09-16 13:50           ` Gerd Hoffmann
2016-09-16 13:50             ` Gerd Hoffmann
2016-09-19 10:51           ` Alexander Graf
2016-09-19 10:51             ` Alexander Graf
2016-09-19 11:41             ` Christoffer Dall
2016-09-19 11:41               ` Christoffer Dall
2016-09-16 12:25   ` Alexander Graf
2016-09-16 12:25     ` Alexander Graf
2016-09-16 12:29     ` Christoffer Dall
2016-09-16 12:29       ` Christoffer Dall
2016-09-16 12:40       ` Paolo Bonzini
2016-09-16 12:40         ` Paolo Bonzini
2016-09-16 12:44         ` Alexander Graf
2016-09-16 12:44           ` Alexander Graf
2016-09-16 12:54           ` Paolo Bonzini
2016-09-16 12:54             ` Paolo Bonzini
2016-09-17 15:28           ` Ard Biesheuvel
2016-09-17 15:28             ` Ard Biesheuvel
2016-09-17 15:38             ` Peter Maydell
2016-09-17 15:38               ` Peter Maydell
2016-09-17 16:47               ` Ard Biesheuvel
2016-09-17 16:47                 ` Ard Biesheuvel
2016-09-16 12:43       ` Alexander Graf
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=20160916133027.GA27036@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.zyngier@arm.com \
    --cc=pbonzini@redhat.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.