From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KuY9H-0005KM-Qb
	for qemu-devel@nongnu.org; Mon, 27 Oct 2008 15:53:11 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KuY9D-0005Je-OZ
	for qemu-devel@nongnu.org; Mon, 27 Oct 2008 15:53:11 -0400
Received: from [199.232.76.173] (port=39952 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KuY9D-0005Jb-KV
	for qemu-devel@nongnu.org; Mon, 27 Oct 2008 15:53:07 -0400
Received: from yw-out-1718.google.com ([74.125.46.158]:16979)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1KuY9D-00041I-0V
	for qemu-devel@nongnu.org; Mon, 27 Oct 2008 15:53:07 -0400
Received: by yw-out-1718.google.com with SMTP id 6so533553ywa.82
	for <qemu-devel@nongnu.org>; Mon, 27 Oct 2008 12:53:02 -0700 (PDT)
Message-ID: <49061C1A.1030008@codemonkey.ws>
Date: Mon, 27 Oct 2008 14:52:58 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 2/2] Add code to override IRQ 0 to INTI 2
References: <1225131960.7555.79.camel@beth-laptop> <49061B2B.702@redhat.com>
In-Reply-To: <49061B2B.702@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: eak@us.ibm.com

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.

Regards,

Anthony Liguori

> (what's irq 2 connected to now?)
>