From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: Arvind R <arvino55@gmail.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com,
Joanna Rutkowska <joanna@invisiblethingslab.com>,
Michael D Labriola <mlabriol@gdeb.com>,
xen-devel-bounces@lists.xensource.com
Subject: Re: Re: [Patch RFC] ttm: nouveau accelerated on Xen pv-ops kernel
Date: Thu, 24 Jun 2010 17:00:29 -0400 [thread overview]
Message-ID: <20100624210029.GA3602@phenom.dumpdata.com> (raw)
In-Reply-To: <20100624195554.GC17817@reaktio.net>
On Thu, Jun 24, 2010 at 10:55:54PM +0300, Pasi Kärkkäinen wrote:
> On Wed, Jun 23, 2010 at 08:54:30AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Wed, Jun 23, 2010 at 12:32:57AM +0200, Joanna Rutkowska wrote:
> > > On 06/17/10 19:51, Konrad Rzeszutek Wilk wrote:
> > > >>> And my X log ends abruptly after this line:
> > > >>> (II) NOUVEAU(0): Opened GPU Channel 1
> > > >>
> > > >>
> > > >> So, I've spent the last two weeks trying to get this to work.
> > > >>
> > > > ..
> > > >> other ones too (hadn't tested yet). However, I am still failing at the same
> > > >> spot as Michael: the dreaded Opened GPU Channel 1...
> > > >
> > > > Fixed! Plus I've tested it on:
> > > >
> > > > GeForce 1 256
> > > > GeForce 3 NV20
> > > > GeForce 4 Ti 4200
> > > > GeForce 8600 GT
> > > > ICH5 82865G
> > > > ICH7 82G33/G31G
> > > > ICH8 82Q963/Q965
> > > > Matrox G450
> > > > Radeon ES1000
> > > > Radeon HD 3200
> > > > Radeon R100 QD (7200)
> > > > Radeon RV100QY (7000)
> > > > Radeon RV710 [Radeon HD 4350]
> > > > RIVA TNT2 Pro
> > > >
> > > > Details on: http://wiki.xensource.com/xenwiki/XenPVOPSDRM
> > > > There are two bugs that are creeping up. One of the can be disabled by
> > > > 'nopat' on the command line. The other, well the other is only seen
> > > > during shutdown.
> > > >
> > > >>
> > > >> Anyhow.. if you want the patches:
> > > >>
> > > >> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/kms-fixes
> > > >
> > > > I rebased the branch and it is now devel/kms.fixes-0.3
> > > >
> > > Which stable branch have you rebased it for (.31, .32, .33?)?
> >
> > .32.
> >
>
> Hey,
>
> I just tried devel/kms.fixes-0.3:
>
> [root@f13 linux-2.6-xen]# git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen
> ..
>
> [root@f13 linux-2.6-xen]# cd linux-2.6-xen/
> [root@f13 linux-2.6-xen]# git checkout -b xen/stable-2.6.32.x origin/xen/stable-2.6.32.x
> [root@f13 linux-2.6-xen]# git pull
>
> [root@f13 linux-2.6-xen]# git remote add -f konrad git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> [root@f13 linux-2.6-xen]# git pull
> Already up-to-date.
>
> [root@f13 linux-2.6-xen]# git merge konrad/devel/kms.fixes-0.3
> Auto-merging drivers/char/agp/intel-agp.c
> Auto-merging drivers/gpu/drm/ttm/ttm_bo_vm.c
> CONFLICT (content): Merge conflict in drivers/gpu/drm/ttm/ttm_bo_vm.c
> Auto-merging drivers/gpu/drm/ttm/ttm_tt.c
> Automatic merge failed; fix conflicts and then commit the result.
>
>
> Does it merge ok for you with xen/stable-2.6.32.x?
No. I get the same. The fault is that my patches assumes a bit different
tree. What you need is to fixup to this:
vma->vm_private_data = bo;
- vma->vm_flags |= VM_RESERVED | VM_IO | VM_MIXEDMAP | VM_DONTEXPAND;
+ vma->vm_flags |= VM_RESERVED | VM_MIXEDMAP | VM_DONTEXPAND;
+ man = &bdev->man[bo->mem.mem_type];
+ if (man->flags & TTM_MEMTYPE_FLAG_NEEDS_IOREMAP)
+ vma->vm_flags |= VM_IO;
vma->vm_page_prot = vm_get_page_prot(vma->vm_flags);
return 0;
next prev parent reply other threads:[~2010-06-24 21:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 13:21 [Patch RFC] nouveau accelerated on Xen pv-ops kernel Arvind R
[not found] ` <d799c4761003100521h663c82eepda85f3f0309828c2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-11 11:02 ` [Patch RFC] ttm: " Pekka Paalanen
2010-03-12 5:27 ` Arvind R
2010-03-28 10:20 ` Joanna Rutkowska
2010-03-30 5:50 ` Arvind R
2010-03-12 12:45 ` Arvind R
2010-03-12 13:20 ` Michael D Labriola
2010-03-13 22:03 ` Joanna Rutkowska
2010-03-15 14:44 ` Michael D Labriola
2010-03-15 23:13 ` Jeremy Fitzhardinge
2010-03-16 7:18 ` Arvind R
2010-03-16 16:48 ` Michael D Labriola
2010-03-16 16:40 ` Michael D Labriola
2010-03-16 17:21 ` Konrad Rzeszutek Wilk
2010-03-16 19:39 ` Michael D Labriola
2010-03-16 19:41 ` Konrad Rzeszutek Wilk
2010-03-17 1:01 ` Konrad Rzeszutek Wilk
2010-03-18 6:09 ` Arvind R
2010-03-19 15:29 ` Michael D Labriola
2010-03-20 6:01 ` Arvind R
2010-03-22 21:14 ` Michael D Labriola
2010-03-23 6:21 ` Arvind R
2010-03-23 12:45 ` Michael D Labriola
2010-03-23 13:27 ` Michael D Labriola
2010-03-25 7:05 ` Arvind R
2010-03-25 7:18 ` Jeremy Fitzhardinge
2010-03-29 14:42 ` Michael D Labriola
2010-06-09 17:43 ` Konrad Rzeszutek Wilk
2010-06-09 18:39 ` Pasi Kärkkäinen
2010-06-09 19:31 ` Konrad Rzeszutek Wilk
2010-06-17 17:51 ` Konrad Rzeszutek Wilk
2010-06-22 22:32 ` Joanna Rutkowska
2010-06-23 12:54 ` Konrad Rzeszutek Wilk
2010-06-23 13:21 ` Joanna Rutkowska
2010-06-23 14:38 ` Konrad Rzeszutek Wilk
2010-06-23 15:08 ` Konrad Rzeszutek Wilk
2010-06-24 19:55 ` Pasi Kärkkäinen
2010-06-24 21:00 ` Konrad Rzeszutek Wilk [this message]
[not found] ` <d799c4761003120445h57ab1373m31eb0add242ef74c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-03-16 13:25 ` Thomas Hellstrom
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=20100624210029.GA3602@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=arvino55@gmail.com \
--cc=jeremy@goop.org \
--cc=joanna@invisiblethingslab.com \
--cc=mlabriol@gdeb.com \
--cc=pasik@iki.fi \
--cc=xen-devel-bounces@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.