From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: irq_guest_eoi_timer interaction with MSI
Date: Thu, 13 Nov 2008 11:22:51 +0000
Message-ID: <C541BE8B.290AB%keir.fraser@eu.citrix.com>
References: <C541BD18.2905B%keir.fraser@eu.citrix.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C541BD18.2905B%keir.fraser@eu.citrix.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org


Oh yes, and indeed this could be stashed at the end of shared_info. We could
reserve another bitmap of, say, 1024 bits quite easily. Plenty of PIRQs!

 -- Keir

On 13/11/08 11:16, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:

> We already have PHYSDEVOP_eoi. We can force guests to always use that. It'll
> be no slower than level-triggered IO-APIC IRQs, which we've been using since
> forever with no complaints. And yeah, as an extension we could have a
> shared-memory pirq bitmap to indicate dynamically whether eoi is required.
> Quite a secondary concern though, I would say.