Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp424515imm; Thu, 6 Sep 2018 04:51:51 -0700 (PDT) X-Google-Smtp-Source: ANB0VdYHcDGvGirQybQkhIqY1ClzkGUk/lM/YEz7s8AjYOK0MOM3b8EAcj3oxPVUczgEowovUv01 X-Received: by 2002:a62:f610:: with SMTP id x16-v6mr2321792pfh.169.1536234711212; Thu, 06 Sep 2018 04:51:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536234711; cv=none; d=google.com; s=arc-20160816; b=henOpDifvo56BiHd6pBHYDWMHOkAJDmKgmvtdjrVH+LWQ3wyxr9jcM12sqmp81cHfx Sox51SuqiEmWYxy+tHATma7fP8X17pVOzg6ju4cOpPitn8+EoM8hIFxHnwAS84BggG5i 4gL+Lk/I9yUzhzjN2KP9j25RGOiGSUlBh3GZuP/MIoHXAPSvMU/p4nzca5B9F5aX42NX iv7xqBiNvhO0HJ5eak+Jq3QBigtzep1QMyaEj86nyXYGxlDwifJoGiiemSUGvAGfQCP1 kPX9mp3YJd58vKGu3YJ+Cnmy1xdzdbVpuHq50sjOvM/yrZlUL56ia+uNW3oXOPmZbyc1 yMnw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=i3rJxIjbOQujsxfXbu/ZBk9lkQcj2fr48NvvfpmOIdc=; b=DyW0Njv0z/KWKmdEFsuXgN7vt7OARrEw53UHVB/tFLHYdRp1VfOqm4YvGw1i5YWj0N uf8Ytrgs/9ILtJbjZuQkapCeL7vjDrH9N5qmtDQqZiypX3oIQPjX3ZyjLtEeSOiM23k0 4GOsB66E2CKavuf4j2L/cT37Ly68Z2wBdaqh5Puu95gmaLqoOlfYRhsyMeQGn9vAyRIG iOPKE+RCg+nVRIMrCQfYcXcgwAyBl9NXxmHZv57N7dH6tegoTrhSpXPsURc+aVRGs9p5 QlyK3VehD8QUOuC9577TMue6cSBBHo+vT3akZWRpZQpf0tpdzPzYCV6iOyB6bUlKpdz6 PX+g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v8-v6si4936894pga.487.2018.09.06.04.51.35; Thu, 06 Sep 2018 04:51:51 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727217AbeIFQWA (ORCPT + 99 others); Thu, 6 Sep 2018 12:22:00 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:33564 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725929AbeIFQWA (ORCPT ); Thu, 6 Sep 2018 12:22:00 -0400 Received: from hsi-kbw-5-158-153-52.hsi19.kabel-badenwuerttemberg.de ([5.158.153.52] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fxskI-0005Zh-EW; Thu, 06 Sep 2018 13:46:46 +0200 Date: Thu, 6 Sep 2018 13:46:46 +0200 (CEST) From: Thomas Gleixner To: Dou Liyang cc: Kashyap Desai , Ming Lei , Sumit Saxena , Ming Lei , Christoph Hellwig , Linux Kernel Mailing List , Shivasharan Srikanteshwara , linux-block , Dou Liyang Subject: Re: Affinity managed interrupts vs non-managed interrupts In-Reply-To: Message-ID: References: <20180829084618.GA24765@ming.t460p> <300d6fef733ca76ced581f8c6304bac6@mail.gmail.com> <615d78004495aebc53807156d04d988c@mail.gmail.com> <486f94a563d63c4779498fe8829a546c@mail.gmail.com> <602cee6381b9f435a938bbaf852d07f9@mail.gmail.com> <66256272c020be186becdd7a3f049302@mail.gmail.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 6 Sep 2018, Dou Liyang wrote: > At 09/05/2018 06:38 PM, Thomas Gleixner wrote: > > Oh well. This was not intended to magically provide the solution you want > > to have. It merily changed the behaviour of the managed interrupt > > selection, which is a valid thing to do independent of the stuff you want > > to see. > > > > Thank you for clarifying it, I will send the patch independently. > > > As I said that needs more thought and I really can't tell when I have a > > time slot to look at that. > > > > In this period, I am willing to be a volunteer to try to do that you > said in the previous reply. May I? You don't have to ask for permission. It's Open Source :) There are a few things we need to clarify upfront: Right now the pre and post vectors are marked managed and their affinity mask is set to the irq default affinity mask. The default affinity mask is by default ALL cpus, but it can be tweaked both on the kernel command line and via proc. If that mask is only a subset of CPUs and all of them go offline then these vectors are shutdown in managed mode. That means we need to set the affinity mask of the pre and post vectors to possible mask, but that doesn't make much sense either, unless there is a reason to have them marked managed. I think the right solution for these pre/post vectors is to _NOT_ mark them managed and leave them as regular interrupts which can be affinity controlled and also can move freely on hotplug. Christoph? Thanks, Thomas