WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH][HVM] fix PCI interrupt routing via ACPI

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][HVM] fix PCI interrupt routing via ACPI
From: "Dave Lively" <dave.lively@xxxxxxxxx>
Date: Tue, 17 Oct 2006 09:26:47 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Wang, Winston L" <winston.l.wang@xxxxxxxxx>
Delivery-date: Tue, 17 Oct 2006 06:27:22 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QrlDBPDamNovCk1g4bFF3TGqWtwMQ+mOd1kt2S5f/Z3scFupsbEMuHGoDUtW03iHNnty/7gsAUHAxD6h22UknmOqUurA9VNRrV2XsJui7fYEW4kG+rSSKV1iuzNpvE/2LOu7g7wwtz//jNwiANf2twvM8eWTTFsB/WNzJLA15nw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C15968E1.294C%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1b64e7ec0610160751u67d2f00as767087f789b0fcc0@xxxxxxxxxxxxxx> <C15968E1.294C%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 10/16/06, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:

 On 16/10/06 15:51, "Dave Lively" <dave.lively@xxxxxxxxx> wrote:


What about PIC mode support?  OSes expecting just a PIC may
 rely on being able to choose the 4 PCI IRQs.  But I don't know
 this for sure.  In fact, I remember Win2003 with the ACPI PIC HAL
 was successfully working around this problem (by leaving the PCI
 IRQ assignments unchanged), though it complained in the event
 log.  I'm not sure whether we can rely on this or not ...

 I think it's unlikely they'd rely on it. If we don't care about the PIC-mode 
limitation
we could keep the PIIX3 emulation

Are you proposing we use the (current) PIIX3 interrupt routing emulation for
PIC mode guests, and simply hide the interrupt routing functionality for APIC
mode?  That would certainly address my concerns about PIC mode (but note
neither of us is convinced my concerns here are legitimate).

(but I'm not sure that most OSes would bother to switch to APIC mode if they 
have only

Mostly I see SMP kernels using it on uniprocessor configs.

one processor). But bothering to try to emulate better PCI-ISA bridge hardware 
feels like
wasted effort if we can sidestep the entire problem.

I'm all for sidestepping the problem when that works.  But I worry
that the requirement
of supporting PIC mode means we need this general functionality (i.e.,
PCI interrupt
routing) anyway.  Since there will be no performance advantage in
hiding this functionality
in APIC mode, perhaps we're better off just leaving it there.

Dave

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel