public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: venkatesh.pallipadi@intel.com
Cc: mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com,
	akpm@linux-foundation.org, hugh@veritas.com, arjan@infradead.org,
	jbarnes@virtuousgeek.org, rdreier@cisco.com, jeremy@goop.org,
	linux-kernel@vger.kernel.org,
	Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [patch 2/7] x86 PAT: Add follow_pfnmp_pte routine to help tracking pfnmap pages - v3
Date: Thu, 18 Dec 2008 22:31:12 +0100	[thread overview]
Message-ID: <20081218213112.GE10681@wotan.suse.de> (raw)
In-Reply-To: <20081218194617.247280000@intel.com>

On Thu, Dec 18, 2008 at 11:41:28AM -0800, venkatesh.pallipadi@intel.com wrote:
> Add a generic interface to follow pfn in a pfnmap vma range. This is used by
> one of the subsequent x86 PAT related patch to keep track of memory types
> for vma regions across vma copy and free.
> 
> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>

Can you please reuse follow_phys for this? (preferably use the same API
even if it requires some modification, otherwise if not possible, then
at least can you implement a common core for both APIs).


> 
> ---
>  include/linux/mm.h |    3 +++
>  mm/memory.c        |   43 +++++++++++++++++++++++++++++++++++++++++++
>  2 files changed, 46 insertions(+)
> 
> Index: linux-2.6/include/linux/mm.h
> ===================================================================
> --- linux-2.6.orig/include/linux/mm.h	2008-11-25 13:56:46.000000000 -0800
> +++ linux-2.6/include/linux/mm.h	2008-11-25 14:20:23.000000000 -0800
> @@ -1223,6 +1223,9 @@ struct page *follow_page(struct vm_area_
>  #define FOLL_GET	0x04	/* do get_page on page */
>  #define FOLL_ANON	0x08	/* give ZERO_PAGE if no pgtable */
>  
> +int follow_pfnmap_pte(struct vm_area_struct *vma,
> +				unsigned long address, pte_t *ret_ptep);
> +
>  typedef int (*pte_fn_t)(pte_t *pte, pgtable_t token, unsigned long addr,
>  			void *data);
>  extern int apply_to_page_range(struct mm_struct *mm, unsigned long address,
> Index: linux-2.6/mm/memory.c
> ===================================================================
> --- linux-2.6.orig/mm/memory.c	2008-11-25 14:07:42.000000000 -0800
> +++ linux-2.6/mm/memory.c	2008-11-25 14:18:35.000000000 -0800
> @@ -1111,6 +1111,49 @@ no_page_table:
>  	return page;
>  }
>  
> +int follow_pfnmap_pte(struct vm_area_struct *vma, unsigned long address,
> +			pte_t *ret_ptep)
> +{
> +	pgd_t *pgd;
> +	pud_t *pud;
> +	pmd_t *pmd;
> +	pte_t *ptep, pte;
> +	spinlock_t *ptl;
> +	struct page *page;
> +	struct mm_struct *mm = vma->vm_mm;
> +
> +	if (!is_pfn_mapping(vma))
> +		goto err;
> +
> +	page = NULL;
> +	pgd = pgd_offset(mm, address);
> +	if (pgd_none(*pgd) || unlikely(pgd_bad(*pgd)))
> +		goto err;
> +
> +	pud = pud_offset(pgd, address);
> +	if (pud_none(*pud) || unlikely(pud_bad(*pud)))
> +		goto err;
> +
> +	pmd = pmd_offset(pud, address);
> +	if (pmd_none(*pmd) || unlikely(pmd_bad(*pmd)))
> +		goto err;
> +
> +	ptep = pte_offset_map_lock(mm, pmd, address, &ptl);
> +
> +	pte = *ptep;
> +	if (!pte_present(pte))
> +		goto err_unlock;
> +
> +	*ret_ptep = pte;
> +	pte_unmap_unlock(ptep, ptl);
> +	return 0;
> +
> +err_unlock:
> +	pte_unmap_unlock(ptep, ptl);
> +err:
> +	return -EINVAL;
> +}
> +
>  /* Can we do the FOLL_ANON optimization? */
>  static inline int use_zero_page(struct vm_area_struct *vma)
>  {
> 
> -- 

  reply	other threads:[~2008-12-18 21:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18 19:41 [patch 0/7] x86 PAT: track pfnmap mappings with remap_pfn_range vm_insert_pfn - v3 venkatesh.pallipadi
2008-12-18 19:41 ` [patch 1/7] x86 PAT: store vm_pgoff for all linear_over_vma_region mappings " venkatesh.pallipadi
2008-12-18 21:27   ` Nick Piggin
2008-12-18 22:10     ` Pallipadi, Venkatesh
2008-12-18 22:33       ` Nick Piggin
2008-12-18 19:41 ` [patch 2/7] x86 PAT: Add follow_pfnmp_pte routine to help tracking pfnmap pages " venkatesh.pallipadi
2008-12-18 21:31   ` Nick Piggin [this message]
2008-12-18 22:15     ` Pallipadi, Venkatesh
2008-12-18 19:41 ` [patch 3/7] x86 PAT: hooks in generic vm code to help archs to track pfnmap regions " venkatesh.pallipadi
2008-12-18 21:35   ` Nick Piggin
2008-12-18 22:23     ` Pallipadi, Venkatesh
2008-12-18 19:41 ` [patch 4/7] x86 PAT: Implement track/untrack of pfnmap regions for x86 " venkatesh.pallipadi
2008-12-18 21:38   ` Nick Piggin
2008-12-18 21:40     ` H. Peter Anvin
2008-12-18 21:46       ` Ingo Molnar
2008-12-18 21:53         ` Pallipadi, Venkatesh
2008-12-18 19:41 ` [patch 5/7] x86 PAT: change pgprot_noncached to uc_minus instead of strong uc " venkatesh.pallipadi
2008-12-18 19:41 ` [patch 6/7] x86 PAT: add pgprot_writecombine() interface for drivers " venkatesh.pallipadi
2008-12-18 19:41 ` [patch 7/7] x86 PAT: update documentation to cover pgprot and remap_pfn related changes " venkatesh.pallipadi
2008-12-18 21:13   ` Randy Dunlap
2008-12-18 21:49     ` Pallipadi, Venkatesh
2008-12-18 21:53       ` Randy Dunlap
2008-12-18 22:03         ` Pallipadi, Venkatesh
2008-12-18 21:17 ` [patch 0/7] x86 PAT: track pfnmap mappings with remap_pfn_range vm_insert_pfn " H. Peter Anvin

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=20081218213112.GE10681@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=hugh@veritas.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdreier@cisco.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --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