From: Terence Ripperda <tripperda@nvidia.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.15-rc4
Date: Thu, 1 Dec 2005 15:11:19 -0600 [thread overview]
Message-ID: <20051201211119.GA11437@hygelac> (raw)
In-Reply-To: <20051201121826.GF19694@charite.de>
On Thu, Dec 01, 2005 at 01:18:27PM +0100, Ralf.Hildebrandt@charite.de wrote:
> * Linus Torvalds <torvalds@osdl.org>:
>
> > [ Btw, some drivers will now complain loudly about their nasty mis-use of
> > page remapping, and that migh look scary, but it should all be good, and
> > we'd love to see the detailed output of dmesg on such machines. ]
>
> Here's one - smite me for using the nvidia driver:
>
> Xorg does an incomplete pfn remapping [<c013eb8c>] incomplete_pfn_remap+0x6b/0xca
> [<f94fc956>] nv_kern_mmap+0x47d/0x4cb [nvidia]
> [<c01415e1>] do_mmap_pgoff+0x3cf/0x6ee
> [<c0107dea>] sys_mmap2+0x66/0xaf
> [<c0102c25>] syscall_call+0x7/0xb
from looking at the new code, it looks like this is due to how we mmap
our dma pages. due to opengl using large (multiple megabyte) push
buffers, we allocate individual physically discontiguous pages, then
mmap them in one call. we end up iterating over all of the pages with
individual calls to remap_pfn_range.
it appears this new warning doesn't like that and will complain,
unless VM_INCOMPLETE is set. when, if ever, is it valid to set
VM_INCOMPLETE? I'm guessing that the answer is to rely on the nopage
handler to map these pages individually. but I'm not clear how
dropping back and forth between user/kernel mode for each page between
each call to remap_pfn_page would be more efficient than just calling
remap_pfn_page for each page while we're already in kernel space.
Thanks,
Terence
>
> repeated 4 times.
>
> --
> Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt@charite.de
> Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155
> Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962
> IT-Zentrum Standort CBF send no mail to spamtrap@charite.de
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2005-12-01 21:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 6:40 Linux 2.6.15-rc4 Linus Torvalds
2005-12-01 12:18 ` Ralf Hildebrandt
2005-12-01 21:11 ` Terence Ripperda [this message]
2005-12-01 23:11 ` Linus Torvalds
2005-12-02 18:02 ` Terence Ripperda
2005-12-03 0:22 ` Greg KH
[not found] ` <6f6293f10512031726n10ea87e6s44be5dffbd512bb5@mail.gmail.com>
2005-12-04 1:34 ` Linus Torvalds
2005-12-01 14:05 ` Kasper Sandberg
2005-12-01 16:05 ` Linus Torvalds
2005-12-01 18:57 ` Kasper Sandberg
2005-12-01 19:04 ` Linus Torvalds
2005-12-01 22:57 ` Kasper Sandberg
[not found] ` <6f6293f10512011112m6e50fe0ejf0aa5ba9d09dca1e@mail.gmail.com>
2005-12-01 19:34 ` Linus Torvalds
2005-12-01 21:41 ` Eyal Lebedinsky
2005-12-01 21:53 ` Linus Torvalds
2005-12-01 23:37 ` Grant Coady
2005-12-02 11:45 ` Mauro Carvalho Chehab
2005-12-02 17:41 ` Grant Coady
2005-12-02 17:48 ` Michael Krufky
2005-12-02 19:37 ` Pauline Middelink
2005-12-02 20:19 ` Grant Coady
2005-12-02 20:32 ` Richard Mittendorfer
2005-12-04 15:50 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-12-04 3:00 Paul Blazejowski
2005-12-04 14:12 Subodh Shrivastava
2005-12-05 15:51 ` Mark Lord
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=20051201211119.GA11437@hygelac \
--to=tripperda@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
/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