[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v6 2/8] vpci: Refactor REGISTER_VPCI_INIT


  • To: Jan Beulich <jbeulich@xxxxxxxx>
  • From: "Chen, Jiqian" <Jiqian.Chen@xxxxxxx>
  • Date: Tue, 24 Jun 2025 08:32:40 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass header.d=amd.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=riykvut66DTxk6YJ7YMoyfqs5HLJBG2e0oJy/dPBol8=; b=tKoyQGhy1JH8L1juuFwoAoWedcBMBG2MVQ5Yl8H7KJNBRpvaXFQxn54rUruotAuqnZQc2Q4meWOYX+YlxjKCLWuc93JY/6R5A5elEqNKB4TfSY2YhUxkV9d7toOngIibp6IoTZ0FIHAPcmwjVYRDQLgiKUCkntXbJ1LoxEMKE+pDq2rhkbfryj6GWTAGzPz8QNk8kUwigip5IBz0iubw4LuiLVAkkjc/v/U7+GAICd/n8p3W0017YfKlNaZtdaEeht28viAI9A9oNUjkdt1ISg8CLLAECdnL5rcv0BGhtOv/2o834Q97XpTyCCJIu2V8fAyoSE7LZ+efZ3LQe5c6mw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=Q0TfRwBadpRQ0VsfioR97EMC/EEP/I5cueS5zLo5UXWNO0dTsdOQXgjlu3oT5y+0WX2K7Clg1spZuUCV5tZ5IQHaVHQIzfG1W4buTrZHRnAT4M/9Nd9me8w8nt+y+jWc8Q+K6YICQfTp/uWacTEvWTfW7l4GKJiO71//YA6kOzdFXG4qUnMgy8IrP2GyYox60JmIZigVPdXyQ4F1EeUK+fxEBe2CItnWWvPtdplEGshbDR2JzMLHRJPjUYiD30vsTE6cPx9NoniiPKpHAKHlCcPW1SrGXlzGvLFnPk8R8UsjS2FpZv0oHx4UVDyIAbc3lIByPL2YkliVLBtfbmSlMw==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=amd.com;
  • Cc: "Huang, Ray" <Ray.Huang@xxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, "Orzel, Michal" <Michal.Orzel@xxxxxxx>, Julien Grall <julien@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "Chen, Jiqian" <Jiqian.Chen@xxxxxxx>
  • Delivery-date: Tue, 24 Jun 2025 08:32:52 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHb23yakGdVC9XxvEWnYcnp8zrTt7QJBRKAgAGLVICAARN8gIAG6YaA//98XQCAAIcUAP//fCSAgACGWwA=
  • Thread-topic: [PATCH v6 2/8] vpci: Refactor REGISTER_VPCI_INIT

On 2025/6/24 16:28, Jan Beulich wrote:
> On 24.06.2025 10:26, Chen, Jiqian wrote:
>> On 2025/6/24 16:17, Jan Beulich wrote:
>>> On 24.06.2025 10:12, Chen, Jiqian wrote:
>>>> On 2025/6/20 14:34, Jan Beulich wrote:
>>>>> On 19.06.2025 08:14, Chen, Jiqian wrote:
>>>>>> On 2025/6/18 22:33, Jan Beulich wrote:
>>>>>>> On 12.06.2025 11:29, Jiqian Chen wrote:
>>>>>>>> +} vpci_capability_t;
>>>>>>>
>>>>>>> As you have it here, ...
>>>>>>>
>>>>>>>> @@ -29,9 +30,22 @@ typedef int vpci_register_init_t(struct pci_dev 
>>>>>>>> *dev);
>>>>>>>>   */
>>>>>>>>  #define VPCI_MAX_VIRT_DEV       (PCI_SLOT(~0) + 1)
>>>>>>>>  
>>>>>>>> -#define REGISTER_VPCI_INIT(x, p)                \
>>>>>>>> -  static vpci_register_init_t *const x##_entry  \
>>>>>>>> -               __used_section(".data.vpci." p) = (x)
>>>>>>>> +#define REGISTER_VPCI_CAPABILITY(cap, finit, fclean, ext) \
>>>>>>>> +    static const vpci_capability_t finit##_t = { \
>>>>>>>
>>>>>>> ... _t suffixes generally designate types. I don't think we should abuse
>>>>>>> that suffix for an identifier of a variable.
>>>>>> What do you think I should change to?
>>>>>
>>>>> Well, if you take my other advice, this question won't need answering, as
>>>>> then you only need the ..._entry one.
>>>>>
>>>>> Btw, noticing only now - why is it finit that's used to derive the 
>>>>> identifier?
>>>>> With that, it could as well be fclean (leaving aside the fact that that's
>>>>> optional). Imo the name would better be derived from cap, and it would 
>>>>> better
>>>>> also reflect the purpose of the variable.
>>>> I considered this.
>>>> I think it is easier to use finit, and finit contains the cap type, and 
>>>> the main purpose of this struct is to initialize the cap.
>>>
>>> Yet identifier names should make sense for the object they name.
>> OK. What's your suggestion about naming the entry?
> 
> cap##_init or _##cap##_init for example.
If so, I need to extend the parameter of REGISTER_VPCI_CAPABILITY since current 
cap is number, not string.
Maybe:
REGISTER_VPCI_CAPABILITY (cap, cap_id, finit, fclean, ext)

> 
> Jan

-- 
Best regards,
Jiqian Chen.

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.