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 08:28:18 -0700
Message-ID: <29b32d341003180828j3b606b2bh8267a6cadd889240@mail.gmail.com>
References: <1268660645.10129.25070.camel@zakaz.uk.xensource.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>
	<20100318143906.GH14445@phenom.dumpdata.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1545124092=="
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20100318143906.GH14445@phenom.dumpdata.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: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Ian Campbell <Ian.Campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

--===============1545124092==
Content-Type: multipart/alternative; boundary=000e0cd107be5f75ba048214e1f5

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

Thanks Ian for clarification on interrupt handling mechanism.

Thanks Konrad. Should I use xen/next in dom0 or domU?

Thanks

On Thu, Mar 18, 2010 at 7:39 AM, Konrad Rzeszutek Wilk <
konrad.wilk@oracle.com> wrote:

> > > 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.
>
> Oh yeah. That got fixed in the xen/next (or rather in the
> pv/pcifront-2.6.32 branch and pv/pciback-2.6.32).
>
> It should work with the newer kernel (xen/next from Jeremy's PV-OPS git
> tree).
>

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

Thanks Ian for clarification on interrupt handling mechanism.<br><br>Thanks=
 Konrad. Should I use xen/next in dom0 or domU?<br><br>Thanks<br><br><div c=
lass=3D"gmail_quote">On Thu, Mar 18, 2010 at 7:39 AM, Konrad Rzeszutek Wilk=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:konrad.wilk@oracle.com">konrad.wil=
k@oracle.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=3D"im"=
>&gt; &gt; Yes my nic device is sharing interrupts(IRQ17) with usb and ide<=
br>

&gt; &gt; devices in dom0.<br>
&gt;<br>
&gt; This may be your problem, I don&#39;t know if this is expected to work=
 or<br>
&gt; not.<br>
<br>
</div>Oh yeah. That got fixed in the xen/next (or rather in the<br>
pv/pcifront-2.6.32 branch and pv/pciback-2.6.32).<br>
<br>
It should work with the newer kernel (xen/next from Jeremy&#39;s PV-OPS git=
<br>
tree).<br>
</blockquote></div><br>

--000e0cd107be5f75ba048214e1f5--


--===============1545124092==
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

--===============1545124092==--