From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: kernel mode setting Date: Wed, 10 Feb 2010 16:00:47 -0500 Message-ID: <20100210210047.GC21068@phenom.dumpdata.com> References: <20100210151544.GI2861@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Michael D Labriola Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org On Wed, Feb 10, 2010 at 10:45:52AM -0500, Michael D Labriola wrote: > Well, here's what I've done so far. In a fit of rage aimed towards the > lameness of the nv driver, I cherry-picked all the drm commits from the > official nouveau git tree into my xen/master checkout. And it semi-works. > Baremetal it looks good for a few minutes then X gets corrupted. Under > Xen 3.4.2, X locks up before anything is even painted to the screen. If I > force the xorg nouveau driver to use software rendering, my system appears > to be perfectly stable with good 2d support. My compiled upstream nouveau > tree works perfectly (although the hardware acceleration is slow). > > Now, it was late at night and I was bleary eyed... and that's a TON of > commits to get merged in a code base I've never looked at before... and I > GUESSED at which commits to apply... so I'm encouraged that anything > worked at all. :-) > > Now I'm trying to decide if the X lockup under Xen is my fault (mangled a > merge conflict, missed a commit, etc), or whether something in the 3.4.2 > hypervisor in just plain incompatible with KMS DRM drivers. I suppose I > can try getting a Xen 4.0-rc build installed and see if the behavior > changes... > > And there's also the potential to try getting it to work under xen/next... > although I'm not so sure that that would be wise at this point. It does not have the backends in yet, so you can't launch guests yet :-(