From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] KVM: arm/arm64: Add ARM arch timer interrupts ABI
Date: Tue, 1 Nov 2016 16:32:32 +0100 [thread overview]
Message-ID: <20161101153232.GD13677@cbox> (raw)
In-Reply-To: <CAFEAcA_mdrTUBBDV91X3Zo6pNzVaukQ7foN+cPt_41+ouBdEfQ@mail.gmail.com>
On Tue, Nov 01, 2016 at 02:54:11PM +0000, Peter Maydell wrote:
> On 1 November 2016 at 14:50, Christoffer Dall
> <christoffer.dall@linaro.org> wrote:
> > On Tue, Nov 01, 2016 at 11:26:54AM +0000, Peter Maydell wrote:
> >> Possible current and future outbound interrupt lines (some of these
> >> would only show up in some unlikely or lots-of-implementation-needed
> >> cases, I'm just trying to produce an exhaustive list):
> >> * virtual timer
> >> * physical timer
> >> * hyp timer (nested virtualization case)
> >> * secure timer (unlikely but maybe if EL3 is ever supported inside a VM)
> >> * gic maintenance interrupt (nested virt again)
> >> * PMU interrupt
> >
> > Thanks for the list, that's good to have around for the future.
> >
> > There's also the potential of the EL2 virtual timer for nested VHE
> > support, right?
>
> That's the one I meant by "hyp timer".
>
there's the hyp timer, and then there's the ARMv8.1 virtual hyp timer.
> >> The kernel doesn't know which interrupt number these would be wired
> >> up to, so they're all just arbitrary outputs, and you could put them
> >> in one field or split them up into multiple fields, it doesn't make
> >> much difference.
> >>
> >
> > So if we keep this we're kind of suggesting that we'll have a field per
> > device type later on. Since this is a u8 and we are talking about up 5
> > 5 timers already,
>
> 4.
>
virtual
physical
hyp
virtual hyp
secure
Am I missing something?
-Christoffer
next prev parent reply other threads:[~2016-11-01 15:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 19:08 [PATCH 0/3] Support userspace irqchip with arch timers Christoffer Dall
2016-09-27 19:08 ` [PATCH 1/3] KVM: arm/arm64: Cleanup the arch timer code's irqchip checking Christoffer Dall
2016-09-27 19:08 ` [PATCH 2/3] KVM: arm/arm64: Add ARM arch timer interrupts ABI Christoffer Dall
2016-11-01 11:26 ` Peter Maydell
2016-11-01 14:50 ` Christoffer Dall
2016-11-01 14:54 ` Peter Maydell
2016-11-01 15:32 ` Christoffer Dall [this message]
2016-11-01 16:56 ` Marc Zyngier
2016-09-27 19:08 ` [PATCH 3/3] KVM: arm/arm64: Support arch timers with a userspace gic Christoffer Dall
2016-09-29 15:11 ` [PATCH 0/3] Support userspace irqchip with arch timers Alexander Graf
2016-09-30 14:54 ` Alexander Graf
2016-09-30 15:38 ` Alexander Graf
2016-09-30 15:43 ` Christoffer Dall
2016-09-30 15:55 ` Alexander Graf
2016-09-30 19:31 ` Alexander Graf
2016-10-28 14:38 ` Marc Zyngier
2016-10-28 15:52 ` Alexander Graf
2016-10-28 15:57 ` Marc Zyngier
2016-10-28 20:25 ` Alexander Graf
2016-10-29 13:19 ` Paolo Bonzini
2016-10-29 18:55 ` 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=20161101153232.GD13677@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).