[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230318083806.41a121f9.alex.williamson@redhat.com>
Date: Sat, 18 Mar 2023 08:38:06 -0600
From: Alex Williamson <alex.williamson@...hat.com>
To: liulongfang <liulongfang@...wei.com>
Cc: <jgg@...dia.com>, <shameerali.kolothum.thodi@...wei.com>,
<jonathan.cameron@...wei.com>, <cohuck@...hat.com>,
<linux-kernel@...r.kernel.org>, <linuxarm@...neuler.org>
Subject: Re: [PATCH v8 3/5] hisi_acc_vfio_pci: register debugfs for
hisilicon migration driver
On Sat, 18 Mar 2023 17:07:38 +0800
liulongfang <liulongfang@...wei.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
Powered by blists - more mailing lists