All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: Nick Piggin <npiggin@suse.de>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	"mingo@elte.hu" <mingo@elte.hu>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"hugh@veritas.com" <hugh@veritas.com>,
	"arjan@infradead.org" <arjan@infradead.org>,
	"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>,
	"rdreier@cisco.com" <rdreier@cisco.com>,
	"jeremy@goop.org" <jeremy@goop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Siddha, Suresh B" <suresh.b.siddha@intel.com>
Subject: Re: [patch 3/7] x86 PAT: hooks in generic vm code to help archs to track pfnmap regions - v3
Date: Thu, 18 Dec 2008 14:23:41 -0800	[thread overview]
Message-ID: <20081218222340.GC3331@linux-os.sc.intel.com> (raw)
In-Reply-To: <20081218213557.GF10681@wotan.suse.de>

On Thu, Dec 18, 2008 at 01:35:57PM -0800, Nick Piggin wrote:
> On Thu, Dec 18, 2008 at 11:41:29AM -0800, venkatesh.pallipadi@intel.com wrote:
> > Introduce generic hooks in remap_pfn_range and vm_insert_pfn and
> > corresponding copy and free routines with reserve and free tracking.
> 
> These should be inline so that they can be folded out (I'm sure gcc
> with -Os and "optimize" inlining will do something stupid here).
> Also, the normal way to add such arch hooks is to put the default
> into asm-generic and have other archs include it... that would be
> nicer than sticking it into mm/memory.c wouldn't it?

I did check that these calls were optimized by gcc when there is no arch
specific definitions. But, as you pointed out, it should be cleaner to put this
in asm-generic, though I may have to touch more files.

> Sigh, fork/exit paths slow down yet again. But oh well. Maybe can
> you add some branch hints?

OK. Will add branch hints for these..

Thanks,
Venki


  reply	other threads:[~2008-12-18 22:23 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
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 [this message]
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=20081218222340.GC3331@linux-os.sc.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --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=npiggin@suse.de \
    --cc=rdreier@cisco.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.