From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Maa3b-0006h5-0K
	for qemu-devel@nongnu.org; Mon, 10 Aug 2009 14:57:19 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Maa3W-0006fD-9a
	for qemu-devel@nongnu.org; Mon, 10 Aug 2009 14:57:18 -0400
Received: from [199.232.76.173] (port=47277 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Maa3W-0006f8-1x
	for qemu-devel@nongnu.org; Mon, 10 Aug 2009 14:57:14 -0400
Received: from mail-qy0-f174.google.com ([209.85.221.174]:44243)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1Maa3V-0006Z6-NI
	for qemu-devel@nongnu.org; Mon, 10 Aug 2009 14:57:13 -0400
Received: by qyk4 with SMTP id 4so2676329qyk.4
	for <qemu-devel@nongnu.org>; Mon, 10 Aug 2009 11:57:12 -0700 (PDT)
Message-ID: <4A806D86.8090208@codemonkey.ws>
Date: Mon, 10 Aug 2009 13:57:10 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] qemu_reserve_isa_irq()
References: <4A7ADE70.7060204@sgi.com>
In-Reply-To: <4A7ADE70.7060204@sgi.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Jes Sorensen <jes@sgi.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel <qemu-devel@nongnu.org>, Gleb Natapov <gleb@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>

Jes Sorensen wrote:
> Hi
>
> As part of trying to provide the BIOS with information about PCI
> interrupt availability, I have added qemu_reserve_isa_irq() to try
> and keep track of which IRQs are claimed for ISA.
>
> If we can agree on this approach, then I'll be using it to pass info
> on to the guest BIOS in a follow on patch.

Given the new isa qdev support, maybe it would be better to hook into 
isa_connect_irq?

> Thanks,
> Jes
>

Regards,

Anthony Liguori