From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: xen.git branch reorg / crash with 2.6.30-rc3 pv_ops dom0 Date: Fri, 01 May 2009 11:35:19 -0700 Message-ID: <49FB40E7.80009@goop.org> References: <49F0B42E.2040904@goop.org> <20090425115404.GZ24960@edu.joroinen.fi> <49F6086D.1020602@goop.org> <20090427193835.GF24960@edu.joroinen.fi> <1240931113.22119.11.camel@zakaz.uk.xensource.com> <49F72DF7.8020904@goop.org> <1240939020.22119.15.camel@zakaz.uk.xensource.com> <49F73D18.60300@goop.org> <1240989350.17173.2096.camel@localhost.localdomain> <49F87F74.7050205@goop.org> <20090501095811.GM24960@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: <20090501095811.GM24960@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: Ian Campbell , Xen-devel List-Id: xen-devel@lists.xenproject.org Pasi K=E4rkk=E4inen wrote: > On Wed, Apr 29, 2009 at 09:25:24AM -0700, Jeremy Fitzhardinge wrote: > =20 >>> There was some unification work in this area around the >>> beginning of March although I'm pretty such I've had it work much mor= e >>> recently. (I guess it might not have been merged into a visible branc= h >>> until more recently, it's a bit hard to tell with git but I don't thi= nk >>> that's what happened). >>> =20 >> Yeah, I think it has been working properly for some since then, though= I=20 >> think Pasi has been reporting problems since 32-bit dom0 first booted. >> >> =20 > > Yep, I've had problems from the beginning..=20 > > dom0/hackery was working pretty OK for me before it was removed..=20 > I could run and install new PV guests etc. > =20 Sorry, perhaps I was too hasty in removing the branches. Though you=20 still have references in your own git tree? You still had problems with HIGHPTE in hackery? My suspicion is that=20 we're seeing the same bug manifesting in a much more obvious way, since=20 I'm seeing somewhat similar symptoms, even without HIGHPTE. >> I also realized that my Xen doesn't have debug=3Dy set, so I'm probabl= y=20 >> missing some information. >> >> =20 > > Hmm, good point. I don't have debug=3Dy either..=20 > =20 That would be useful. It would be interesting to see if Xen complains=20 about any stray pte writes. J