Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp6617026ybp; Tue, 15 Oct 2019 18:39:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqw7PiMIZeLlqtloeS/1K3fa92fyAnrImDI2wxAvQazNuJJ9Qlth90Y8ck+SMbKcRaCVu96T X-Received: by 2002:a17:906:480a:: with SMTP id w10mr37362296ejq.212.1571189967267; Tue, 15 Oct 2019 18:39:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571189967; cv=none; d=google.com; s=arc-20160816; b=gDk4rw2QeMgKCygBfqz62T+XScFt5XzCBW9bP3A+hlgvzzEO6YPmTncSPFez/FcxGP SRYWUpgR5FLlFKzavk79Ez8fTO5DYkcj2sN2mDcT0+BRmqeNgOO9UqXK8OBDNJUb5uAl EOAkpZ8ClQbvj1JND+/Xwio+LT7kBwsUEo1ATe94J+dAMjjytof7OvMcFQRTOcPEbwrb io7/A1J7ZI6G8WHn5fOwisaliDH78vNZItwRyEPMhgEJHTT3PDKFZFpowlObIFgYXx0j oXdSArUIuBr6DCe1n1og62KY/jMMs5JYNrbP81rT/sEpMt4eR0JFneMAiS/ok4vwNK/e /P3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=eNx73Kw8ynvu+lEgVpSyFt+Om4vT4ydv9Tan4mpIPm0=; b=AQ761/Moa65umqqgB4Mf90If17exIi1BSrTiyp1Ff5+cpT3FjQQRUr/dAGZGr57z0r pkDk8XLMGlppnyR5NU47Nhi93rQf3YyI+uUO/g8pQvAZ1u+EwYhlGpAPp983DHHigDyX yFzhuQ+2Ybp6JAxpb3pjquBENFKalwdphHq8jDEazmGvuTLDPBA2IogAd7cQh2YL33Lt 4r8qbYXLlBl4raMb7p9h+4KHQmbs5UbrFxaLZ+DL+adXlCNoWKqcs8mYxp0iheBLVECI 9vAOcQHvB4B8MtLqFzyGKqLpa3upWokKPgUTg0+iM6EEA3R4o1VtW9SNY8ZXjHhNwyJt W1NA== 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 b30si16632455eda.200.2019.10.15.18.39.04; Tue, 15 Oct 2019 18:39:27 -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 S2389505AbfJOTS4 (ORCPT + 99 others); Tue, 15 Oct 2019 15:18:56 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:45716 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389468AbfJOTSv (ORCPT ); Tue, 15 Oct 2019 15:18:51 -0400 Received: from localhost ([127.0.0.1] helo=localhost.localdomain) by Galois.linutronix.de with esmtp (Exim 4.80) (envelope-from ) id 1iKSLF-00067i-SH; Tue, 15 Oct 2019 21:18:46 +0200 From: Sebastian Andrzej Siewior To: linux-kernel@vger.kernel.org Cc: tglx@linutronix.de, Sebastian Andrzej Siewior , Tejun Heo , Lai Jiangshan Subject: [PATCH 34/34] workqueue: Use PREEMPTION Date: Tue, 15 Oct 2019 21:18:21 +0200 Message-Id: <20191015191821.11479-35-bigeasy@linutronix.de> In-Reply-To: <20191015191821.11479-1-bigeasy@linutronix.de> References: <20191015191821.11479-1-bigeasy@linutronix.de> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org CONFIG_PREEMPTION is selected by CONFIG_PREEMPT and by CONFIG_PREEMPT_RT. Both PREEMPT and PREEMPT_RT require the same functionality which today depends on CONFIG_PREEMPT. Update the comment to use PREEMPTION because it is true for both preemption models. Cc: Tejun Heo Cc: Lai Jiangshan Signed-off-by: Sebastian Andrzej Siewior --- kernel/workqueue.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/workqueue.c b/kernel/workqueue.c index bc2e09a8ea61d..a668b2118539c 100644 --- a/kernel/workqueue.c +++ b/kernel/workqueue.c @@ -2285,7 +2285,7 @@ __acquires(&pool->lock) } =20 /* - * The following prevents a kworker from hogging CPU on !PREEMPT + * The following prevents a kworker from hogging CPU on !PREEMPTION * kernels, where a requeueing work item waiting for something to * happen could deadlock with stop_machine as such work item could * indefinitely requeue itself while all other CPUs are trapped in --=20 2.23.0