Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755399AbbBTUDH (ORCPT ); Fri, 20 Feb 2015 15:03:07 -0500 Received: from mail-ig0-f169.google.com ([209.85.213.169]:56827 "EHLO mail-ig0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753936AbbBTUDE (ORCPT ); Fri, 20 Feb 2015 15:03:04 -0500 MIME-Version: 1.0 In-Reply-To: <20150220194114.GA3603@gmail.com> References: <20150218222544.GA17717@twins.programming.kicks-ass.net> <20150220093000.GA22661@gmail.com> <20150220194114.GA3603@gmail.com> Date: Fri, 20 Feb 2015 12:03:03 -0800 X-Google-Sender-Auth: pMdWr28R2ddIC8XCBnHawTnR9zk Message-ID: Subject: Re: smp_call_function_single lockups From: Linus Torvalds To: Ingo Molnar Cc: Rafael David Tinoco , Peter Anvin , Jiang Liu , Peter Zijlstra , LKML , Jens Axboe , Frederic Weisbecker , Gema Gomez , Christopher Arges , "the arch/x86 maintainers" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 823 Lines: 20 On Fri, Feb 20, 2015 at 11:41 AM, Ingo Molnar wrote: > > I'm not so sure about that aspect: I think disabling IRQs > might be necessary with some APICs (if lower levels don't > disable IRQs), to make sure the 'local APIC busy' bit isn't > set: Right. But afaik not for the x2apic case, which this is. The x2apic doesn't even have a busy bit, and sending the ipi is a single write, I agree that when doing other apic implementations, we may need to guarantee atomicity for things like "wait for apic idle, then send the ipi". Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/