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

To: "Neil Turton" <nturton@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 6/6] Add MSI support to XEN
From: "Haitao Shan" <maillists.shan@xxxxxxxxx>
Date: Wed, 14 May 2008 23:49:54 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Shan, Haitao" <haitao.shan@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Delivery-date: Wed, 14 May 2008 08:50:15 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=fbb09oRZpmcRl2eqbbEmiB8ZheBhfpH0yDSRzlvLwAo=; b=lRhvzrlQnueM+JkmLzEB2i3fyneddC2ZQ3nmWASVBoMN04NGES2ugtCckqV8AU/zJ7CYev8/b0e8JvLIC/+pjUoFuNeFrYiRiM8SEMW2pX1/+JhBNCsfiAaVmRJgOT52u+Z8h8AtnW1NAbn4Le2upDN6bFDVMAJcVnZ4soif6t0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bsSP+Jrg1tYLpsz/WLLq0GdEfqS0k2szpH5XHeMJ/aDqHhGc25fntK9xV61wkVjLwY0bqI3VtZvULpCg8nskUxR8RGZGy5hRanhZDh8qzy2gLtX5HBz3QxGFKganpKHEr/6Lf1heSHfqLjAMRiSSVgFIEyoWizOpK4PPfs6l9uM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <482AEAC8.9080103@xxxxxxxxxxxxxx>
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: <823A93EED437D048963A3697DB0E35DE014F156F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <48296609.8060603@xxxxxxxxxxxxxx> <481ad8630805130652v2f921287qc851edf3fa314477@xxxxxxxxxxxxxx> <482AEAC8.9080103@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
2008/5/14 Neil Turton <nturton@xxxxxxxxxxxxxx>:
> Haitao Shan wrote:
>> Can you tell me how to reproduce your problem? Maybe there are some
>> pathes that I do not take care of. So that I can fix the problem.
>
> I've fixed it now, thanks.
OK. I see your patch. It is my fault to make such a mistake.

>
>> Do you mean your MSI-X capable NIC is owned simultaneously by multi
>> guests?
>
> Exactly.  Do I just call request_irq in the frontend?
I do not quite understand.
What I mean is call PHYSDEVOP_map_pirq with proper domain_id ( the
domain you want Xen to deliver this specific MSI to) in pci backend
and tell frontend the pirq number . Then request_irq in the frontend.
I think this should work if you want to deliver that MSI to some
specific domain.

>
> Cheers, Neil.
>

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