public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: liulongfang <liulongfang@huawei.com>,
	John Garry <john.garry@huawei.com>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	"jgg@nvidia.com" <jgg@nvidia.com>
Cc: "cohuck@redhat.com" <cohuck@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxarm@openeuler.org" <linuxarm@openeuler.org>
Subject: RE: [Linuxarm] [PATCH 1/2] hisi_acc_vfio_pci: Add debugfs to migration driver
Date: Mon, 17 Oct 2022 13:57:30 +0000	[thread overview]
Message-ID: <b8bf06ebd8da46a5a72001bead4b4a09@huawei.com> (raw)
In-Reply-To: <7c041671-71bf-d558-d47a-70296fe5c30e@huawei.com>



> -----Original Message-----
> From: liulongfang
> Sent: 17 October 2022 10:21
> To: John Garry <john.garry@huawei.com>; alex.williamson@redhat.com;
> jgg@nvidia.com; Shameerali Kolothum Thodi
> <shameerali.kolothum.thodi@huawei.com>
> Cc: cohuck@redhat.com; linux-kernel@vger.kernel.org;
> linuxarm@openeuler.org
> Subject: Re: [Linuxarm] [PATCH 1/2] hisi_acc_vfio_pci: Add debugfs to
> migration driver
> 
> On 2022/10/14 17:20, John Garry wrote:
> > On 14/10/2022 03:57, Longfang Liu wrote:
> >> +static void hisi_acc_vf_debugfs_init(struct hisi_acc_vf_core_device
> *hisi_acc_vdev)
> >> +{
> >> +    struct pci_dev *vf_pdev = hisi_acc_vdev->vf_dev;
> >> +    struct device *dev = &vf_pdev->dev;
> >> +    int ret;
> >> +
> >> +    if (!atomic_read(&hisi_acc_root_ref))
> >> +        hisi_acc_debugfs_root = debugfs_create_dir("hisi_vfio_acc",
> NULL);
> >> +    atomic_inc(&hisi_acc_root_ref);
> >> +
> >
> > This looks totally racy, such that I wonder why even bother using an atomic
> for hisi_acc_root_ref.
> 
> 
> When enabling VF, it is possible for multiple VMs to enable VF at the same
> time. The atomic variable
> is used to ensure that only one "hisi_vfio_acc" is created. When other VFs
> are enabled,
> it will not be created again, but will be used directly.
> 
>  Indeed, why is hisi_acc_debugfs_root not created in the driver module init?
> >
> Because the normal function of VF is to perform encryption and decryption
> services, the live migration
> function is an auxiliary function, which no need to be used in scenarios
> where only encryption and
> decryption services are performed.
> 
> During module init, it can register ops(hisi_acc_vfio_pci_ops) that only
> perform encryption and
> decryption services, and can also register with live migration function
> ops(hisi_acc_vfio_pci_migrn_ops),
> and this debugfs only needs to register it when the the ops is
> hisi_acc_vfio_pci_migrn_ops.

Isn't the ops registration happens at probe()? In any case, I think you can move
the hisi_acc_debugfs_root creation to module_init() as suggested above
and avoid the race.

Thanks,
Shameer

  parent reply	other threads:[~2022-10-17 13:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  2:57 [PATCH 0/2] Add debugfs to hisilicon migration driver Longfang Liu
2022-10-14  2:57 ` [PATCH 1/2] hisi_acc_vfio_pci: Add debugfs to " Longfang Liu
2022-10-14  9:20   ` [Linuxarm] " John Garry
2022-10-17  9:20     ` liulongfang
2022-10-17 12:11       ` Jason Gunthorpe
2022-10-18  7:06         ` liulongfang
2022-10-18 12:01           ` Jason Gunthorpe
2022-10-19  7:17             ` liulongfang
2022-10-17 13:57       ` Shameerali Kolothum Thodi [this message]
2022-10-18  6:55         ` liulongfang
2022-10-18  7:05           ` liulongfang
2022-10-14  2:57 ` [PATCH 2/2] Documentation: Add debugfs for hisi_acc_vfio_pci Longfang Liu

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=b8bf06ebd8da46a5a72001bead4b4a09@huawei.com \
    --to=shameerali.kolothum.thodi@huawei.com \
    --cc=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=john.garry@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@openeuler.org \
    --cc=liulongfang@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