mirror of
https://github.com/torvalds/linux.git
synced 2024-11-01 09:41:44 +00:00
d95bfe464b
Rationales from Eric: So I just looked a little deeper and it appears architectures that do not support atomic64_t are broken. The generic atomic64 support came in 2009 to support the perf subsystem with the expectation that all architectures would implement atomic64 support. Furthermore upon inspection of the kernel atomic64_t is used in a fair number of places beyond the performance counters: block/blk-cgroup.c drivers/acpi/apei/ drivers/block/rbd.c drivers/crypto/nx/nx.h drivers/gpu/drm/radeon/radeon.h drivers/infiniband/hw/ipath/ drivers/infiniband/hw/qib/ drivers/staging/octeon/ fs/xfs/ include/linux/perf_event.h include/net/netfilter/nf_conntrack_acct.h kernel/events/ kernel/trace/ net/mac80211/key.h net/rds/ The block control group, infiniband, xfs, crypto, 802.11, netfilter. Nothing quite so fundamental as fs/namespace.c but definitely in multiplatform-code that should work, and is already broken on those architecutres. Looking at the implementation of atomic64_add_return in lib/atomic64.c the code looks as efficient as these kinds of things get. Which leads me to the conclusion that we need atomic64 support on all architectures. Signed-off-by: Fengguang Wu <fengguang.wu@intel.com> Cc: "Eric W. Biederman" <ebiederm@xmission.com> Cc: Yoshinori Sato <ysato@users.sourceforge.jp> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
---|---|---|
.. | ||
boot | ||
include | ||
kernel | ||
lib | ||
mm | ||
platform | ||
defconfig | ||
Kconfig | ||
Kconfig.cpu | ||
Kconfig.debug | ||
Kconfig.ide | ||
Makefile | ||
README |
linux-2.6 for H8/300 README Yoshinori Sato <ysato@users.sourceforge.jp> * Supported CPU H8/300H and H8S * Supported Target 1.simulator of GDB require patches. 2.AE 3068/AE 3069 more information MICROTRONIQUE <http://www.microtronique.com/> Akizuki Denshi Tsusho Ltd. <http://www.akizuki.ne.jp> (Japanese Only) 3.H8MAX see http://ip-sol.jp/h8max/ (Japanese Only) 4.EDOSK2674 see http://www.eu.renesas.com/products/mpumcu/tool/edk/support/edosk2674.html http://www.uclinux.org/pub/uClinux/ports/h8/HITACHI-EDOSK2674-HOWTO http://www.azpower.com/H8-uClinux/ * Toolchain Version gcc-3.1 or higher and patch see arch/h8300/tools_patch/README binutils-2.12 or higher gdb-5.2 or higher The environment that can compile a h8300-elf binary is necessary. * Userland Develop environment used h8300-elf toolchains. see http://www.uclinux.org/pub/uClinux/ports/h8/ * A few words of thanks Porting to H8/300 serieses is support of Information-technology Promotion Agency, Japan. I thank support. and All developer/user.