From: Avi Kivity <avi@redhat.com>
To: eak@us.ibm.com
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 21:48:59 +0200 [thread overview]
Message-ID: <49061B2B.702@redhat.com> (raw)
In-Reply-To: <1225131960.7555.79.camel@beth-laptop>
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?
(what's irq 2 connected to now?)
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-10-27 19:49 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 [this message]
2008-10-27 19:52 ` Anthony Liguori
2008-10-27 23:02 ` Beth Kon
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=49061B2B.702@redhat.com \
--to=avi@redhat.com \
--cc=eak@us.ibm.com \
--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).