From: Sean Christopherson <seanjc@google.com>
To: Josh Hilke <jrhilke@google.com>
Cc: Alex Williamson <alex@shazbot.org>,
David Matlack <dmatlack@google.com>,
Vipin Sharma <vipinsh@google.com>,
Raghavendra Rao Ananta <rananta@google.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] vfio: selftests: Find devices that have VFIO selftest drivers
Date: Fri, 8 May 2026 11:17:12 -0700 [thread overview]
Message-ID: <af4oqOB-zXgVgkLf@google.com> (raw)
In-Reply-To: <20260414230943.41198-2-jrhilke@google.com>
On Tue, Apr 14, 2026, Josh Hilke wrote:
> +# Print the segment:bus:device.function numbers of PCI devices that can be used
> +# to run VFIO selftests.
> +function main() {
> + local vendor_device_id
> +
> + for vendor_device_id in "${DEVICES[@]}"; do
> + lspci -D -d "${vendor_device_id}" | awk '{print $1}'
For ignorant people like me, it would be helpful to capture what device was actually
found. I mean, I don't necessarily know exactly what these devices do, but as the
list grows, at least having a general sense of what device I'm going to be feeding
into VFIO would be helpful.
E.g. something like this (ignore my terrible script skills)?
#!/bin/bash
# SPDX-License-Identifier: GPL-2.0-or-later
# List of devices which have a VFIO selftest driver
DEVICES=(
"8086:0b25","Intel SPR DSA"
"8086:11fb","Intel GNR-D DSA"
"8086:1212","Intel DR DSA"
"8086:0cf8","Intel CBDMA"
)
# Print the segment:bus:device.function numbers of PCI devices that can be used
# to run VFIO selftests.
function main() {
local found
local i
OLDIFS=$IFS
IFS=','
for i in "${DEVICES[@]}"; do
set -- $i
found=$(lspci -D -d "$1" | cut -f 1 -d ' ')
if [[ -n $found ]]; then
echo "$2 ($1) Device IDs:"
echo $found
fi
done
IFS=$OLDIFS
}
main
# ./devices.sh
Intel SPR DSA (8086:0b25) Device IDs:
0000:6a:01.0
0000:6f:01.0
0000:74:01.0
0000:79:01.0
0000:e7:01.0
0000:ec:01.0
0000:f1:01.0
0000:f6:01.0
> + done
> +}
> +
> +main "$@"
Why pass along args? The script doesn't actually recognize any arguments.
> --
> 2.54.0.rc0.605.g598a273b03-goog
>
next prev parent reply other threads:[~2026-05-08 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 23:09 [PATCH v2 0/1] vfio: selftests: Find devices that have VFIO selftest drivers Josh Hilke
2026-04-14 23:09 ` [PATCH v2 1/1] " Josh Hilke
2026-04-16 23:35 ` David Matlack
2026-05-08 18:17 ` Sean Christopherson [this message]
2026-05-08 22:03 ` Josh Hilke
2026-05-08 22:20 ` Sean Christopherson
2026-05-08 22:49 ` David Matlack
2026-05-11 16:12 ` Josh Hilke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af4oqOB-zXgVgkLf@google.com \
--to=seanjc@google.com \
--cc=alex@shazbot.org \
--cc=dmatlack@google.com \
--cc=jrhilke@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rananta@google.com \
--cc=vipinsh@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.