From: Beth Kon <eak@us.ibm.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Add code to override IRQ 0 to INTI 2
Date: Mon, 27 Oct 2008 19:02:08 -0400 [thread overview]
Message-ID: <1225148528.7555.89.camel@beth-laptop> (raw)
In-Reply-To: <49061C1A.1030008@codemonkey.ws>
On Mon, 2008-10-27 at 14:52 -0500, Anthony Liguori wrote:
> Avi Kivity wrote:
> > Beth Kon wrote:
> >> This patch, provided by Anthony Liguori, maps IRQ0 to INTI2.
> >>
> >>
> >
> > This will cause problems for kvm, which maps interrupts 1:1 without
> > exceptions. While we could add support for remapping, it would mean
> > that older kernels would not be able to support an hpet.
> >
> > Isn't it possible to connect the hpet to pic irq 2 and ioapic irq 2,
> > maintaining the 1:1 mapping?
>
> The APIC spec says that the hpet must be connected to APIC IRQ 0 and
> IOAPIC IRQ 2. I don't understand GSI very well, but I think this is the
> normally remapping of interrupts that would occur as opposed to
> something device specific.
>
Just a slight clarification to Anthony's words in order to avoid
confusion... The HPET spec says that the hpet, when replacing the PIT in
legacy mode must map to PIC IRQ 0 and APIC IRQ2.
> Regards,
>
> Anthony Liguori
>
> > (what's irq 2 connected to now?)
> >
>
--
Elizabeth Kon (Beth)
IBM Linux Technology Center
Open Hypervisor Team
email: eak@us.ibm.com
next prev parent reply other threads:[~2008-10-27 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 18:26 [Qemu-devel] [PATCH 2/2] Add code to override IRQ 0 to INTI 2 Beth Kon
2008-10-27 19:48 ` Avi Kivity
2008-10-27 19:52 ` Anthony Liguori
2008-10-27 23:02 ` Beth Kon [this message]
2008-10-28 12:47 ` Avi Kivity
2008-10-27 20:02 ` Avi Kivity
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=1225148528.7555.89.camel@beth-laptop \
--to=eak@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.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).