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=-13.2 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_IN_DEF_DKIM_WL autolearn=no 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 0CF62C43460 for ; Thu, 29 Apr 2021 17:00:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E10BF61441 for ; Thu, 29 Apr 2021 17:00:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240888AbhD2RBJ (ORCPT ); Thu, 29 Apr 2021 13:01:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45914 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240852AbhD2RBG (ORCPT ); Thu, 29 Apr 2021 13:01:06 -0400 Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1E050C06138B for ; Thu, 29 Apr 2021 10:00:19 -0700 (PDT) Received: by mail-lj1-x232.google.com with SMTP id m7so66446053ljp.10 for ; Thu, 29 Apr 2021 10:00:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=f0HDs304V6rBQyJsC5AJ9JCDtTKnf5YiKXTX64eRPok=; b=ExZEkvb48KmMdff51m5EllB7RqJi7o96Jtn3zE3fRmXGBVkDfzxzZmLnWIq5F+BdEM q6cz07f9ztPJ3Y+jdlGik9OM0RnI/rho9TYwV1UhXhrBQA6aDsNZTG7hRI26Qc0ryVgj gQavAami2VG0lmlSiImr4AagqgDrhqmLkFypq6RtwXc83dhxlenMhB+LDhHVLNIMURfI fTSEu8MjopjkR03N++XlTEGNOFm1cTZu1KKiLdMtCngzZHV6ntqCm1+Hop9fah1h5JbZ Zsm2slRg6nDEOwvT6Zr/IdzMWQW9c4v0uSIKofH2VEpAtrDCEOAnIkyePqrkjvIveyFP Da2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=f0HDs304V6rBQyJsC5AJ9JCDtTKnf5YiKXTX64eRPok=; b=phSZv8dp9qlzSmY1gNJD8+TSI3oMCxDlp8l6W/1J8o0PMsg0oviQExrN78dcReBQi0 8QmSSrY0hPL9tgg9ujWA+XuXIrEHTRTN2NydsfLgXNNnzKDR3XaoB16hZ9y7gIOf4xnP ksru983SYn5mf7PluQhobDOzgmopQ4/9r8ygA5QuoPbUd/lYQ/c97mKWBibdweF3Z/Cr RXnZg4ZncqMpvtFOK1LY4RmAL1HqAXrTfaT1yi8mYyWdisaKM6dFNoA8b4CJSOU7Qw7K BvAVakn/VFHxUtSJXg4PificOJYrjeTm7WOKhSyGmYwwntU5dL/ZsGrbsYV6UKZwyDGL DSnA== X-Gm-Message-State: AOAM5307WJn0bKjOlxKvzwdHQG3mV+x3TFvqQwHn30DJ3dWGUUCacXa9 hS26xeu65VLzsHoXrr4xEmfOKqRHrC6B0twhZJbo4g== X-Google-Smtp-Source: ABdhPJw+ESSs7VTM3JdnNUYO1nFYP+5xozFj+wC6Na197QlKwaCYJN5flP6NE6Ly3ROztBiNyG6qGBwyM8dd8acjBKQ= X-Received: by 2002:a05:651c:50b:: with SMTP id o11mr431200ljp.323.1619715617399; Thu, 29 Apr 2021 10:00:17 -0700 (PDT) MIME-Version: 1.0 References: <20210424021631.1972022-1-rajatja@google.com> <20210424021631.1972022-2-rajatja@google.com> <79b994f2476249498797e1784f735fd7@AcuMS.aculab.com> <21c6b5002c5ad36cd7fe0bb849f5eba12a614bca.camel@suse.com> <0601e45130495b152bec04eee4a50e302db4cfd2.camel@suse.com> <5ac7634acbe7569879234ad541879c79918f3e00.camel@suse.com> In-Reply-To: From: Rajat Jain Date: Thu, 29 Apr 2021 09:59:39 -0700 Message-ID: Subject: Re: [PATCH v2 2/2] pci: Support "removable" attribute for PCI devices To: "Rafael J. Wysocki" Cc: Oliver Neukum , David Laight , Greg Kroah-Hartman , Bjorn Helgaas , Alan Stern , Linux Kernel Mailing List , Linux PCI , "open list:ULTRA-WIDEBAND (UWB) SUBSYSTEM:" , Bjorn Helgaas , Rajat Jain , Jesse Barnes , Dmitry Torokhov Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 29, 2021 at 2:58 AM Rafael J. Wysocki wrote: > > On Thu, Apr 29, 2021 at 11:03 AM Oliver Neukum wrote: > > > > Am Mittwoch, den 28.04.2021, 14:21 +0200 schrieb Rafael J. Wysocki: > > > > > In principle, in the wake of Thunderbolt every PCI driver handling > > > PCIe devices needs to be able to deal with a device that's gone away > > > without notice, because in principle any PCIe device can be included > > > into a Thunderbolt docking station which may go away as a whole > > > without notice. > > > > Yes, but we are dealing with what we export to user space, don't we? > > Right, so it would be good to know why exporting this information to > user space is desired. For us, the driving motivation is to implement policies in userspace for user removable devices. Eg: * Tracking the statistics around usage of user removable devices (how many users use such devices, how often etc). * Removing user removable devices when a user logs out. * Not allowing a new user removable device while the screen is locked. * (perhaps additional such policies in future). Thanks, Rajat