From: Alex Mastro <amastro@fb.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Alex Mastro <amastro@fb.com>, <peterx@redhat.com>,
<kbusch@kernel.org>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] vfio/pci: print vfio-device name to fdinfo
Date: Mon, 23 Jun 2025 16:14:48 -0700 [thread overview]
Message-ID: <20250623231450.1326244-1-amastro@fb.com> (raw)
In-Reply-To: <20250623161831.12109402.alex.williamson@redhat.com>
Hi Alex, thanks for the prompt feedback.
On Mon, 23 Jun 2025 16:18:31 -0600 Alex Williamson <alex.williamson@redhat.com> wrote:
> TBH, I don't think we need a callback, just use dev_name() in
> vfio_main. The group interface always requires the name, in some cases
> it can require further information, but we seem to have forgotten that
> in the cdev interface anyway :-\
Sounds good -- I'll follow up on this in v2.
> > +#include <linux/seq_file.h>
>
> Only where we're doing the seq_print do we need to include this.
Ah, I only added it due to the direct reference to `struct seq_file *` in this
file, but will keep this in mind. I do see that it's transitively visible via
vfio.h's include.
> I think you're missing an update to Documentation/filesystems/proc.rst
> as well.
TIL about this documentation (section 3.8), but it looks to be focused more on
common fs/* pieces like eventfd, signalfd, and such. I didn't see any drivers/*
precedence, but would not be opposed to being the first. Do you think it still
makes sense to add there?
Thanks,
Alex
next prev parent reply other threads:[~2025-06-23 23:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 21:02 Alex Mastro
2025-06-23 21:50 ` Keith Busch
2025-06-23 22:18 ` Alex Williamson
2025-06-23 23:14 ` Alex Mastro [this message]
2025-06-24 0:56 ` Jason Gunthorpe
2025-06-24 16:23 ` Alex Williamson
2025-06-24 18:12 ` Jason Gunthorpe
2025-06-24 16:35 ` Alex Mastro
2025-06-24 18:16 ` Jason Gunthorpe
2025-06-24 18:53 ` Alex Mastro
2025-06-24 18:58 ` Jason Gunthorpe
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=20250623231450.1326244-1-amastro@fb.com \
--to=amastro@fb.com \
--cc=alex.williamson@redhat.com \
--cc=jgg@ziepe.ca \
--cc=kbusch@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterx@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®