From: Jim Nelson <james4765@cwazy.co.uk>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: linux-kernel@vger.kernel.org,
linuxsh-shmedia-dev@lists.sourceforge.net, lethal@linux-sh.org
Subject: Re: [PATCH /3] sh64: remove cli()/sti() from arch/sh64/*
Date: Tue, 04 Jan 2005 22:11:23 -0500 [thread overview]
Message-ID: <41DB5ADB.9060102@cwazy.co.uk> (raw)
In-Reply-To: <20050105023405.GE26051@parcelfarce.linux.theplanet.co.uk>
Al Viro wrote:
>On Tue, Jan 04, 2005 at 08:22:47PM -0600, James Nelson wrote:
>
>
>>This series of patches is to remove the last cli()/sti() function calls in arch/sh64.
>>
>>
>
>Wait a minute. Is that just a blanket search-and-replace job? There is
>a reason why cli/sti is marked obsolete instead of being silently #define'd
>that way. Namely, in a lot of cases users of cli/sti are actually racy.
>
>For such instances replacing these with local_... would not improve anything
>(obviously) *and* would hide a trouble spot by silencing a warning.
>
>I'm not familiar with the architectures in question, so it might very well
>be that all replacements so far had been correct. However, I would really
>like to see rationale for each of those warning removals to go along with
>the patches.
>
>Note that basically you are doing "remove the warning in foo.c:42 and
>keep the current behaviour". The missing part is "current behaviour is,
>in fact, correct in that place and does not deserve a warning because
><list of reasons>".
>
>
>
Everything I've looked at so far has been for single-processor systems
AFAICT - embedded processors, evaluation boards, etc. I do not pretend
to have intimate familiarity with the hardware in question, and I will
be much more careful when I reach anything that can be plugged into an
SMP box, but I was grabbing the low-hanging fruit first. The nasty
stuff (drivers/char, for example) will come later.
That's why I cc'd the arch maintainers - figured they'd whack me with a
cluebat if I'd overlooked something.
next prev parent reply other threads:[~2005-01-05 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 2:22 James Nelson
2005-01-05 2:22 ` [PATCH /3] sh64: remove cli()/sti() in arch/sh64/kernel/time.c James Nelson
2005-01-05 2:34 ` [PATCH /3] sh64: remove cli()/sti() from arch/sh64/* Al Viro
2005-01-05 3:11 ` Jim Nelson [this message]
2005-01-05 17:28 ` Paul Mundt
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=41DB5ADB.9060102@cwazy.co.uk \
--to=james4765@cwazy.co.uk \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxsh-shmedia-dev@lists.sourceforge.net \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
Powered by JetHome