From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ritu kaur <ritu.kaur.us@gmail.com>
Subject: Re: domU guest for xcp 0.1.1
Date: Thu, 18 Mar 2010 07:23:48 -0700
Message-ID: <29b32d341003180723l652adb4bvb3b3aba3d8f3a529@mail.gmail.com>
References: <29b32d341003141329v3c6a73c0y8030cf3c6736634c@mail.gmail.com>
	<29b32d341003150646o4d215dfel1c2a2bc6d287edc@mail.gmail.com>
	<29b32d341003151904m2a992be5s74697d6047b864c6@mail.gmail.com>
	<1268725069.8652.4179.camel@localhost.localdomain>
	<20100316152259.GO1878@reaktio.net>
	<29b32d341003161625w2969f2daib3408561920793d3@mail.gmail.com>
	<29b32d341003171144k628a7741x17b6658731f96e4b@mail.gmail.com>
	<1268903824.10129.38718.camel@zakaz.uk.xensource.com>
	<29b32d341003180643o326f7f43h97c25bd104f3b658@mail.gmail.com>
	<1268921503.10129.39640.camel@zakaz.uk.xensource.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1213365512=="
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1268921503.10129.39640.camel@zakaz.uk.xensource.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: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

--===============1213365512==
Content-Type: multipart/alternative; boundary=000e0cd0ea86bc1cbe048213fa9e

--000e0cd0ea86bc1cbe048213fa9e
Content-Type: text/plain; charset=ISO-8859-1

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@citrix.com>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.
>
>
>

--000e0cd0ea86bc1cbe048213fa9e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

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 pc=
ifront i.e InterruptDescTable-&gt;Hypervisor-&gt;pciback-&gt;pcifront-&gt;a=
ctual_device is this correct?<br>
<br>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 tr=
y with another nic device or someother device?<br><br>Thanks<br><br><br>
<div class=3D"gmail_quote">On Thu, Mar 18, 2010 at 7:11 AM, Ian Campbell <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:Ian.Campbell@citrix.com">Ian.Campbell=
@citrix.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); =
padding-left: 1ex;">
<div class=3D"im">On Thu, 2010-03-18 at 13:43 +0000, Ritu kaur wrote:<br>
&gt; Hi Ian.<br>
&gt;<br>
&gt; =A0pcifront_handler_aer is the callback function.<br>
<br>
</div>This is not the same interrupt/evtchn as your device&#39;s interrupt =
though.<br>
This is the PCI error handling notification interrupt (PCI AER is PCI<br>
Advanced Error Reporting).<br>
<br>
[...]<br>
<div class=3D"im"><br>
&gt; Yes my nic device is sharing interrupts(IRQ17) with usb and ide<br>
&gt; devices in dom0.<br>
<br>
</div>This may be your problem, I don&#39;t know if this is expected to wor=
k or<br>
not.<br>
<br>
You could experiment with another device which doesn&#39;t share an<br>
interrupt, just to check that the basic mechanism is working.<br>
<font color=3D"#888888"><br>
Ian.<br>
<br>
<br>
</font></blockquote></div><br>

--000e0cd0ea86bc1cbe048213fa9e--


--===============1213365512==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1213365512==--