linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: "Thomas Hellström" <thomas@tungstengraphics.com>,
	linux-mm@kvack.org,
	"Linux Kernel list" <linux-kernel@vger.kernel.org>,
	"Hugh Dickins" <hugh@veritas.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Linus Torvalds" <torvalds@osdl.org>,
	"Nick Piggin" <npiggin@suse.de>
Subject: Re: User switchable HW mappings & cie
Date: Tue, 10 Oct 2006 07:03:49 +1000	[thread overview]
Message-ID: <1160427829.7752.21.camel@localhost.localdomain> (raw)
In-Reply-To: <200610092036.50010.ioe-lkml@rameria.de>

On Mon, 2006-10-09 at 20:36 +0200, Ingo Oeser wrote:
> Hi all,
> 
> On Monday, 9. October 2006 13:51, Benjamin Herrenschmidt wrote:
> > > One problem that occurs is that the rule for ptes with non-backing 
> > > struct pages
> > > Which I think was introduced in 2.6.16:
> > > 
> > >     pfn_of_page == vma->vm_pgoff + ((addr - vma->vm_start) >> PAGE_SHIFT)
> > > 
> > > cannot be honored, at least not with the DRM memory manager, since the 
> > > graphics object will be associated with a vma and not the underlying 
> > > physical address. User space will have vma->vm_pgoff as a handle to the 
> > > object, which may move around in graphics memory.
> > 
> > That's a problem with VM_PFNMAP set indeed. get_user_pages() is a
> > non-issue with VM_IO set too but I'm not sure about other code path that
> > might try to hit here... though I think we don't hit that if MAP_SHARED,
> > Nick ?
> 
> Istn't this just a non-linear PFN mapping, you are describing here?
> 
> Nick: 
> 	Cant your new fault consolidation code handle that?
> 	AFAICS your new .fault handler just gets the
> 	vma and pgoff and install the matching PTE via install_THINGIE()
> 	or vm_insert_THINGIE()
> 
> Or do I miss sth. here?

It is somewhat yes.

Ben.


--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-10-09 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-08 22:37 Benjamin Herrenschmidt
2006-10-09 11:43 ` Thomas Hellström
2006-10-09 11:51   ` Benjamin Herrenschmidt
2006-10-09 12:00     ` Nick Piggin
2006-10-09 18:36     ` Ingo Oeser
2006-10-09 21:03       ` Benjamin Herrenschmidt [this message]
2006-10-09 19:14   ` Linus Torvalds
2006-10-09 21:06     ` Benjamin Herrenschmidt

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=1160427829.7752.21.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=hugh@veritas.com \
    --cc=ioe-lkml@rameria.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=thomas@tungstengraphics.com \
    --cc=torvalds@osdl.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