From: Thomas Gleixner <tglx@linutronix.de>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-arch@vger.kernel.org, linux-mips@linux-mips.org,
linux-am33-list@redhat.com, linux-ia64@vger.kernel.org,
linux-c6x-dev@linux-c6x.org, linux-parisc@vger.kernel.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
adi-buildroot-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
linux-alpha@vger.kernel.org, x86@kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/3] x86, irq: Rename VECTOR_UNDEFINED and VECTOR_RETRIGGERED to IRQ_*
Date: Fri, 17 Jul 2015 16:06:54 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1507171558010.18576@nanos> (raw)
Message-ID: <20150717140654.HcPduANUEMEP-7NMPTyj-ktkC718E7pwXQuiXTHMdmM@z> (raw)
In-Reply-To: <20150712220154.7166.48327.stgit@bhelgaas-glaptop2.roam.corp.google.com>
On Sun, 12 Jul 2015, Bjorn Helgaas wrote:
> The per-cpu vector_irq[] table is indexed by CPU vector numbers, and each
> entry contains an IRQ number.
>
> Rename the special values VECTOR_UNDEFINED and VECTOR_RETRIGGERED to
> IRQ_UNDEFINED and IRQ_RETRIGGERED to indicate that they are in the IRQ
> number space, not the CPU vector number space.
Makes some sense, but OTOH vector_irq actually reflects the vector
state not the irq number state. The fact that we store the Linux irq
number in vector_irq is just an implementation detail.
VECTOR_UNDEFINED is certainly a misnomer; that should be VECTOR_UNUSED
VECTOR_RETRIGGERED is pretty accurate. In the case we retrigger an
interrupt, we merily use the Linux irq number to figure out which
vector to kick. And after we retriggered it, we lose the association
to the Linux irq number completely.
That said, I'm working on storing the irq descriptor pointer in
vector_irq instead of the irq number, which has the advantage that we
avoid the lookup of the irq descriptor in the interrupt hotpath.
Thanks,
tglx
next prev parent reply other threads:[~2015-07-17 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-12 22:01 [PATCH 0/3] IRQ trivial clarifications Bjorn Helgaas
[not found] ` <20150712220154.69FhyRpGu7t7LGxef1_lZLW5DTtjnS9ZftcIRA_u3yM@z>
2015-07-12 22:01 ` [PATCH 1/3] x86, irq: Rename VECTOR_UNDEFINED and VECTOR_RETRIGGERED to IRQ_* Bjorn Helgaas
[not found] ` <20150717140654.HcPduANUEMEP-7NMPTyj-ktkC718E7pwXQuiXTHMdmM@z>
2015-07-17 14:06 ` Thomas Gleixner [this message]
[not found] ` <20150717175005.2PlYOf0u2qPgVsqTCvNtUs-fPZzf1WtW6hNE2-FoR0I@z>
2015-07-17 17:50 ` Bjorn Helgaas
[not found] ` <20150712220202.f9KliyDwO6IFU43gC5ZsnEy7raDmWwea-j1X67SBaLE@z>
2015-07-12 22:02 ` [PATCH 2/3] x86, irq: Clarify "No irq handler" message Bjorn Helgaas
[not found] ` <20150712220211.Bpjwxxqm9qIh456M5VmuH88Is0DuGm8BXdBwTbSbmjA@z>
2015-07-12 22:02 ` [PATCH 3/3] IRQ: Print "unexpected IRQ" messages consistently across architectures Bjorn Helgaas
[not found] ` <20150713032303.WfTEmQh0az1X1qkGyv-NrJ0d47RgMIRNCOGN8pxwRI8@z>
2015-07-13 3:23 ` [3/3] " Michael Ellerman
2015-07-13 18:35 ` Bjorn Helgaas
2015-07-16 4:12 ` Michael Ellerman
[not found] ` <20150713071442.QXzbRfa3uYKKOTRlIbXP6BUoTWzN7o1J876ux2kMbgo@z>
2015-07-13 7:14 ` [PATCH 3/3] " Geert Uytterhoeven
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=alpine.DEB.2.11.1507171558010.18576@nanos \
--to=tglx@linutronix.de \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=bhelgaas@google.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-am33-list@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=x86@kernel.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