From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 10277C11F66 for ; Tue, 13 Jul 2021 16:10:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EE4E0611AB for ; Tue, 13 Jul 2021 16:10:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230254AbhGMQNa (ORCPT ); Tue, 13 Jul 2021 12:13:30 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:54072 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230122AbhGMQNa (ORCPT ); Tue, 13 Jul 2021 12:13:30 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1626192638; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=iEAhZ97kc19v5KOhlPKV1kLM8SFB0YQp8RmvQDnU2XE=; b=ho1DbTFaxUHhnPyMnI4J3nwQKqJgz2YxEcfwiqLjGhO7y5S0KUHSdOs2GUOwfXJ9Pyb3Iu q/YbW5YC2PpzHzMPId0giqqpC0JVj9eT8ZIDlPrdQzEtkdEybRNifRpjp3W+GABI1/mIWz AuMZl42DpiU+U3gmItI17SmeK+A9g/B7N5P2uIH7VVmP0kG9coYDdDDJKYIL8hNtqfrfcU 73NO5umljMMq/14YspwSNBJJ3Il+780PUEfu6A0XwKyJ7uFCo5dTVKJltrFk3/nOs5Eiys 6cE9l15kKglOJ9DnaEyGIC3tTp6U+q3WrrHJxIlg7SLXo+60dw+uxqubpFaZLQ== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1626192638; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=iEAhZ97kc19v5KOhlPKV1kLM8SFB0YQp8RmvQDnU2XE=; b=hDJAXLk2s+jZ7ffTp+oAOk1BpiDwv7hJIrqjFX70cWZd8QVV5firdqF92WgMdwDV5kao2+ iNWr41XxFmz1frBg== To: Yongxin Liu Cc: evgreen@chromium.org, rajatja@google.com, bhelgaas@google.com, stable@vger.kernel.org, linux-pci@vger.kernel.org, x86@kernel.org, maz@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86/apic/msi: check interupt context before reporting warning In-Reply-To: <20210713064609.25429-1-yongxin.liu@windriver.com> References: <20210713064609.25429-1-yongxin.liu@windriver.com> Date: Tue, 13 Jul 2021 18:10:38 +0200 Message-ID: <874kcychz5.ffs@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 13 2021 at 14:46, Yongxin Liu wrote: > Affinity change can happen in both interrupt context and non-interrupt > context. The paranoia check for interrupt target cpu is not always true > in non-interrupt context. Supressing the warning is just papering over a larger underlying problem which was discussed recently already. I'm working on a fix for that already. Thanks, tglx