RE: [patch 0/7] x86 PAT: v2 - track pfnmap mappings withremap_pfn_range and vm_insert_pfn

[Pallipadi, Venkatesh]

Ingo,

Haven't seen any comments on the patches here. Can you push these patches along to tip.

Thanks,
Venki

>-----Original Message-----
>From: Pallipadi, Venkatesh
>Sent: Tuesday, November 25, 2008 4:22 PM
>To: akpm@xxxxxxxxxxxxxxxxxxxx; npiggin@xxxxxxx;
>hugh@xxxxxxxxxxx; mingo@xxxxxxx; hpa@xxxxxxxxx; tglx@xxxxxxxxxxxxx
>Cc: rdreier@xxxxxxxxx; jeremy@xxxxxxxx;
>jbarnes@xxxxxxxxxxxxxxxx; arjan@xxxxxxxxxxxxx; linux-kernel@;
>Siddha, Suresh B
>Subject: [patch 0/7] x86 PAT: v2 - track pfnmap mappings with
>remap_pfn_range and vm_insert_pfn
>
>Followup for the patches posted earlier here:
>http://marc.info/?l=linux-kernel&m=122653213110404&w=2
>
>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.
>
>
>--
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/