Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp380166ybl; Fri, 23 Aug 2019 02:13:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqzDShlbCQ5eP6SPvJLCldhCRY6x9gNHxMGpf2XOl5I3dj/WW9V0wRcomGZFwuh4H81OyKDc X-Received: by 2002:aa7:9477:: with SMTP id t23mr4106590pfq.29.1566551616263; Fri, 23 Aug 2019 02:13:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566551616; cv=none; d=google.com; s=arc-20160816; b=zGgX3QNqlILAor6kp6OPD8ug45kXcHRkWlILTiJgC8Gs5aB+0pH6g4rN9zDjMS3w4m xV3BCawbLg1q/LeNJPscwXfTByx+5LjWvbwLXpdTFPrnZj1e9ualjvIDmnR8OC8yjW4K A4Ah0q5EM52Kw8gxg4cj+P5yf56KcG+htWpD1ufq9KUiyefdTvghIwuCtMkvC82+E+sv fy64ac6e7SIH61NUFsVP/gh4ds4hII501+Ryizbm3UjUZgGKzfEX0gh4C4HvwjvUj4wG 8R6gNwTJlPqGR3sMKqkb033rgZ4YQV5kzU4GplY58UKbIPtZDHdlFtqvLSsOWJTx9XKr McSw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=hzy36hhVXFi6wqDa1Z1jG9B3/csgmeqFSkjTTR5TT8o=; b=I/DJu3NcAcmpJpVVumWbyi6iHg8hHZ3Em0uRzYSgNKoZOSdn8qau03LVX1+oKJ0Nof cSEd/IJSQTpsXuVWp2daq9vlI1ck9OxuQSMYyLuSdhqgifUcHjC9HuCztFFNg9zy4p58 ce6k3qe5bEpAormiVapHHi0cPxLiQJ16onRkVOICD8tDPbceB+dnENFzKBRTi1/9/KXK d355sx1hxnhAFWVjD4OjdASIpJK3Dy8pJjVK9ej9Ehl2NVdii48VUhppQBsfBFgJe6ke dkFc1Lv5CPbm58hAXWTdKoYfcR5fN2vAyB+SteqImfXIu0nJclZoDpcLXYymJ17JUheP JXrQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=hYL+u0eQ; 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 x130si1474021pgx.526.2019.08.23.02.13.20; Fri, 23 Aug 2019 02:13:36 -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; dkim=pass header.i=@joelfernandes.org header.s=google header.b=hYL+u0eQ; 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 S1732394AbfHWAwW (ORCPT + 99 others); Thu, 22 Aug 2019 20:52:22 -0400 Received: from mail-pg1-f193.google.com ([209.85.215.193]:40325 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730401AbfHWAwW (ORCPT ); Thu, 22 Aug 2019 20:52:22 -0400 Received: by mail-pg1-f193.google.com with SMTP id w10so4697615pgj.7 for ; Thu, 22 Aug 2019 17:52:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=hzy36hhVXFi6wqDa1Z1jG9B3/csgmeqFSkjTTR5TT8o=; b=hYL+u0eQoTbpWIVtYnginblV5imhgI8XxMCyi9l7/HBpQMrxDA/vdrxCnNultRSBkY P5JMBNUxfa2VHB72aDX+cgK5x5Pg+SVWjdRnWHlGNng1tFEMrua/lr9A/QngXcR9+PIr z8i7RNwUNfD9CTp7+geP9YlxQpiKIiEyRI9jk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=hzy36hhVXFi6wqDa1Z1jG9B3/csgmeqFSkjTTR5TT8o=; b=X5w9Uc+DZp09/NBqgzX9287NoqLKKyZ5klu1TAzznGXBMBYP+yGE32fILS7bc5bmkh uqctiKWKQf3y46N475ewptKxNjhmz8DHWROXAIhRD5/7FzipjQeEn37g/3Lndz2X6rgc bz6O0Rob6byHejVHRZOp/LjRifciRBXDgMmxGBBtXOOWN4APp+qAj8ZwqK7Tm76Ig8vv 1/DV+wcDWKYnxYMk3AuLOiqQx0ZNlezYwCyHyDptEbqKiOfjMMTirnp+Ls/KTTE/3yKX Yqa7CwgcuJdF74x/4IncTH4/HS2Noi5uXSVYzTbWNetlcMcQyumrFH84zLec9xDY07nx Al9g== X-Gm-Message-State: APjAAAX8xDt2UWS2Sokq76hv7Ke/UGhssByMmYv5BrVTw0Ng2dZsLOb5 /sufZBrszdoAqmjLgVC0+6Lnsd7m8Ew= X-Received: by 2002:a63:7d49:: with SMTP id m9mr1704700pgn.161.1566521540968; Thu, 22 Aug 2019 17:52:20 -0700 (PDT) Received: from localhost ([2620:15c:6:12:9c46:e0da:efbf:69cc]) by smtp.gmail.com with ESMTPSA id g1sm460656pgg.27.2019.08.22.17.52.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 22 Aug 2019 17:52:20 -0700 (PDT) Date: Thu, 22 Aug 2019 20:52:18 -0400 From: Joel Fernandes To: Scott Wood Cc: Sebastian Andrzej Siewior , linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org, "Paul E . McKenney" , Thomas Gleixner , Peter Zijlstra , Juri Lelli , Clark Williams Subject: Re: [PATCH RT v2 3/3] rcu: Disable use_softirq on PREEMPT_RT Message-ID: <20190823005218.GA36261@google.com> References: <20190821231906.4224-1-swood@redhat.com> <20190821231906.4224-4-swood@redhat.com> <20190822135953.GB29841@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 22, 2019 at 02:31:17PM -0500, Scott Wood wrote: > On Thu, 2019-08-22 at 09:59 -0400, Joel Fernandes wrote: > > On Wed, Aug 21, 2019 at 06:19:06PM -0500, Scott Wood wrote: > > > I think the prohibition on use_softirq can be dropped once RT gets the > > > latest RCU code, but the question of what use_softirq should default > > > to on PREEMPT_RT remains. > > > > Independent of the question of what use_softirq should default to, could > > we > > test RT with latest RCU code now to check if the deadlock goes away? That > > way, maybe we can find any issues in current RCU that cause scheduler > > deadlocks in the situation you pointed. The reason I am asking is because > > recently additional commits [1] try to prevent deadlock and it'd be nice > > to > > ensure that other conditions are not lingering (I don't think they are but > > it'd be nice to be sure). > > > > I am happy to do such testing myself if you want, however what does it > > take > > to apply the RT patchset to the latest mainline? Is it an achievable feat? > > I did run such a test (cherry picking all RCU patches that aren't already in > RT, plus your RFC patch to rcu_read_unlock_special, rather than applying RT > to current mainline) with rcutorture plus a looping kernel build overnight, > and didn't see any splats with or without use_softirq. Cool, that's good to know you didn't see splats! thanks, - Joel