[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <494ABDED.60308@zytor.com>
Date: Thu, 18 Dec 2008 13:17:33 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: venkatesh.pallipadi@...el.com
CC: mingo@...e.hu, tglx@...utronix.de, akpm@...ux-foundation.org,
npiggin@...e.de, hugh@...itas.com, arjan@...radead.org,
jbarnes@...tuousgeek.org, rdreier@...co.com, jeremy@...p.org,
linux-kernel@...r.kernel.org,
Suresh Siddha <suresh.b.siddha@...el.com>
Subject: Re: [patch 0/7] x86 PAT: track pfnmap mappings with remap_pfn_range
vm_insert_pfn - v3
venkatesh.pallipadi@...el.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists