public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: <linux-kernel@vger.kernel.org>, <discuss@x86-64.org>
Subject: [i386, x86-64] ioapic_register_intr() and assign_irq_vector() questions
Date: Thu, 13 Apr 2006 15:50:39 +0200	[thread overview]
Message-ID: <443E734F.76E4.0078.0@novell.com> (raw)

Since ioapic_register_intr() ties, for the PCI case, the interrupt gate for vector to interrupt[vector], doesn't this,
since do_IRQ() derives the IRQ from the value loaded in the handler at that address (which is the value of vector), mean
that here irq == vector in all cases? If so, why does this function need an if/else (the 'else' case would then be good
for both cases)?

Looking at the call paths assign_irq_vector() can get called from, I would think this function, namely as it's using
static variables, lacks synchronization - is there any (hidden) reason this is not needed here?

Thanks, Jan

             reply	other threads:[~2006-04-13 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13 13:50 Jan Beulich [this message]
2006-04-13 17:11 ` [i386, x86-64] ioapic_register_intr() and assign_irq_vector() questions Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2006-04-14 17:16 Jan Beulich

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=443E734F.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.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