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.7 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,URIBL_BLOCKED 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 6014EC47076 for ; Fri, 21 May 2021 15:16:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3B143613E6 for ; Fri, 21 May 2021 15:16:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232447AbhEUPRW (ORCPT ); Fri, 21 May 2021 11:17:22 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:54568 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230420AbhEUPRS (ORCPT ); Fri, 21 May 2021 11:17:18 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1621610153; 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=7rDRNMv1/hXibroql/UgiqWQxCjjntQmsL2o4JvFzco=; b=CR2dKo3U/qEBXxRraK/8180LCq2JsVkgxoQhDex49QqNVsA8WjfbCTuVAvD4DqbhzqEg1p ZwJgdt4G35FTyS8UDSsCt1txkl1Bie1PciZkWfLORal7+xPmjMv41Jqz5tn3bG9iyWZ7gq /QMT/Yowkk4ZN1Ngvzy71tZEyQsFX7Mvkc3DtD8wskLXULMGAXIt5jNgrSIQIiAf7DU94i Sc4sTbCpSUws0yW4AJeK1viYb1VQzQyDUzMVuBmzHBg2zyPGBQppD6I1kBmKwrbBiW7QpR KWkhnjqCGGhNCPBgpqfnuZXZg2aoke1az2/RnVU3FxAZRCdbtqVdk6AXgIMe+w== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1621610153; 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=7rDRNMv1/hXibroql/UgiqWQxCjjntQmsL2o4JvFzco=; b=KUni+pfxwwfjisVYWwUO6XqqoJkOc9cJl+l6wjG0Pf13ZeZyiU+ahF3JQji/TLv5FM1TnR p5NROJTbK6SxNWBA== To: Nitesh Lal Cc: Jesse Brandeburg , Robin Murphy , Marcelo Tosatti , Ingo Molnar , linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org, jbrandeb@kernel.org, "frederic\@kernel.org" , "juri.lelli\@redhat.com" , Alex Belits , "linux-api\@vger.kernel.org" , "bhelgaas\@google.com" , "linux-pci\@vger.kernel.org" , "rostedt\@goodmis.org" , "peterz\@infradead.org" , "davem\@davemloft.net" , "akpm\@linux-foundation.org" , "sfr\@canb.auug.org.au" , "stephen\@networkplumber.org" , "rppt\@linux.vnet.ibm.com" , "jinyuqi\@huawei.com" , "zhangshaokun\@hisilicon.com" , netdev@vger.kernel.org, chris.friesen@windriver.com, Marc Zyngier , Neil Horman , pjwaskiewicz@gmail.com Subject: Re: [PATCH tip:irq/core v1] genirq: remove auto-set of the mask when setting the hint In-Reply-To: References: <20210504092340.00006c61@intel.com> <87pmxpdr32.ffs@nanos.tec.linutronix.de> <87im3gewlu.ffs@nanos.tec.linutronix.de> <87zgwo9u79.ffs@nanos.tec.linutronix.de> Date: Fri, 21 May 2021 17:15:53 +0200 Message-ID: <87pmxk9kye.ffs@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-api@vger.kernel.org On Fri, May 21 2021 at 09:46, Nitesh Lal wrote: > On Fri, May 21, 2021 at 7:56 AM Thomas Gleixner wrote: >> >> - Driver use this API to force a certain affinity mask >> >> + In this case we have to replace the API with the irq_force_affinity() >> >> irq_set_affinity() or irq_set_affinity_and_hint() > > Ah yes! my bad. _force_ doesn't check the mask against the online CPUs. > Hmm, I didn't realize that you also added irq_set_affinity_and_hint() > in your last patchset. I did not. It just exposed irq_set_affinity(). See https://lore.kernel.org/r/87wnrs9tvp.ffs@nanos.tec.linutronix.de for the new hint interface I came up with. Thanks, tglx