From: Marc Zyngier <marc.zyngier@arm.com>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
Andre Przywara <andre.przywara@arm.com>,
Eric Auger <eric.auger@redhat.com>
Subject: Re: [PATCH v8 9/9] KVM: arm/arm64: Update timer and forwarded irq documentation
Date: Tue, 19 Dec 2017 20:35:04 +0000 [thread overview]
Message-ID: <20171219203504.1dbb9226@why.wild-wind.fr.eu.org> (raw)
In-Reply-To: <20171219202954.GC5380@cbox>
On Tue, 19 Dec 2017 21:29:54 +0100
Christoffer Dall <christoffer.dall@linaro.org> wrote:
> On Wed, Dec 13, 2017 at 08:15:10PM +0000, Marc Zyngier wrote:
> > On Wed, 13 Dec 2017 10:46:02 +0000,
> > Christoffer Dall wrote:
> > >
> > > Now when we've reworked how mapped level-triggered interrupts are
> > > processed for the timer interrupts, we update the documentation
> > > correspondingly.
> >
> > Seems like the documentation is more out of date than we thought, see
> > below.
> >
>
> Indeed. And I wondered if we should just nuke this file. The reason I
> added it originally was that the concept of "never taking the interrupt"
> was confusing to most, and we had to explain it several times over, but
> perhaps it's really not needed anymore and we should let people read the
> code instead?
Suits me (maintaining documentation is hard). I suggest we delete it
and write the perfect explanation once KVM is completely done...
M.
--
Without deviation from the norm, progress is not possible.
WARNING: multiple messages have this Message-ID (diff)
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 9/9] KVM: arm/arm64: Update timer and forwarded irq documentation
Date: Tue, 19 Dec 2017 20:35:04 +0000 [thread overview]
Message-ID: <20171219203504.1dbb9226@why.wild-wind.fr.eu.org> (raw)
In-Reply-To: <20171219202954.GC5380@cbox>
On Tue, 19 Dec 2017 21:29:54 +0100
Christoffer Dall <christoffer.dall@linaro.org> wrote:
> On Wed, Dec 13, 2017 at 08:15:10PM +0000, Marc Zyngier wrote:
> > On Wed, 13 Dec 2017 10:46:02 +0000,
> > Christoffer Dall wrote:
> > >
> > > Now when we've reworked how mapped level-triggered interrupts are
> > > processed for the timer interrupts, we update the documentation
> > > correspondingly.
> >
> > Seems like the documentation is more out of date than we thought, see
> > below.
> >
>
> Indeed. And I wondered if we should just nuke this file. The reason I
> added it originally was that the concept of "never taking the interrupt"
> was confusing to most, and we had to explain it several times over, but
> perhaps it's really not needed anymore and we should let people read the
> code instead?
Suits me (maintaining documentation is hard). I suggest we delete it
and write the perfect explanation once KVM is completely done...
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2017-12-19 20:35 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 10:45 [PATCH v8 0/9] Handle forwarded level-triggered interrupts Christoffer Dall
2017-12-13 10:45 ` Christoffer Dall
2017-12-13 10:45 ` [PATCH v8 1/9] KVM: arm/arm64: Remove redundant preemptible checks Christoffer Dall
2017-12-13 10:45 ` Christoffer Dall
2017-12-13 10:45 ` [PATCH v8 2/9] KVM: arm/arm64: Factor out functionality to get vgic mmio requester_vcpu Christoffer Dall
2017-12-13 10:45 ` Christoffer Dall
2017-12-13 10:45 ` [PATCH v8 3/9] KVM: arm/arm64: Don't cache the timer IRQ level Christoffer Dall
2017-12-13 10:45 ` Christoffer Dall
2017-12-13 19:38 ` Marc Zyngier
2017-12-13 19:38 ` Marc Zyngier
2017-12-19 14:17 ` Julien Thierry
2017-12-19 14:17 ` Julien Thierry
2017-12-19 20:35 ` Christoffer Dall
2017-12-19 20:35 ` Christoffer Dall
2017-12-13 10:45 ` [PATCH v8 4/9] KVM: arm/arm64: vgic: Support level-triggered mapped interrupts Christoffer Dall
2017-12-13 10:45 ` Christoffer Dall
2017-12-13 10:45 ` [PATCH v8 5/9] KVM: arm/arm64: Support a vgic interrupt line level sample function Christoffer Dall
2017-12-13 10:45 ` Christoffer Dall
2017-12-13 10:45 ` [PATCH v8 6/9] KVM: arm/arm64: Support VGIC dist pend/active changes for mapped IRQs Christoffer Dall
2017-12-13 10:45 ` Christoffer Dall
2017-12-13 10:46 ` [PATCH v8 7/9] KVM: arm/arm64: Provide a get_input_level for the arch timer Christoffer Dall
2017-12-13 10:46 ` Christoffer Dall
2017-12-13 19:45 ` Marc Zyngier
2017-12-13 19:45 ` Marc Zyngier
2017-12-13 10:46 ` [PATCH v8 8/9] KVM: arm/arm64: Avoid work when userspace iqchips are not used Christoffer Dall
2017-12-13 10:46 ` Christoffer Dall
2017-12-13 20:05 ` Marc Zyngier
2017-12-13 20:05 ` Marc Zyngier
2017-12-19 13:34 ` Christoffer Dall
2017-12-19 13:34 ` Christoffer Dall
2017-12-19 13:55 ` Marc Zyngier
2017-12-19 13:55 ` Marc Zyngier
2017-12-19 14:18 ` Christoffer Dall
2017-12-19 14:18 ` Christoffer Dall
2017-12-19 14:32 ` Marc Zyngier
2017-12-19 14:32 ` Marc Zyngier
2017-12-13 10:46 ` [PATCH v8 9/9] KVM: arm/arm64: Update timer and forwarded irq documentation Christoffer Dall
2017-12-13 10:46 ` Christoffer Dall
2017-12-13 20:15 ` Marc Zyngier
2017-12-13 20:15 ` Marc Zyngier
2017-12-19 20:29 ` Christoffer Dall
2017-12-19 20:29 ` Christoffer Dall
2017-12-19 20:35 ` Marc Zyngier [this message]
2017-12-19 20:35 ` Marc Zyngier
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=20171219203504.1dbb9226@why.wild-wind.fr.eu.org \
--to=marc.zyngier@arm.com \
--cc=andre.przywara@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@redhat.com \
--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.