From: Tejun Heo <htejun@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Fengguang Wu <fengguang.wu@intel.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Motohiro Kosaki <Motohiro.Kosaki@us.fujitsu.com>,
Mike Travis <travis@sgi.com>
Subject: Re: percpu: Define this_cpu_cpumask_var_t_ptr
Date: Thu, 28 Aug 2014 09:02:13 -0400 [thread overview]
Message-ID: <20140828130213.GD29737@htj.dyndns.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1408261911290.22692@gentwo.org>
Hello,
On Tue, Aug 26, 2014 at 07:12:21PM -0500, Christoph Lameter wrote:
>
> New patch:
>
> From: Christoph Lameter <cl@linux.com>
> Subject: __get_cpu_var/cpumask_var_t: Resolve ambiguities v2
>
> __get_cpu_var can paper over differences in the definitions
> of cpumask_var_t and either use the address of the cpumask
> variable directly or perform a fetch of the address of the
> struct cpumask allocated elsewhere. This is important
> particularly when using per cpu cpumask_var_t declarations
> because in one case we have an offset into a per cpu area
> to handle and in the other case we need to fetch a pointer
> from the offset.
>
> This patch introduces a new macro
>
> this_cpu_cpumask_var_t_ptr()
>
> that is defined where cpumask_var_t is defined and performs
> the proper actions. All use cases where __get_cpu_var
> is used with cpumask_var_t are converted to the use
> of this_cpu_cpumask_var_t_ptr().
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
Rusty, if this looks okay to you, I'll route this through
percpu/for-3.18-consistent-ops branch.
Thanks.
--
tejun
prev parent reply other threads:[~2014-08-28 13:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 15:05 Christoph Lameter
2014-08-08 19:46 ` Christoph Lameter
2014-08-21 22:22 ` Tejun Heo
2014-08-22 1:03 ` Christoph Lameter
2014-08-22 16:40 ` Tejun Heo
2014-08-22 17:43 ` Christoph Lameter
2014-08-23 17:14 ` Tejun Heo
2014-08-23 20:00 ` Christoph Lameter
2014-08-26 21:33 ` Christoph Lameter
2014-08-26 21:37 ` Tejun Heo
2014-08-26 23:04 ` Christoph Lameter
2014-08-27 0:12 ` Christoph Lameter
2014-08-28 13:02 ` Tejun Heo [this message]
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=20140828130213.GD29737@htj.dyndns.org \
--to=htejun@gmail.com \
--cc=Motohiro.Kosaki@us.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=travis@sgi.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®