From: Nick Piggin <npiggin@suse.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"elendil@planet.nl" <elendil@planet.nl>,
"thellstrom@vmware.com" <thellstrom@vmware.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@elte.hu" <mingo@elte.hu>
Subject: Re: [PATCH] Add a new vm flag to track full pfnmap at mmap
Date: Sat, 14 Mar 2009 03:53:18 +0100 [thread overview]
Message-ID: <20090314025318.GB32065@wotan.suse.de> (raw)
In-Reply-To: <20090313233543.GA19909@linux-os.sc.intel.com>
On Fri, Mar 13, 2009 at 04:35:44PM -0700, Pallipadi, Venkatesh wrote:
>
> Add a new vm flag VM_PFN_AT_MMAP to identify a PFNMAP that is
> fully mapped with remap_pfn_range. Patch removes the overloading
> of VM_INSERTPAGE from the earlier patch.
>
Acked-by: Nick Piggin <npiggin@suse.de>
> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
> ---
> include/linux/mm.h | 16 +++-------------
> mm/memory.c | 4 ++--
> 2 files changed, 5 insertions(+), 15 deletions(-)
>
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index 3daa05f..b1ea37f 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -98,12 +98,13 @@ extern unsigned int kobjsize(const void *objp);
> #define VM_HUGETLB 0x00400000 /* Huge TLB Page VM */
> #define VM_NONLINEAR 0x00800000 /* Is non-linear (remap_file_pages) */
> #define VM_MAPPED_COPY 0x01000000 /* T if mapped copy of data (nommu mmap) */
> -#define VM_INSERTPAGE 0x02000000 /* The vma has had "vm_insert_page()" done on it. Refer note in VM_PFNMAP_AT_MMAP below */
> +#define VM_INSERTPAGE 0x02000000 /* The vma has had "vm_insert_page()" done on it */
> #define VM_ALWAYSDUMP 0x04000000 /* Always include in core dumps */
>
> #define VM_CAN_NONLINEAR 0x08000000 /* Has ->fault & does nonlinear pages */
> #define VM_MIXEDMAP 0x10000000 /* Can contain "struct page" and pure PFN pages */
> #define VM_SAO 0x20000000 /* Strong Access Ordering (powerpc) */
> +#define VM_PFN_AT_MMAP 0x40000000 /* PFNMAP vma that is fully mapped at mmap time */
>
> #ifndef VM_STACK_DEFAULT_FLAGS /* arch can override this */
> #define VM_STACK_DEFAULT_FLAGS VM_DATA_DEFAULT_FLAGS
> @@ -127,17 +128,6 @@ extern unsigned int kobjsize(const void *objp);
> #define VM_SPECIAL (VM_IO | VM_DONTEXPAND | VM_RESERVED | VM_PFNMAP)
>
> /*
> - * pfnmap vmas that are fully mapped at mmap time (not mapped on fault).
> - * Used by x86 PAT to identify such PFNMAP mappings and optimize their handling.
> - * Note VM_INSERTPAGE flag is overloaded here. i.e,
> - * VM_INSERTPAGE && !VM_PFNMAP implies
> - * The vma has had "vm_insert_page()" done on it
> - * VM_INSERTPAGE && VM_PFNMAP implies
> - * The vma is PFNMAP with full mapping at mmap time
> - */
> -#define VM_PFNMAP_AT_MMAP (VM_INSERTPAGE | VM_PFNMAP)
> -
> -/*
> * mapping from the currently active vm_flags protection bits (the
> * low four bits) to a page protection mask..
> */
> @@ -156,7 +146,7 @@ extern pgprot_t protection_map[16];
> */
> static inline int is_linear_pfn_mapping(struct vm_area_struct *vma)
> {
> - return ((vma->vm_flags & VM_PFNMAP_AT_MMAP) == VM_PFNMAP_AT_MMAP);
> + return (vma->vm_flags & VM_PFN_AT_MMAP);
> }
>
> static inline int is_pfn_mapping(struct vm_area_struct *vma)
> diff --git a/mm/memory.c b/mm/memory.c
> index e6aced9..302591f 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -1677,7 +1677,7 @@ int remap_pfn_range(struct vm_area_struct *vma, unsigned long addr,
> */
> if (addr == vma->vm_start && end == vma->vm_end) {
> vma->vm_pgoff = pfn;
> - vma->vm_flags |= VM_PFNMAP_AT_MMAP;
> + vma->vm_flags |= VM_PFN_AT_MMAP;
> } else if (is_cow_mapping(vma->vm_flags))
> return -EINVAL;
>
> @@ -1690,7 +1690,7 @@ int remap_pfn_range(struct vm_area_struct *vma, unsigned long addr,
> * needed from higher level routine calling unmap_vmas
> */
> vma->vm_flags &= ~(VM_IO | VM_RESERVED | VM_PFNMAP);
> - vma->vm_flags &= ~VM_PFNMAP_AT_MMAP;
> + vma->vm_flags &= ~VM_PFN_AT_MMAP;
> return -EINVAL;
> }
>
> --
> 1.6.0.6
next prev parent reply other threads:[~2009-03-14 2:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-05 12:47 2.6.29 pat issue Thomas Hellström
2009-02-05 18:03 ` Pallipadi, Venkatesh
2009-02-05 21:32 ` Thomas Hellstrom
2009-02-05 23:08 ` Pallipadi, Venkatesh
2009-02-06 9:51 ` Thomas Hellström
2009-02-06 1:11 ` Eric W. Biederman
2009-02-06 9:43 ` Thomas Hellström
2009-03-04 6:08 ` Pallipadi, Venkatesh
2009-03-04 9:56 ` Thomas Hellstrom
2009-03-06 22:38 ` Pallipadi, Venkatesh
2009-03-06 23:44 ` Thomas Hellstrom
2009-03-10 1:39 ` Pallipadi, Venkatesh
2009-03-10 8:22 ` Thomas Hellstrom
2009-03-10 17:42 ` Pallipadi, Venkatesh
2009-03-11 9:17 ` Thomas Hellstrom
2009-03-11 9:33 ` Ingo Molnar
2009-03-11 17:54 ` [PATCH] VM, x86, PAT: Change implementation of is_linear_pfn_mapping Pallipadi, Venkatesh
2009-03-11 22:09 ` Frans Pop
2009-03-12 0:31 ` Pallipadi, Venkatesh
2009-03-12 3:22 ` Pallipadi, Venkatesh
2009-03-12 5:45 ` Frans Pop
2009-03-12 18:59 ` Pallipadi, Venkatesh
2009-03-12 20:30 ` Frans Pop
2009-03-12 22:48 ` Pallipadi, Venkatesh
2009-03-13 0:36 ` Ingo Molnar
2009-03-13 0:45 ` [PATCH] VM, x86, PAT: Change is_linear_pfn_mapping to not use vm_pgoff Pallipadi, Venkatesh
2009-03-13 4:03 ` [tip:x86/urgent] " Pallipadi, Venkatesh
2009-03-13 16:25 ` Nick Piggin
2009-03-13 17:00 ` Pallipadi, Venkatesh
2009-03-14 2:52 ` Nick Piggin
2009-03-13 23:35 ` [PATCH] Add a new vm flag to track full pfnmap at mmap Pallipadi, Venkatesh
2009-03-14 2:53 ` Nick Piggin [this message]
2009-03-14 8:54 ` [tip:x86/urgent] VM, x86, PAT: add " Pallipadi, Venkatesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090314025318.GB32065@wotan.suse.de \
--to=npiggin@suse.de \
--cc=ebiederm@xmission.com \
--cc=elendil@planet.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thellstrom@vmware.com \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®