On Wed, 2010-11-17 at 19:16 +0800, huang ying wrote: > > I'm not sure Andrew's CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG makes much sense > > for CONFIG_ARCH_HAVE_NMI=n though.. > > Sorry, I do not find ARCH_HAVE_NMI in any Kconfig, can you help me to > point out? I think cmpxchg can be used safely in lock-less code on > architectures without NMI. It doesn't exist, but what I'm saying is that HAVE_NMI_SAFE_CMPXCHG is pointless for architectures that don't actually have an NMI, although I guess you can argue that since it doesn't have one its safe by default, still slightly confusing. Some arch don't currently implement NMI like functionality (ARM comes to mind) but they could using interrupt priorities (like SPARC64 does for example). -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
