From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Marc - A. Dahlhaus" Subject: Re: Xen with dom0 pvops on ultra-recent "git tip" kernel on x86_64 Date: Sat, 10 Jan 2009 21:49:09 +0100 Message-ID: <496909C5.2060403@wol.de> References: <1231615355.19576.23.camel@leto.intern.saout.de> <49690103.5020706@wol.de> <1231619339.5616.15.camel@leto.intern.saout.de> <20090110203706.GW15052@edu.joroinen.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20090110203706.GW15052@edu.joroinen.fi> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel , Christophe Saout List-Id: xen-devel@lists.xenproject.org Pasi K=E4rkk=E4inen schrieb: > On Sat, Jan 10, 2009 at 09:28:59PM +0100, Christophe Saout wrote: > =20 >> Hi Marc, >> >> =20 >>>> I am very excited to see that dom0 pvops is finally coming close to >>>> working, so I wanted to give it a try. >>>> >>>> >From the description it was not clear to me which kernel to chose a= s >>>> base for the patches.hg, so I took the latest (that was ~ 2 weeks ag= o) >>>> kernel on git.kernel.org I could find (post-2.6.28 git tip at that >>>> point). >>>> =20 >>>> =20 >>> Just follow the instructions on this wiki page: >>> >>> http://wiki.xensource.com/xenwiki/XenParavirtOps >>> >>> You could also search the Archives of xen-devel beginning around=20 >>> November 2008 for more >>> informations... >>> =20 >> Yes, I followed those instruction (or at least I believe I did). It i= s >> however not specific as to which kernel version from the "tip.git" to >> use as base for applying the patches. I mean, that is not really my >> problem, I got everything applied and have a compiling kernel. It just >> doesn't boot (or at least doesn't get as far as for instance Pasi and >> his experiments). >> >> =20 > > pv_ops dom0 patches are currently for 2.6.28-rc8.=20 > > I think and hope Jeremy will update them when he gets back from his vac= ation > next week.=20 > > =20 >> Actually, I am not really interested in getting a working kernel (I kn= ow >> that there are still some pieces missing), so this is purely academica= l >> and for testing. Since the patches are supposed to be merged soon (at >> least I got the impression that was the plan) I though I was going to >> join the testing effort. And at this point they are supposed to sort = of >> work on any bleeding edge kernel, right? So I took one. >> >> I could have gone back in the history and take something around >> 2.6.28-rc8 (which seemed to have worked for others), but then they wer= e >> using x86_32 and I am testing x86_64, if I see correctly. So my >> question was mostly if this had seen some testing at all, is supposed = to >> work, and if it is, did I miss something. In any case, this is the >> result of my testing. :-) >> >> =20 > > I think some people have been trying x86-64 too, with similar results t= han > me and others on x86-32. > =20 >> I also forward-ported a few things to the latest version a few hours >> ago, including some changes in xen-iommu.c to follow the dma_ops mergi= ng >> thing in the tip head. >> >> =20 > > Nice. > > I also just noticed there are some new patches in > http://xenbits.xen.org/paravirt_ops/patches.hg/ > > "Fixes for PAE swiotlb with Becky's patches." > > Maybe I should try and see if those make any difference. > =20 My testing included this changeset already. But it changed nothing on=20 the symptoms here, hope you get better results. Marc