From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: chasing the four level page table
Date: Sat, 15 Jan 2005 02:54:15 +0000 (UTC) [thread overview]
Message-ID: <csa0kn$4eg$1@terminus.zytor.com> (raw)
In-Reply-To: 9e47339105010721225c0cfb32@mail.gmail.com
Followup to: <9e47339105010721225c0cfb32@mail.gmail.com>
By author: Jon Smirl <jonsmirl@gmail.com>
In newsgroup: linux.dev.kernel
>
> On Thu, 6 Jan 2005 16:41:59 -0500, Dave Jones <davej@redhat.com> wrote:
> > No other device driver is also doing such lowlevel stuff with
> > page tables directly afaics. drivers/char/drm seem to be the only drivers
> > using [pgd|pmd|pte]_offset() routines.
>
> On 6 Jan 2005 20:38:27 +0100, Andi Kleen <ak@muc.de> wrote:
> > Perhaps we should add a get_user_phys() or somesuch for this.
>
> I think this is a case where the memory manager is missing a function
> that DRM needs. If there was a get_user_phys() function DRM wouldn't
> need to walk the page tables.
>
FWIW, the Nvidia device driver wrapper also has this issue.
There seems to be at least two classes of device drivers -- graphics
and RDMA -- which have a genuine need to DMA user pages, after
appropriate locking, of course.
At that point we're better off having the mm export the right
functionality to keep device driver authors from doing it wrong.
-hpa
next prev parent reply other threads:[~2005-01-15 2:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 17:17 chasing the four level page table Jon Smirl
2005-01-06 18:12 ` Andi Kleen
2005-01-06 18:36 ` Jon Smirl
2005-01-06 19:38 ` Andi Kleen
2005-01-06 20:05 ` Jon Smirl
2005-01-06 21:41 ` Dave Jones
2005-01-08 5:22 ` Jon Smirl
2005-01-15 2:54 ` H. Peter Anvin [this message]
2005-01-15 3:37 ` Roland Dreier
2005-01-15 4:24 ` Andi Kleen
2005-01-15 5:59 ` Jon Smirl
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='csa0kn$4eg$1@terminus.zytor.com' \
--to=hpa@zytor.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;
as well as URLs for NNTP newsgroup(s).