On 2023/10/27 02:06, Robin Murphy wrote:
...
>>>> return ret;
>>>>
>>> [...]
>>>>> +static int __init dwc_pcie_pmu_init(void)
>>>>> +{
>>>>> + int ret;
>>>>> +
>>>>> + ret = cpuhp_setup_state_multi(CPUHP_AP_ONLINE_DYN,
>>>>> + "perf/dwc_pcie_pmu:online",
>>>>> + dwc_pcie_pmu_online_cpu,
>>>>> + dwc_pcie_pmu_offline_cpu);
>>>>> + if (ret < 0)
>>>>> + return ret;
>>>>> +
>>>>> + dwc_pcie_pmu_hp_state = ret;
>>>>> +
>>>>> + ret = platform_driver_register(&dwc_pcie_pmu_driver);
>>>>> + if (ret)
>>>>> + goto platform_driver_register_err;
>>>>> +
>>>>> + dwc_pcie_pmu_dev = platform_device_register_simple(
>>>>> + "dwc_pcie_pmu", PLATFORM_DEVID_NONE, NULL, 0);
>>>>> + if (IS_ERR(dwc_pcie_pmu_dev)) {
>>>>> + ret = PTR_ERR(dwc_pcie_pmu_dev);
>>>>> + goto platform_device_register_error;
>>>>> + }
>>>>
>>>> I'm a bit confused as to why you're having to create a platform device
>>>> for a PCI device -- is this because the main designware driver has already
>>>> bound to it? A comment here explaining why you need to do this would be
>>>> very helpful. In particular, is there any dependency on another driver
>>>> to make sure that e.g. config space accesses work properly? If so, we
>>>> probably need to enforce module load ordering or something like that.
>>>
>>> AFAICS the platform device/driver serve no purpose other than being a hilariously roundabout way to run the for_each_pci_dev() loop in dwc_pcie_pmu_probe() upon module init, and to save explicitly freeing the PMU name/data. Furthermore the devres action for dwc_pcie_pmu_remove_cpuhp_instance() is apparently going for even more style points at module exit by not even relying on the corresponding .remove callback of the tenuous platform driver to undo what its .probe did, but (ab)using the device's devres list to avoid having to keep track of an explicit list of PMU instances at all.
>>
>> You are right.
>>
>>>
>>> Frankly I think it would be a lot more straightforward to just maintain that explicit list of PMU instances, do the PMU creation directly in dwc_pcie_pmu_init(), then unregister and free them in dwc_pcie_pmu_exit(). Not every driver has to contain a literal struct device_driver.
>>
>> Agreed, it might be more straightforward. But personally speaking, I prefer
>> current implementation.
>>
>> - standard driver creation / probe flow is more normal
>
> It's really not, though. We have a weird singleton platform device appearing out of nowhere which effectively represents the module being loaded, rather than anything about the actual underlying hardware. If you want this to look like "normal" driver model usage, then create a separate platform device for each physical PCI PMU instance you discover (potentially via both a one-time scan at module_init and an ADD_DEVICE hotplug notifier later), then have the platform driver just register the corresponding PMU device in .probe and unregister it in .remove, without confusing devres action tricks.
>
Got it. If IIUC, I should register a platform device for each matched pci
device in module_init() or when BUS_NOTIFY_ADD_DEVICE event triggered, and
unwind it in module exit() and when BUS_NOTIFY_DEL_DEVICE event triggered.
Thank you for valuable comments.
Best Regards,
Shuai
