Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp1007261pxb; Thu, 4 Feb 2021 02:44:27 -0800 (PST) X-Google-Smtp-Source: ABdhPJz80EKrASZRK1NKbYpMMMmpkZmU0OyjyY+QV78ZA6IQZi9WTpM2nYTedZvnPzRHeAyHziIu X-Received: by 2002:a17:906:7cd8:: with SMTP id h24mr7178459ejp.511.1612435467357; Thu, 04 Feb 2021 02:44:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612435467; cv=none; d=google.com; s=arc-20160816; b=rxP9imT5kw9PWCxNnnjJShWnyMNfUx2QJnnK81cbl0szXx2o2pYkJDYnMox2ysS3Yo 91WL8k/EdBNsUq7HGHr+glFy4nAUANSBsrwbROzpnZtyree3ZfpAVwEdDBdz/2bUjrB1 8IxXpOXd3CZL4zbsJHphspPHkxc8X6sfF5cdtg1oSdteMxoZiUBToF3WmRs4YYXULz82 qkuz5D5RS4Z29dLeOQhARc4WYIeLdTP4F8yQOKsZJT1HU9W87f5bbNyj5FQ/KWys7qxZ 4qs6EeThGFplNw5yH1+noP/R7d87CpVCFqD2nVeeFH+2LCXFvY2oppDjD8hbnnC+Q1a2 rKXg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=HJczz7TirwT+a287cR8pV5BaQuEtmn4mWyLNex7LbjA=; b=Y2CsLRRsXOhfNIgs/HV1E7QAepJz+jfvn9FxGzLc1CJghGyQZvFaUAvywTkKhhBO4Q tIyBixdesW79JnJ4clJIa6DMZ086kjPapKLBMwA1fUc3okQiIQrGojUq+LcmG6LCRgOx IK9wTRps3LxtnHDkTxLsfDzL1zbVtPkwBpk2i+DlV0Mm7kM65Z7WYwr6mKuqftoVH82q SPgadW5l6IahsvNOwA30MBbogrfo/6RyZseAHvBeT6TScur4pOcskfHoX8lx0T9sAmTO SW9c95L+pVByorrLB4NKOW3Q2RyzQz2PrIM74jRm5togu+6jdQQ0CPI0S4Y8lmyBPDAF LKeg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=PqGL1T1t; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dj14si2803380edb.210.2021.02.04.02.44.01; Thu, 04 Feb 2021 02:44:27 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=PqGL1T1t; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235317AbhBDKkw (ORCPT + 99 others); Thu, 4 Feb 2021 05:40:52 -0500 Received: from mail.kernel.org ([198.145.29.99]:45136 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234895AbhBDKku (ORCPT ); Thu, 4 Feb 2021 05:40:50 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id F369364F4D; Thu, 4 Feb 2021 10:40:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1612435208; bh=CQyj/sSo8xI867DsxS1WdYQhB65eb22naaawqQg/afc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=PqGL1T1ttXRGVzH/yHU8sj3tqnaejolVmxip/w/tP51DDu+51kPsjS2hFtgXcKfvv B2PllRqUiyK/DRLQrT3di2iNITlcDSmeKcE+YQgdXPjm3uJNJSVkxAenDOs2v863Vh Uw9Y9XP6eQkyNxCniCf+Rp9QgRJ8UrEsTYn/6Qm8= Date: Thu, 4 Feb 2021 11:40:04 +0100 From: Greg Kroah-Hartman To: Niklas Schnelle Cc: Bjorn Helgaas , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, Peter Oberparleiter , Viktor Mihajlovski Subject: Re: [RFC v2 1/1] PCI: Add s390 specific UID uniqueness attribute Message-ID: References: <20210204094353.63819-1-schnelle@linux.ibm.com> <20210204094353.63819-2-schnelle@linux.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210204094353.63819-2-schnelle@linux.ibm.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 04, 2021 at 10:43:53AM +0100, Niklas Schnelle wrote: > The global UID uniqueness attribute exposes whether the platform > guarantees that the user-defined per-device UID attribute values > (/sys/bus/pci/device//uid) are unique and can thus be used as > a global identifier for the associated PCI device. With this commit > it is exposed at /sys/bus/pci/zpci/unique_uids > > Signed-off-by: Niklas Schnelle > --- > Documentation/ABI/testing/sysfs-bus-pci | 9 +++++++++ > drivers/pci/pci-sysfs.c | 21 +++++++++++++++++++++ > 2 files changed, 30 insertions(+) > > diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci > index 25c9c39770c6..812dd9d3f80d 100644 > --- a/Documentation/ABI/testing/sysfs-bus-pci > +++ b/Documentation/ABI/testing/sysfs-bus-pci > @@ -375,3 +375,12 @@ Description: > The value comes from the PCI kernel device state and can be one > of: "unknown", "error", "D0", D1", "D2", "D3hot", "D3cold". > The file is read only. > +What: /sys/bus/pci/zpci/unique_uids No blank line before this new line? And why "zpci"? > +Date: February 2021 > +Contact: Niklas Schnelle > +Description: > + This attribute exposes the global state of UID Uniqueness on an > + s390 Linux system. If this file contains '1' the per-device UID > + attribute is guaranteed to provide a unique user defined > + identifier for that PCI device. If this file contains '0' UIDs > + may collide and do not provide a unique identifier. What are they "colliding" with? And where does the UID come from, the device itself or somewhere else? thanks, greg k-h