linux-kernel - Re: [PATCH v4 2/3] PCI: Allow specifying devices using a base bus and path of devfns

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <f4bbe0f2-1087-c626-7776-a4fb6b5457c8@infradead.org>
Date:   Fri, 22 Jun 2018 14:33:34 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Logan Gunthorpe <logang@...tatee.com>,
        linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
        linux-doc@...r.kernel.org
Cc:     Stephen Bates <sbates@...thlin.com>,
        Christoph Hellwig <hch@....de>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Jonathan Corbet <corbet@....net>,
        Ingo Molnar <mingo@...nel.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
        Marc Zyngier <marc.zyngier@....com>,
        Kai-Heng Feng <kai.heng.feng@...onical.com>,
        Frederic Weisbecker <frederic@...nel.org>,
        Dan Williams <dan.j.williams@...el.com>,
        Jérôme Glisse <jglisse@...hat.com>,
        Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        Alex Williamson <alex.williamson@...hat.com>,
        Christian König <christian.koenig@....com>,
        Matthew Wilcox <willy@...radead.org>
Subject: Re: [PATCH v4 2/3] PCI: Allow specifying devices using a base bus and
 path of devfns

On 06/22/2018 01:50 PM, Logan Gunthorpe wrote:
> 
> 
> On 22/06/18 02:01 PM, Randy Dunlap wrote:
>>> Thus, we add an option to specify devices in the following format:
>>>
>>> [<domain>:]<bus>:<slot>.<func>[/<slot>.<func>]*
>>
>> Please explain the trailing '*'.  I looked thru the code and it doesn't
>> seem to look for it or care.
> 
> This was Willy's suggestion and I liked it. It's similar to regular
> expression syntax: the '*' indicating you may have any number of the
> expression repeated in the square brackets.

Oh, OK.  I can do that syntax, I just didn't know that this was
using that notation.

Hopefully admins can read it that way.

-- 
~Randy