Messages in this thread | | | From | "Pallipadi, Venkatesh" <> | Date | Mon, 15 Dec 2008 13:50:05 -0800 | Subject | RE: [patch 0/7] x86 PAT: v2 - track pfnmap mappings with remap_pfn_range and vm_insert_pfn |
| |
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@linux-foundation.org; npiggin@suse.de; >hugh@veritas.com; mingo@elte.hu; hpa@zytor.com; tglx@linutronix.de >Cc: rdreier@cisco.com; jeremy@goop.org; >jbarnes@virtuousgeek.org; arjan@infradead.org; 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. > > >-- > >
| |