From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Arvind R <arvino55@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Code Trace] dom0 Nouveau accelerated mmap problem
Date: Mon, 1 Mar 2010 11:55:52 -0500 [thread overview]
Message-ID: <20100301165552.GH7881@phenom.dumpdata.com> (raw)
In-Reply-To: <d799c4761002272331q38df6ba0k4472eca57cbe8a9b@mail.gmail.com>
On Sun, Feb 28, 2010 at 01:01:16PM +0530, Arvind R wrote:
> Hi,
> In continuation of my 'Nouveau on dom0' posting, I dug into the code ...
> As Konrad had predicted, it is the discontinuous PFN in the mmapped
> area that seems to the problem.
<groan>
I had hoped it would not be...
So the is_iomem flag is set to zero, right? If that is the case, did
this patch:
http://lists.xensource.com/archives/html/xen-devel/2009-10/msg00986.html
help in any regard? And if it did, what did your ttm_bo_vm_fault start
spitting out?
prev parent reply other threads:[~2010-03-01 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 7:31 [Code Trace] dom0 Nouveau accelerated mmap problem Arvind R
2010-03-01 16:55 ` 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=20100301165552.GH7881@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=arvino55@gmail.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).