Messages in this thread | | | Date | Thu, 18 Dec 2008 13:17:33 -0800 | From | "H. Peter Anvin" <> | Subject | Re: [patch 0/7] x86 PAT: track pfnmap mappings with remap_pfn_range vm_insert_pfn - v3 |
| |
venkatesh.pallipadi@intel.com wrote: > v3: Patches updated based on Andrew's comments on the earlier version. > > Drivers use mmap followed by pgprot_* and remap_pfn_range or vm_insert_pfn, > in order to export reserved memory to userspace. Currently, such mappings are > not tracked and hence not kept consistent with other mappings (/dev/mem, > pci resource, ioremap) for the sme memory, that may exist in the system. > > The following patchset adds x86 PAT attribute tracking and untracking for > pfnmap related APIs. > > First three patches in the patchset are changing the generic mm code to fit > in this tracking. Last four patches are x86 specific to make things work > with x86 PAT code. The patchset aso introduces pgprot_writecombine interface, > which gives writecombine mapping when enabled, falling back to > pgprot_noncached otherwise.
Series applied to tip:x86/pat2, thanks!
-hpa
-- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
| |