From: Alex Williamson <alex.williamson@redhat.com>
To: liulongfang <liulongfang@huawei.com>
Cc: <jgg@nvidia.com>, <shameerali.kolothum.thodi@huawei.com>,
<jonathan.cameron@huawei.com>, <cohuck@redhat.com>,
<linux-kernel@vger.kernel.org>, <linuxarm@openeuler.org>
Subject: Re: [PATCH v8 3/5] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver
Date: Sat, 18 Mar 2023 08:38:06 -0600 [thread overview]
Message-ID: <20230318083806.41a121f9.alex.williamson@redhat.com> (raw)
In-Reply-To: <ed124c05-9ebe-57e7-51bb-52edf6061646@huawei.com>
On Sat, 18 Mar 2023 17:07:38 +0800
liulongfang <liulongfang@huawei.com> wrote:
> On 2023/3/14 23:17, Alex Williamson wrote:
> > I was thinking:
> >
> > vfio
> > ├── <name1>
> > │ └── migration
> > │ ├── hisi_acc
> > │ │ ├── attr
> > │ │ ├── data
> > │ │ └── debug
> > │ └── state
> > └── <name2>
> > └── migration
> > ├── hisi_acc
> > │ ├── attr
> > │ ├── data
> > │ └── debug
> > └── state
> >
> > My concern is that if {attr,data,debug} have driver specific
> > definitions, they should have their own driver specific namespace.
> > Thanks,
> >
>
> Do <name1> and <name1> refer to dev_name()?
Yes
> Is the file name "hisi_acc" defined by the driver?
Yes, this is the drive defined namespace. Thanks,
Alex
next prev parent reply other threads:[~2023-03-18 14:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 8:48 [PATCH v8 0/5] add debugfs to " Longfang Liu
2023-02-17 8:48 ` [PATCH v8 1/5] vfio/migration: Add debugfs to live " Longfang Liu
2023-03-10 17:12 ` Jason Gunthorpe
2023-03-14 9:32 ` liulongfang
2023-03-14 11:31 ` liulongfang
2023-03-10 23:40 ` Alex Williamson
2023-03-14 9:42 ` liulongfang
2023-02-17 8:48 ` [PATCH v8 2/5] hisi_acc_vfio_pci: extract public functions for container_of Longfang Liu
2023-03-10 17:18 ` Jason Gunthorpe
2023-03-10 23:40 ` Alex Williamson
2023-03-14 10:34 ` liulongfang
2023-02-17 8:48 ` [PATCH v8 3/5] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver Longfang Liu
2023-03-10 17:22 ` Jason Gunthorpe
2023-03-14 10:35 ` liulongfang
2023-03-10 23:40 ` Alex Williamson
2023-03-14 11:04 ` liulongfang
2023-03-14 11:21 ` liulongfang
2023-03-14 15:17 ` Alex Williamson
2023-03-18 9:07 ` liulongfang
2023-03-18 14:38 ` Alex Williamson [this message]
2023-02-17 8:48 ` [PATCH v8 4/5] Documentation: add debugfs description for vfio Longfang Liu
2023-03-10 23:39 ` Alex Williamson
2023-03-14 10:56 ` liulongfang
2023-02-17 8:48 ` [PATCH v8 5/5] vfio: update live migration device status Longfang Liu
2023-03-10 8:27 ` [PATCH v8 0/5] add debugfs to migration driver liulongfang
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=20230318083806.41a121f9.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=jgg@nvidia.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=liulongfang@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.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®