From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Michael D Labriola <mlabriol@gdeb.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: kernel mode setting
Date: Wed, 10 Feb 2010 16:00:47 -0500 [thread overview]
Message-ID: <20100210210047.GC21068@phenom.dumpdata.com> (raw)
In-Reply-To: <OF234EAB5D.9199AC80-ON852576C6.00547D95-852576C6.005698F1@gdeb.com>
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 :-(
prev parent reply other threads:[~2010-02-10 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 14:53 kernel mode setting Michael D Labriola
2010-02-10 15:15 ` Pasi Kärkkäinen
2010-02-10 15:45 ` Michael D Labriola
2010-02-10 21:00 ` Konrad Rzeszutek Wilk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100210210047.GC21068@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=mlabriol@gdeb.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).