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=-10.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham 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 624E7C07E9A for ; Wed, 14 Jul 2021 11:33:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3DB826128C for ; Wed, 14 Jul 2021 11:33:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239192AbhGNLgQ (ORCPT ); Wed, 14 Jul 2021 07:36:16 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:60702 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230164AbhGNLgP (ORCPT ); Wed, 14 Jul 2021 07:36:15 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1626262403; 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=EcaBntY+oSlhBqgrCZGx/dkv2Mafgo8FgMjqNZcerkg=; b=tfVwLL7KilpXwfngcy8oboF5AkXvv5s05Q4WOxT/DAaU+BtWaK2WAYtBsHA9VpiIuD9FJt +yKAuT48FqTUywKpzulm+uwMq53Jl4RdLNtfOgeFYIfbWlpcH/lNbZtqGgnlsQ8xaURLU9 q3SbTyC5wUC3cJZW46miadIsizbAxdWRPb9PxcGfcOfUKLbToGsizzUJz+P/sRDJOanevs 3ikP3dyKNmwleeuycnGjigxjgcO5YCXJcMu05rluhWzg2+mI84/pWZ8P/5XTVpbtONXGqu va2zeeomZgfWruiyDpnOmzPexTDjrSmHK/3ydt4d8fRjmFesZbl2cZ39bV89Qw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1626262403; 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=EcaBntY+oSlhBqgrCZGx/dkv2Mafgo8FgMjqNZcerkg=; b=Q9X5Zd3o/84fsKNWFpfFRmfvvvid5KIFc5EjTBeBhb3TUUeRlnF11Iheyg5qMKdlW87GwN xfTNrOIG4C73G3CQ== To: Peter Zijlstra Cc: LKML , Ingo Molnar , Juri Lelli , Steven Rostedt , Daniel Bristot de Oliveira , Will Deacon , Waiman Long , Boqun Feng , Sebastian Andrzej Siewior , Davidlohr Bueso Subject: Re: [patch 14/50] locking/rtmutex: Add wake_state to rt_mutex_waiter In-Reply-To: <20210714101831.GC2591@worktop.programming.kicks-ass.net> References: <20210713151054.700719949@linutronix.de> <20210713160747.320345860@linutronix.de> <20210714101831.GC2591@worktop.programming.kicks-ass.net> Date: Wed, 14 Jul 2021 13:33:23 +0200 Message-ID: <87lf69b058.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 Wed, Jul 14 2021 at 12:18, Peter Zijlstra wrote: > On Tue, Jul 13, 2021 at 05:11:08PM +0200, Thomas Gleixner wrote: >> @@ -33,6 +34,7 @@ struct rt_mutex_waiter { >> struct rb_node pi_tree_entry; >> struct task_struct *task; >> struct rt_mutex *lock; >> + int wake_state; >> int prio; >> u64 deadline; > > State is 'unsigned int', but we're (luckily) not yet at the MSB so it's > a bit moot, still... Still. Fixed locally