Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp817585iob; Wed, 18 May 2022 13:45:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxOvpycz2jfGWQ/e6Fly4yZlA0Cz/3aqp3VyGKmvNVEiZLWgCVAMukvCvUL+XErl5P464Sn X-Received: by 2002:a17:902:d2c9:b0:15e:b28d:8ad2 with SMTP id n9-20020a170902d2c900b0015eb28d8ad2mr1196056plc.94.1652906724484; Wed, 18 May 2022 13:45:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652906724; cv=none; d=google.com; s=arc-20160816; b=uy9DDnRHdAmMWajK3T48Qx7IO6JteokdMqAajYfbwbh/ZohjNn6/c8sSub+OVJDXxs 9xdp+A+NvI2r4WAsPzCb+HqoKe6+mMohs881woTjeTM6+FbqXSpIVK8UmSAfsYi7u+ri L5vEpo/Vcaq1B3hkfvQVf6tJk7/rw5zdM/5QycYSXX08olEJg+36lrnlqmeyezlFXlFe iCzP2wJvdo7Wof7DEyZoQVVgmohE3VW/FaxWdnqLMK5jfCzY+InFjkTXUkOxNsPsQFoX yHwaQAqXWtY+G0Dnuvivco9x3nnFg9BO/wQ7vEPt7uvvbYQzjagaX/pmDxEOgo3IPz9G s6rA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=/LqHVbHkRtSXSWgRorqDL1rnNBZq7KUPq1AfC0mPC/E=; b=nEyo17kdfss/jETBA2HhOOl7VCrISyXZrjO39knm49jgygkpOCv/x1qnkG3CWA2K9d aGyA6nx9Yafs94/OhOZmYCCrgUDJ/rwXJ7GxKsd+Wzk1juXdTvEVePOx24R9R9bc+t8N gIK4xHo12crE38/UWdWTFwTlkS+7+691QFGtcRe71bUo2pMrNpPMGbe2PMH/CdhoI1KJ Lk0DquA2B3ZwO8+Os/OkHg62aUWgjcKqoSy5PtXBeAadLGOnnasSuVDG828RzNgbWOCX SnyXWppJjk//lSkDaYZyO03C/UbetpizpqSUA6RI6t6FxoAyhrY6K1qPF2DLv12GNlQI XrCg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=NMSkahHu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id g18-20020a056a000b9200b0050a6c1711d7si4579777pfj.336.2022.05.18.13.45.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 May 2022 13:45:24 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=NMSkahHu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id B37886FD07; Wed, 18 May 2022 13:45:22 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242765AbiERUpQ (ORCPT + 99 others); Wed, 18 May 2022 16:45:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47606 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242734AbiERUpO (ORCPT ); Wed, 18 May 2022 16:45:14 -0400 Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 35B766FA3C for ; Wed, 18 May 2022 13:45:13 -0700 (PDT) Received: by mail-il1-x134.google.com with SMTP id b11so2338024ilr.4 for ; Wed, 18 May 2022 13:45:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/LqHVbHkRtSXSWgRorqDL1rnNBZq7KUPq1AfC0mPC/E=; b=NMSkahHunZrqlzsGNcFHRpOqRGdBCbPIwXcry9fcbtEaPi4EgWh/G3ORW/DTiJJCiR 2caHmsOY1o2oDg/Lq2mDZc44l7S2DvbYBa/xRoSOrGQLzLQ1VeJFugUH4DpTm/NOUEzQ 80JzEYq2mYF4QyVkFmhDPslstvCcA6ywYjLNGo9fWtOnlyLkkFYt3RSezI1KpaFPv3Tf KMc0lUlcgNA6WE2PCSt1FuIByXJXAoQfD43IljOLeBhBIrejNuY3OeOj96r8LgaG6DGv lcudB9Q/FZFVK06KTHbUVhpRwE6f/lRMJYv9f81dbzrujs5UvJTyJPX5/xJwZzoO4Bf2 dacg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/LqHVbHkRtSXSWgRorqDL1rnNBZq7KUPq1AfC0mPC/E=; b=aLbtl5pH6FTon+bBlHbqANQfQ1ZMklT215O8QVFZ0LCBvBoN5GbimmjxqzwA5eudcg WLUiaWkyyfYhTCdeHnBfgZ4lta04jjCYAwn1KzzWGs0TIsZ3LPRzeda48ikhpDd5b4Aa c/Yhih9AmxHHNuDGI7HVO+Ll2tdOpAFzesY/IKkP02In+rvF5le70nckqAl2RCDvzQzo ooOHYoQEstDdQEdVBjksu9OJ17dZE3mZwct1Jx9SupYLqhmYr4jMuiiDNU0vIphypX2h isvJjE8NzSwt7Z1Lw9t0aSHK/dPmm5GIKPw8A7JkB/O639LYJiQjQrkl62BbHL67qg4W JlsQ== X-Gm-Message-State: AOAM533MH1BhBSPPHA0bBNABzf/Uwe7eH7xPDwGbwKYSxGuMDOwMe/7U pLUqx+gHVBHJKf17cZoX+PbWydCfN1+aZGGvh8QXgg== X-Received: by 2002:a92:cc11:0:b0:2d1:129:e1e9 with SMTP id s17-20020a92cc11000000b002d10129e1e9mr851387ilp.211.1652906712429; Wed, 18 May 2022 13:45:12 -0700 (PDT) MIME-Version: 1.0 References: <20220518175002.GA1148748@bhelgaas> In-Reply-To: From: Tanjore Suresh Date: Wed, 18 May 2022 13:45:01 -0700 Message-ID: Subject: Re: [PATCH v3 1/3] driver core: Support asynchronous driver shutdown To: "Rafael J. Wysocki" Cc: Bjorn Helgaas , Greg Kroah-Hartman , Christoph Hellwig , Sagi Grimberg , Bjorn Helgaas , Linux Kernel Mailing List , linux-nvme , Linux PCI Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-9.5 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE, USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Rafeal, On Wed, May 18, 2022 at 11:01 AM Rafael J. Wysocki wrote: > > On Wed, May 18, 2022 at 7:50 PM Bjorn Helgaas wrote: > > > > On Wed, May 18, 2022 at 01:38:49PM +0200, Rafael J. Wysocki wrote: > > > On Wed, May 18, 2022 at 12:08 AM Tanjore Suresh wrote: > > > > > > > > This changes the bus driver interface with additional entry points > > > > to enable devices to implement asynchronous shutdown. The existing > > > > synchronous interface to shutdown is unmodified and retained for > > > > backward compatibility. > > > > > > > > This changes the common device shutdown code to enable devices to > > > > participate in asynchronous shutdown implementation. > > > > > > > > Signed-off-by: Tanjore Suresh > > > > --- > > > > drivers/base/core.c | 38 +++++++++++++++++++++++++++++++++++++- > > > > include/linux/device/bus.h | 12 ++++++++++++ > > > > 2 files changed, 49 insertions(+), 1 deletion(-) > > > > > > > > diff --git a/drivers/base/core.c b/drivers/base/core.c > > > > index 3d6430eb0c6a..ba267ae70a22 100644 > > > > --- a/drivers/base/core.c > > > > +++ b/drivers/base/core.c > > > > @@ -4479,6 +4479,7 @@ EXPORT_SYMBOL_GPL(device_change_owner); > > > > void device_shutdown(void) > > > > { > > > > struct device *dev, *parent; > > > > + LIST_HEAD(async_shutdown_list); > > > > > > > > wait_for_device_probe(); > > > > device_block_probing(); > > > > @@ -4523,7 +4524,13 @@ void device_shutdown(void) > > > > dev_info(dev, "shutdown_pre\n"); > > > > dev->class->shutdown_pre(dev); > > > > } > > > > - if (dev->bus && dev->bus->shutdown) { > > > > + if (dev->bus && dev->bus->async_shutdown_start) { > > > > + if (initcall_debug) > > > > + dev_info(dev, "async_shutdown_start\n"); > > > > + dev->bus->async_shutdown_start(dev); > > > > + list_add_tail(&dev->kobj.entry, > > > > + &async_shutdown_list); > > > > + } else if (dev->bus && dev->bus->shutdown) { > > > > if (initcall_debug) > > > > dev_info(dev, "shutdown\n"); > > > > dev->bus->shutdown(dev); > > > > @@ -4543,6 +4550,35 @@ void device_shutdown(void) > > > > spin_lock(&devices_kset->list_lock); > > > > } > > > > spin_unlock(&devices_kset->list_lock); > > > > + > > > > + /* > > > > + * Second pass spin for only devices, that have configured > > > > + * Asynchronous shutdown. > > > > + */ > > > > + while (!list_empty(&async_shutdown_list)) { > > > > + dev = list_entry(async_shutdown_list.next, struct device, > > > > + kobj.entry); > > > > + parent = get_device(dev->parent); > > > > + get_device(dev); > > > > + /* > > > > + * Make sure the device is off the list > > > > + */ > > > > + list_del_init(&dev->kobj.entry); > > > > + if (parent) > > > > + device_lock(parent); > > > > + device_lock(dev); > > > > + if (dev->bus && dev->bus->async_shutdown_end) { > > > > + if (initcall_debug) > > > > + dev_info(dev, > > > > + "async_shutdown_end called\n"); > > > > + dev->bus->async_shutdown_end(dev); > > > > + } > > > > + device_unlock(dev); > > > > + if (parent) > > > > + device_unlock(parent); > > > > + put_device(dev); > > > > + put_device(parent); > > > > + } > > > > } > > > > > > > > /* > > > > diff --git a/include/linux/device/bus.h b/include/linux/device/bus.h > > > > index a039ab809753..f582c9d21515 100644 > > > > --- a/include/linux/device/bus.h > > > > +++ b/include/linux/device/bus.h > > > > @@ -49,6 +49,16 @@ struct fwnode_handle; > > > > * will never get called until they do. > > > > * @remove: Called when a device removed from this bus. > > > > * @shutdown: Called at shut-down time to quiesce the device. > > > > + * @async_shutdown_start: Called at the shutdown-time to start > > > > + * the shutdown process on the device. > > > > + * This entry point will be called only > > > > + * when the bus driver has indicated it would > > > > + * like to participate in asynchronous shutdown > > > > + * completion. > > > > + * @async_shutdown_end: Called at shutdown-time to complete the shutdown > > > > + * process of the device. This entry point will be called > > > > + * only when the bus drive has indicated it would like to > > > > + * participate in the asynchronous shutdown completion. > > > > > > I'm going to repeat my point here, but only once. > > > > > > I see no reason to do async shutdown this way, instead of adding a > > > flag for drivers to opt in for calling their existing shutdown > > > callbacks asynchronously, in analogy with the async suspend and resume > > > implementation. > > > > There's a lot of code here that mere mortals like myself don't > > understand very well, so here's my meager understanding of how > > async suspend works and what you're suggesting to make this a > > little more concrete. > > > > Devices have this async_suspend bit: > > > > struct device { > > struct dev_pm_info { > > unsigned int async_suspend:1; > > > > Drivers call device_enable_async_suspend() to set async_suspend if > > they want it. The system suspend path is something like this: > > > > suspend_enter > > dpm_suspend_noirq(PMSG_SUSPEND) > > dpm_noirq_suspend_devices(PMSG_SUSPEND) > > pm_transition = PMSG_SUSPEND > > while (!list_empty(&dpm_late_early_list)) > > device_suspend_noirq(dev) > > dpm_async_fn(dev, async_suspend_noirq) > > if (is_async(dev)) > > async_schedule_dev(async_suspend_noirq) # async path > > > > async_suspend_noirq # called asynchronously > > __device_suspend_noirq(dev, PMSG_SUSPEND, true) > > callback = pm_noirq_op(PMSG_SUSPEND) # .suspend_noirq() > > dpm_run_callback(callback) # async call > > > > __device_suspend_noirq(dev, pm_transition, false) # sync path > > callback = pm_noirq_op(PMSG_SUSPEND) # .suspend_noirq() > > dpm_run_callback(callback) # sync call > > > > async_synchronize_full # wait > > > > If a driver has called device_enable_async_suspend(), we'll use the > > async_schedule_dev() path to schedule the appropriate .suspend_noirq() > > method. After scheduling it via the async path or directly calling it > > via the sync path, the async_synchronize_full() waits for completion > > of all the async methods. > > > > I assume your suggestion is to do something like this: > > > > struct device { > > struct dev_pm_info { > > unsigned int async_suspend:1; > > + unsigned int async_shutdown:1; > > > > + void device_enable_async_shutdown(struct device *dev) > > + dev->power.async_shutdown = true; > > > > device_shutdown > > while (!list_empty(&devices_kset->list)) > > - dev->...->shutdown() > > + if (is_async_shutdown(dev)) > > + async_schedule_dev(async_shutdown) # async path > > + > > + async_shutdown # called asynchronously > > + dev->...->shutdown() > > + > > + else > > + dev->...->shutdown() # sync path > > + > > + async_synchronize_full # wait > > Yes, that's the idea IIUC. Thanks for the clarification, I misunderstood your earlier comment, thanks for explaining and clarification. Let me evaluate and get back to you as soon as possible. Thanks sureshtk