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] domU guest for xcp 0.1.1

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject: Re: [Xen-devel] domU guest for xcp 0.1.1
From: Ritu kaur <ritu.kaur.us@xxxxxxxxx>
Date: Thu, 18 Mar 2010 07:23:48 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 18 Mar 2010 07:24:45 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=MDl+hgXluyTvezsO6XFSVLh3Eb+ZUJ1W8rgzyG/GmCQ=; b=MHN8w2STYShQHkHCYvt5UA8c0nonsVa6MrduOJIq3L9QZk1A0do/v1kdgCCqPXG7Wo KtW9l75zw6A4qyEbJxX0H3LHuKEaQ6QZ5Jamtum9ciKRXKyb7M3xmgqT2OULA9BTC/EH IZXjXukpfM3ERHgWMvxxajhq733SeIQC1NO1Y=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=f0E9ZhSXc+77RaHvV1xnEOV2CzY03Zh58V+tMzzJObJY5zUIjaqHeYPtJHM+RixcPo cHC1aWASR+dZ+hcMSMSTRykjZOj089LkKJg/EVsOUquKhwpPtSGwne6JNlHmVbdX41kr I8gpOU2EPirViaAj7zpSrPW/1eGikjje0rANA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1268921503.10129.39640.camel@xxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <29b32d341003141329v3c6a73c0y8030cf3c6736634c@xxxxxxxxxxxxxx> <29b32d341003150646o4d215dfel1c2a2bc6d287edc@xxxxxxxxxxxxxx> <29b32d341003151904m2a992be5s74697d6047b864c6@xxxxxxxxxxxxxx> <1268725069.8652.4179.camel@xxxxxxxxxxxxxxxxxxxxx> <20100316152259.GO1878@xxxxxxxxxxx> <29b32d341003161625w2969f2daib3408561920793d3@xxxxxxxxxxxxxx> <29b32d341003171144k628a7741x17b6658731f96e4b@xxxxxxxxxxxxxx> <1268903824.10129.38718.camel@xxxxxxxxxxxxxxxxxxxxxx> <29b32d341003180643o326f7f43h97c25bd104f3b658@xxxxxxxxxxxxxx> <1268921503.10129.39640.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thanks Ian, could you please clarify me how are interrupts handled for pci passthrough device. I thought it is delivered via evtchn from pciback to pcifront i.e InterruptDescTable->Hypervisor->pciback->pcifront->actual_device is this correct?

IRQ is 11 in dom0 for nic device but after driver for nic is loaded in domU IRQ is changed to 17. When you say try with another device should I try with another nic device or someother device?

Thanks


On Thu, Mar 18, 2010 at 7:11 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
On Thu, 2010-03-18 at 13:43 +0000, Ritu kaur wrote:
> Hi Ian.
>
>  pcifront_handler_aer is the callback function.

This is not the same interrupt/evtchn as your device's interrupt though.
This is the PCI error handling notification interrupt (PCI AER is PCI
Advanced Error Reporting).

[...]

> Yes my nic device is sharing interrupts(IRQ17) with usb and ide
> devices in dom0.

This may be your problem, I don't know if this is expected to work or
not.

You could experiment with another device which doesn't share an
interrupt, just to check that the basic mechanism is working.

Ian.



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