All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
	Dave Martin <dave.martin@linaro.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Tony Lindgren <tony@atomide.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	linux-omap@vger.kernel.org, Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH v2] ARM: Define wfi() macro for v6 processors
Date: Wed, 9 Feb 2011 11:07:54 +0100	[thread overview]
Message-ID: <201102091107.54917.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTimDTVypBFCoO9G72TzKToAThdXm_aEi56O+w9nY@mail.gmail.com>

On Tuesday 08 February 2011, Dave Martin wrote:
> I have a (possibly silly) question ... are the definitions in
> arm/system.h intended to be fully generic, or not?  Some features
> suggest an attempt at genericness, but not everything there is
> generic.  Maybe I have misconstrued the purpose of this header.

asm/system.h contains an ill-defined set of random stuff derived
from what used to be in there in the old days Linux-1.x and
whatever the individual architectures added to it.

There have been previous attempts to reduce the common stuff
and leave only architecture-specific definitions in there, but
it still contains for all architectures at least:

* switch_to()
* mb() and friends
* cmpxchg() and friends

These are hard to change, because each architecture has slightly
different rules for recursive header file inclusion, so you end
up breaking stuff when you touch them.

The other declarations and macros are arch specific, so we could
move them to a different place or change them if there is a good
reason to do that.

I personally think it would be good to have at least cmpxchg and
everything related to it in a separate header, like a few
architectures do (x86, sh, alpha, mips), but I don't see too
much value in doing that just on ARM while leaving the other
architectures alone.

	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: Define wfi() macro for v6 processors
Date: Wed, 9 Feb 2011 11:07:54 +0100	[thread overview]
Message-ID: <201102091107.54917.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTimDTVypBFCoO9G72TzKToAThdXm_aEi56O+w9nY@mail.gmail.com>

On Tuesday 08 February 2011, Dave Martin wrote:
> I have a (possibly silly) question ... are the definitions in
> arm/system.h intended to be fully generic, or not?  Some features
> suggest an attempt at genericness, but not everything there is
> generic.  Maybe I have misconstrued the purpose of this header.

asm/system.h contains an ill-defined set of random stuff derived
from what used to be in there in the old days Linux-1.x and
whatever the individual architectures added to it.

There have been previous attempts to reduce the common stuff
and leave only architecture-specific definitions in there, but
it still contains for all architectures at least:

* switch_to()
* mb() and friends
* cmpxchg() and friends

These are hard to change, because each architecture has slightly
different rules for recursive header file inclusion, so you end
up breaking stuff when you touch them.

The other declarations and macros are arch specific, so we could
move them to a different place or change them if there is a good
reason to do that.

I personally think it would be good to have at least cmpxchg and
everything related to it in a separate header, like a few
architectures do (x86, sh, alpha, mips), but I don't see too
much value in doing that just on ARM while leaving the other
architectures alone.

	Arnd

  reply	other threads:[~2011-02-09 10:07 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 11:01 [PATCH v2] ARM: Define wfi() macro for v6 processors Dave Martin
2011-02-08 11:01 ` Dave Martin
2011-02-08 11:08 ` Russell King - ARM Linux
2011-02-08 11:08   ` Russell King - ARM Linux
2011-02-08 11:16   ` Dave Martin
2011-02-08 11:16     ` Dave Martin
2011-02-08 12:11   ` Arnd Bergmann
2011-02-08 12:11     ` Arnd Bergmann
2011-02-08 12:13     ` Russell King - ARM Linux
2011-02-08 12:13       ` Russell King - ARM Linux
2011-02-08 12:53       ` Arnd Bergmann
2011-02-08 12:53         ` Arnd Bergmann
2011-02-08 14:45         ` Dave Martin
2011-02-08 14:45           ` Dave Martin
2011-02-08 14:54           ` Santosh Shilimkar
2011-02-08 14:54             ` Santosh Shilimkar
2011-02-08 15:09             ` Dave Martin
2011-02-08 15:09               ` Dave Martin
2011-02-08 15:17               ` Arnd Bergmann
2011-02-08 15:17                 ` Arnd Bergmann
2011-02-08 16:32                 ` Russell King - ARM Linux
2011-02-08 16:32                   ` Russell King - ARM Linux
2011-02-08 16:58                   ` Arnd Bergmann
2011-02-08 16:58                     ` Arnd Bergmann
2011-02-08 17:15                     ` Dave Martin
2011-02-08 17:15                       ` Dave Martin
2011-02-08 15:15           ` Arnd Bergmann
2011-02-08 15:15             ` Arnd Bergmann
2011-02-08 15:30             ` Dave Martin
2011-02-08 15:30               ` Dave Martin
2011-02-08 15:42               ` Arnd Bergmann
2011-02-08 15:42                 ` Arnd Bergmann
2011-02-08 16:21                 ` Dave Martin
2011-02-08 16:21                   ` Dave Martin
2011-02-09 10:07                   ` Arnd Bergmann [this message]
2011-02-09 10:07                     ` Arnd Bergmann
2011-02-08 16:25             ` Russell King - ARM Linux
2011-02-08 16:25               ` Russell King - ARM Linux
2011-02-08 16:31               ` Dave Martin
2011-02-08 16:31                 ` Dave Martin
2011-02-08 16:47               ` Arnd Bergmann
2011-02-08 16:47                 ` Arnd Bergmann
2011-02-08 16:55                 ` Russell King - ARM Linux
2011-02-08 16:55                   ` Russell King - ARM Linux
2011-02-08 17:00                   ` Dave Martin
2011-02-08 17:00                     ` Dave Martin
2011-02-08 16:20           ` Russell King - ARM Linux
2011-02-08 16:20             ` Russell King - ARM Linux
2011-02-08 16:28             ` Dave Martin
2011-02-08 16:28               ` Dave Martin
2011-02-08 12:22     ` Dave Martin
2011-02-08 12:22       ` Dave Martin
2011-02-08 12:31       ` Santosh Shilimkar
2011-02-08 12:31         ` Santosh Shilimkar

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=201102091107.54917.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=dave.martin@linaro.org \
    --cc=j-pihet@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nicolas.pitre@linaro.org \
    --cc=santosh.shilimkar@ti.com \
    --cc=tony@atomide.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 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.