Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp871032imj; Fri, 15 Feb 2019 08:09:47 -0800 (PST) X-Google-Smtp-Source: AHgI3IZ8dpGSTNDSMcxPEpoGBJei35nlZPyiGs0R0Fxm2zSSxBG2J8Zsi8BS6dZ5DrG9l163dLLd X-Received: by 2002:a63:5d20:: with SMTP id r32mr6132293pgb.329.1550246987668; Fri, 15 Feb 2019 08:09:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550246987; cv=none; d=google.com; s=arc-20160816; b=lwSfJVKiR2lNloa85E0C+APGw299HBuppn5hKZz8IMdOhX3X7nAlgr9lZxq7IcLcn6 B0EUYTKWmXGXbHLE5OyTkb4l65vPBvaQmei04MxrLgxkVR3S7VvZxCAXIsJKS1r6PjKn O0BMMW5ivI+26SQNRGK3nqThfvVt0A2X9VbTnJvzMPyw3O4jKJbNq41airnCti0t64n4 8JxkVLtJhHWSuKlP4k2HYHJz/1X+6kL3MoPMVhNevgw/88hwhEU/XlBxRrVXSZYwI1sf 14rqvtobgt63KrhYNxwzkgovPQZx+Bs1K9t1wfbvF4cEC5fnzz2CpwHwVrXu4GUB0DXK EgiQ== 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:message-id :in-reply-to:date:references:subject:cc:to:from; bh=dRCSOM+05sb+WHOoPDdhBXHoNt8PgyIqhWlF79BiiLE=; b=wpLatPGoM9k6LqGJvjA1CPYKBgStY6yAw6xscJV/uRuCyv2nYMsn5NenQ0vctfj+N/ fAiagoabSKfBHhN8vH9RP024J8F8Iq69vwy+NaY2riZi1qFm24v3q4bPF/rNBGhG7B8V rUMybkIbl3mRkdfmDNmI3YsGJzIHEMpb7Qx1X4SDpXXAhfdhdFcpgj0E+ExdmzyFDhim uzuBeHZTKxDvqjklG9LMwrLJQzcx7a07JZlfk8VPce/kdzE6Pc+u6XIwBG8uVc7UjqXN 2CRQqxvK+JYfUlPqud3vZzt9E5HPYwxL00nqTjgMrRWIU7gqWP5ClOdEBKUao4FAu2NM wabQ== 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 v20si373368pgb.207.2019.02.15.08.09.30; Fri, 15 Feb 2019 08:09:47 -0800 (PST) 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 S2405970AbfBOK4Z (ORCPT + 99 others); Fri, 15 Feb 2019 05:56:25 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:52312 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726160AbfBOK4Z (ORCPT ); Fri, 15 Feb 2019 05:56:25 -0500 Received: from localhost ([127.0.0.1] helo=vostro.local) by Galois.linutronix.de with esmtp (Exim 4.80) (envelope-from ) id 1gubAH-0000xP-7K; Fri, 15 Feb 2019 11:56:17 +0100 From: John Ogness To: Petr Mladek Cc: linux-kernel@vger.kernel.org, Peter Zijlstra , Sergey Senozhatsky , Steven Rostedt , Daniel Wang , Andrew Morton , Linus Torvalds , Greg Kroah-Hartman , Alan Cox , Jiri Slaby , Peter Feiner , linux-serial@vger.kernel.org, Sergey Senozhatsky Subject: Re: [RFC PATCH v1 02/25] printk-rb: add prb locking functions References: <20190212143003.48446-1-john.ogness@linutronix.de> <20190212143003.48446-3-john.ogness@linutronix.de> <20190213154541.wvft64nf352vghou@pathway.suse.cz> <87pnrvs707.fsf@linutronix.de> <20190214103324.viexpifsyons5qya@pathway.suse.cz> <87y36ih8p7.fsf@linutronix.de> <20190215102635.kdo4yxifh5dt2yj7@pathway.suse.cz> Date: Fri, 15 Feb 2019 11:56:15 +0100 In-Reply-To: <20190215102635.kdo4yxifh5dt2yj7@pathway.suse.cz> (Petr Mladek's message of "Fri, 15 Feb 2019 11:26:35 +0100") Message-ID: <87y36hials.fsf@linutronix.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) 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 2019-02-15, Petr Mladek wrote: >>> void prb_lock(struct prb_cpulock *cpu_lock) >>> { >>> unsigned int flags; >>> int cpu; >> >> I added an explicit preempt_disable here: >> >> cpu = get_cpu(); > > It is superfluous. Preemption is not possible when interrupts > are disabled. Interrupts are not necessarily disabled here. They get disabled later if the lock needs to be taken (i.e. we are not nested). John Ogness