From: Mike Travis <travis@sgi.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
mm-commits@vger.kernel.org, Yinghai Lu <yhlu.kernel@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] x86: Add check for node passed to node_to_cpumask V3
Date: Sun, 29 Jun 2008 05:40:09 -0700 [thread overview]
Message-ID: <486782A9.9060704@sgi.com> (raw)
In-Reply-To: <19f34abd0806290434l836e858p47850eb96addd0b3@mail.gmail.com>
Vegard Nossum wrote:
> On Fri, Jun 27, 2008 at 8:03 PM, Mike Travis <travis@sgi.com> wrote:
>>> So if CONFIG_DEBUG_RODATA=y, I believe we'll see first this warning,
>>> then a panic (after all). Would it be better to make cpu_mask_none
>>> non-const, in spirit of trying to continue as far as possible? I don't
>>> really know if it matters, though. It seems that fedora kernels at
>>> least ship with a default of DEBUG_RODATA=y.
>>>
>
> ...
>
>> Ingo asked me to add the "const". But it would be a mistake to use
>> node_to_cpumask_ptr to modify the map... numa_set/clear_node is the
>> proper way to modify the maps. Hmm, maybe I should add "const" to
>> the real node_to_cpumask_ptr function, at least then the compiler
>> would help spot illegal usages.
>
> That sounds like a brilliant idea, as long as none of the callers
> expect it to be non-const.
Being that I modified all the callers to use this new function, I did
verify that each caller expected it to be read only... ;-)
>
> I changed it to return const to see, and built allmodconfig + a few
> randconfigs without error (well, warning). There are not that many
> users of this function anyway.
Did any violate the read-only nature of the call?
>
> BTW, what's up with the topology.h/setup_percpu.c mismatch, when
> topology.c exists as well?
Topology.h supplies the generic usage which is to define a local cpumask
variable, fill it, and then return a pointer to it. This is for arch's
that do not maintain a separate node_to_cpumask_map[] but allows a
compatible call interface.
>
>
> Vegard
>
Thanks!
Mike
next prev parent reply other threads:[~2008-06-29 12:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806090918.m599Ib0G012837@imap1.linux-foundation.org>
[not found] ` <19f34abd0806090420r4100241cgb4b828441de3b102@mail.gmail.com>
[not found] ` <20080609113547.GA1534@elte.hu>
[not found] ` <484D54F2.4070603@sgi.com>
[not found] ` <20080626113229.GB29619@elte.hu>
2008-06-26 16:26 ` [PATCH 1/1] x86: Add check for node passed to node_to_cpumask Mike Travis
2008-06-27 2:39 ` [PATCH 1/1] x86: Add check for node passed to node_to_cpumask V2 Mike Travis
2008-06-27 17:10 ` [PATCH 1/1] x86: Add check for node passed to node_to_cpumask V3 Mike Travis
2008-06-27 17:24 ` Vegard Nossum
2008-06-27 18:03 ` Mike Travis
2008-06-29 11:34 ` Vegard Nossum
2008-06-29 12:40 ` Mike Travis [this message]
2008-07-03 8:44 ` Ingo Molnar
2008-07-03 8:55 ` Vegard Nossum
2008-07-03 9:01 ` Ingo Molnar
2008-07-08 17:06 ` [PATCH 1/1] x86: Change _node_to_cpumask_ptr to return const ptr Mike Travis
2008-07-08 17:35 ` Vegard Nossum
2008-07-08 18:05 ` Mike Travis
2008-07-08 18:22 ` Vegard Nossum
2008-07-08 20:51 ` Mike Travis
2008-07-08 21:21 ` Vegard Nossum
2008-07-08 21:28 ` Mike Travis
2008-07-08 21:35 ` Mike Travis
2008-07-08 21:52 ` Vegard Nossum
2008-07-13 17:12 ` Ingo Molnar
2008-07-07 17:23 ` [PATCH 1/1] x86: Add check for node passed to node_to_cpumask V3 Mike Travis
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=486782A9.9060704@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=vegard.nossum@gmail.com \
--cc=yhlu.kernel@gmail.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