On Wed, Nov 17, 2010 at 6:49 PM, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote: > On Wed, 2010-11-17 at 14:05 +0800, Huang Ying wrote: >> Hi, Peter, >> >> Do you think think irq_work should depend on that? ÂOr we just >> reimplement irq_work based on lockless list and make irq_work depends on >> lockless list? > > If you can make it use a lockless list thing that's fine. I will try to do that. > 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. > Anyway, make sure to consolidate net/rds/xlist.h and its users, having > two lockless lists is one too many. Sure. >> At least as the first step, I prefer to just make lockless list depend >> on CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG. > > But only if the platform has NMIs, otherwise its moot. Yes. Best Regards, Huang Ying -- 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
