Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-next@vger.kernel.org, Tejun Heo <tj@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: linux-next: manual merge of the kmemleak tree with the tip-core tree
Date: Fri, 6 Mar 2009 18:21:46 +1100	[thread overview]
Message-ID: <20090306182146.8f07e030.sfr@canb.auug.org.au> (raw)

Hi Catalin,

Today's linux-next merge of the kmemleak tree got a conflict in
include/linux/percpu.h between commit
fbf59bc9d74d1fb30b8e0630743aff2806eafcea ("percpu: implement new dynamic
percpu allocator") from the tip-core tree and commit
a1c9c21c85f5c0bda772419c758bd3f4248ce840 ("kmemleak: Remove some of the
kmemleak false positives") from the kmemleak tree.

I fixed it up (see below) and can carry the fix as necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

diff --cc include/linux/percpu.h
index 545b068,c3b95c0..0000000
--- a/include/linux/percpu.h
+++ b/include/linux/percpu.h
@@@ -132,18 -69,25 +132,23 @@@ struct percpu_data 
  	void *ptrs[1];
  };
  
+ /* pointer disguising messes up the kmemleak objects tracking */
+ #ifndef CONFIG_DEBUG_KMEMLEAK
  #define __percpu_disguise(pdata) (struct percpu_data *)~(unsigned long)(pdata)
+ #else
+ #define __percpu_disguise(pdata) (struct percpu_data *)(pdata)
+ #endif
 -/* 
 - * Use this to get to a cpu's version of the per-cpu object dynamically
 - * allocated. Non-atomic access to the current CPU's version should
 - * probably be combined with get_cpu()/put_cpu().
 - */ 
 -#define percpu_ptr(ptr, cpu)                              \
 -({                                                        \
 -        struct percpu_data *__p = __percpu_disguise(ptr); \
 -        (__typeof__(ptr))__p->ptrs[(cpu)];	          \
 +
 +#define per_cpu_ptr(ptr, cpu)						\
 +({									\
 +        struct percpu_data *__p = __percpu_disguise(ptr);		\
 +        (__typeof__(ptr))__p->ptrs[(cpu)];				\
  })
  
 -extern void *__percpu_alloc_mask(size_t size, gfp_t gfp, cpumask_t *mask);
 -extern void percpu_free(void *__pdata);
 +#endif /* CONFIG_HAVE_DYNAMIC_PER_CPU_AREA */
 +
 +extern void *__alloc_percpu(size_t size, size_t align);
 +extern void free_percpu(void *__pdata);
  
  #else /* CONFIG_SMP */
  

             reply	other threads:[~2009-03-06  7:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  7:21 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-06  7:19 linux-next: manual merge of the kmemleak tree with the tip-core tree Stephen Rothwell
2009-03-06  7:17 Stephen Rothwell
2009-02-17  8:45 Stephen Rothwell

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=20090306182146.8f07e030.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=catalin.marinas@arm.com \
    --cc=hpa@zytor.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    /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