From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [PATCH] compilation fixes for i460 with 2.5.1[5-7] kernels
Date: Fri, 24 May 2002 18:00:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905596@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905594@msgid-missing>
>>>>> On Fri, 24 May 2002 15:26:34 +1000, Peter Chubb <peter@chubb.wattle.id.au> said:
Peter> Since 2.5.15, a few interfaces are no longer exported from
Peter> filemap.c --- which means the code for getting and releasing
Peter> locked pages in files .../agp/agpgart_be.c, .../drm/radeon.c,
Peter> and .../drm/r128_cce.c has to be changed.
Peter> Question: Is it *really* necessary to lock these pages? As
Peter> they're grabbed from the freepage list, they're not backed by
Peter> a file, so noone else will ever try to get the page. (Or
Peter> have I misunderstood completely what's going on here?) So
Peter> what's it locking against?
I believe the locking is bogus. I'm no AGP expert, but my
understanding is that what's going on there is that the agp code is
allocating an scatter/gather table which is accessed by the GART
("AGP's DMA engine"). This table can be mapped into user level. I
suspect the intent of the original code was to prevent swap-outs
etc. on those pages. However, that's already taken care of by the
vm-area which is used to map the memory into user level: it has the
VM_RESERVED flag set (see drm_vm.h).
BTW: I'm finally back to working on the 2.5 tree. I hope to have a
(preliminary) 2.5.17 patch sometime today.
--david
prev parent reply other threads:[~2002-05-24 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 5:26 [Linux-ia64] [PATCH] compilation fixes for i460 with 2.5.1[5-7] kernels Peter Chubb
2002-05-24 18:00 ` David Mosberger [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=marc-linux-ia64-105590701905596@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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