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 0/5] Add MSI support to XEN

To: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Espen Skoglund <espen.skoglund@xxxxxxxxxxxxx>, "Shan, Haitao" <haitao.shan@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/5] Add MSI support to XEN
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Mon, 31 Mar 2008 15:33:48 +0100
Cc: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Li, Xin B" <xin.b.li@xxxxxxxxx>
Delivery-date: Mon, 31 Mar 2008 07:35:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <391BF3CDD2DC0848B40ACB72FA97AD590323064B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciQMO1Y+dTIVbdxTuGacqzZj4GuywARL6KAAAvIwN8AALvKIAADJmsgAAB3TPAAn7fz4AABG9/OAABJeBAAAGRHOw==
Thread-topic: [Xen-devel] [PATCH 0/5] Add MSI support to XEN
User-agent: Microsoft-Entourage/11.4.0.080122
On 31/3/08 15:25, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:

>> So, if you leave the driver as it is (triggering the software LSC
>> interrupt), do APIC EOI in Xen before executing the interrupt
>> handler in
>> dom0, and do not mask the MSI at all, then you no longer hang?
> 
> I usuually do experiement in linux kernel, and it no longer hang.

Well, I'd be okay with an initial implementation which does not allow Xen to
mask MSIs. But still I think it will be cleaner and more extensible to have
Xen program the MSI registers anyway. This will hide details like interrupt
vector, APIC destination mode, etc. from the MSI-capable guest, and also
will make it easier to support things like changing interrupt affinity on
the fly (since it will not be necessary to get dom0 involved in that).

Once you have Xen able to write the MSI registers, I suppose it is not much
extra work to implement some kind of interrupt mitigation scheme involving
mask/enable bits of the MSI configuration register.

 -- Keir



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