From: Shu Ming <shuming@linux.vnet.ibm.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] IRQ number, interrupt number, interrupt line & GPIO[in/out]
Date: Sun, 11 Mar 2012 23:04:45 +0800 [thread overview]
Message-ID: <4F5CBF0D.3080803@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAEH94LhPcVzoqqfNwMe0MUg7dR7s74ZkthF4W2UVCKS0qys9dg@mail.gmail.com>
IRQ number is actually a word coming from ancient time. When 8259 was
popular at that time, we only have 0 ~ 15 interrupts when two 8259 are
cascaded. The IRQ number mattered in that time, because 8259 put their
vector number in the bus for CPU after the interrupt was delivered. The
number did have special meaning to the CPU used as a vector to interrupt
table. However, in modern time, especially after we have APIC and MSI,
the number don't have much meaning to CPU because the interrupt is
targeting some special PCI address to notify the CPU. So APIC don't
need put a vector number in the bus. In modern os, it is usually called
auto vector for OS to walk the interrupt routine table. Interrupt line
is similar to IRQ numbers, interrupt numbers.
On 2012-3-2 20:38, Zhi Yong Wu wrote:
> HI,
>
> Can anyone explain their relationship and difference among them? It
> is very appreciated if you can make some comments. thanks.
>
--
Shu Ming<shuming@linux.vnet.ibm.com>
IBM China Systems and Technology Laboratory
prev parent reply other threads:[~2012-03-11 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 12:38 [Qemu-devel] IRQ number, interrupt number, interrupt line & GPIO[in/out] Zhi Yong Wu
2012-03-02 15:12 ` 陳韋任
2012-03-03 2:10 ` Zhi Yong Wu
2012-03-03 17:12 ` Peter Maydell
2012-03-04 3:30 ` Zhi Yong Wu
2012-03-02 16:01 ` Anthony Liguori
2012-03-02 16:41 ` Peter Maydell
2012-03-03 2:19 ` Zhi Yong Wu
2012-03-03 2:06 ` Zhi Yong Wu
2012-03-11 15:04 ` Shu Ming [this message]
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=4F5CBF0D.3080803@linux.vnet.ibm.com \
--to=shuming@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=zwu.kernel@gmail.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 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).