Skip to contentSkip to conversation

Replace nopage() / nopfn() with fault()

DISCUSSION Thomas Hellström 2 participants 3 messages Jan 9, 2007 – Jan 12, 2007

lore
Share & tools
lore
#0 lore raw

Nick,

We're working to slowly get the new DRM memory manager into the mainstream kernel. This means we have a need for the page fault handler patch you wrote some time ago. I guess we could take the no_pfn() route, but that would need a check for racing unmap_mapping_range(), and other problems may arise.

What is the current status and plans for inclusion of the fault() code?

Thanks,
Thomas Hellstrom
Tungsten Graphics.

#1 lore raw
Quoted 11 lines · Thomas Hellström

Nick,

We're working to slowly get the new DRM memory manager into the mainstream kernel.
This means we have a need for the page fault handler patch you wrote some time ago.
I guess we could take the no_pfn() route, but that would need a check for racing
unmap_mapping_range(), and other problems may arise.

What is the current status and plans for inclusion of the fault() code?

Hi Thomas,

fault should have gone in already, but the ordering of my patchset was a little bit unfortunate :P

I will submit them to Andrew later today.

Nick

#2 lore raw
Quoted 14 lines · Nick Piggin
Quoted 10 lines · Thomas Hellström

Nick,

We're working to slowly get the new DRM memory manager into the mainstream kernel. This means we have a need for the page fault handler patch you wrote some time ago. I guess we could take the no_pfn() route, but that would need a check for racing unmap_mapping_range(), and other problems may arise.

What is the current status and plans for inclusion of the fault() code?

Quoted 11 lines

Hi Thomas,

fault should have gone in already, but the ordering of my patchset was a little bit unfortunate :P

I will submit them to Andrew later today.

Nick

Thanks, Nick.

/Thomas.