Re: [PATCH v3 03/11] vpci/header: Emulate legacy capability list for dom0

2025-05-07 Thread Roger Pau Monné
On Wed, May 07, 2025 at 02:46:52AM +, Chen, Jiqian wrote: > On 2025/5/6 21:50, Roger Pau Monné wrote: > > On Mon, Apr 21, 2025 at 02:18:55PM +0800, Jiqian Chen wrote: > >> Current logic of emulating legacy capability list is only for domU. > >> So, expand it to emulate for dom0 too. Then it wil

Re: [PATCH v3 03/11] vpci/header: Emulate legacy capability list for dom0

2025-05-07 Thread Chen, Jiqian
On 2025/5/7 15:49, Roger Pau Monné wrote: > On Wed, May 07, 2025 at 02:46:52AM +, Chen, Jiqian wrote: >> On 2025/5/6 21:50, Roger Pau Monné wrote: >>> On Mon, Apr 21, 2025 at 02:18:55PM +0800, Jiqian Chen wrote: Current logic of emulating legacy capability list is only for domU. So, e

Re: [PATCH v3 03/11] vpci/header: Emulate legacy capability list for dom0

2025-05-06 Thread Chen, Jiqian
On 2025/5/7 10:46, Chen, Jiqian wrote: > On 2025/5/6 21:50, Roger Pau Monné wrote: >> On Mon, Apr 21, 2025 at 02:18:55PM +0800, Jiqian Chen wrote: >>> Current logic of emulating legacy capability list is only for domU. >>> So, expand it to emulate for dom0 too. Then it will be easy to hide >>> a ca

Re: [PATCH v3 03/11] vpci/header: Emulate legacy capability list for dom0

2025-05-06 Thread Chen, Jiqian
On 2025/5/6 21:50, Roger Pau Monné wrote: > On Mon, Apr 21, 2025 at 02:18:55PM +0800, Jiqian Chen wrote: >> Current logic of emulating legacy capability list is only for domU. >> So, expand it to emulate for dom0 too. Then it will be easy to hide >> a capability whose initialization fails in a func

Re: [PATCH v3 03/11] vpci/header: Emulate legacy capability list for dom0

2025-05-06 Thread Roger Pau Monné
On Mon, Apr 21, 2025 at 02:18:55PM +0800, Jiqian Chen wrote: > Current logic of emulating legacy capability list is only for domU. > So, expand it to emulate for dom0 too. Then it will be easy to hide > a capability whose initialization fails in a function. > > Signed-off-by: Jiqian Chen Sorry,

Re: [PATCH v3 03/11] vpci/header: Emulate legacy capability list for dom0

2025-05-06 Thread Roger Pau Monné
On Mon, Apr 21, 2025 at 02:18:55PM +0800, Jiqian Chen wrote: > Current logic of emulating legacy capability list is only for domU. > So, expand it to emulate for dom0 too. Then it will be easy to hide > a capability whose initialization fails in a function. > > Signed-off-by: Jiqian Chen With th

Re: [PATCH v3 03/11] vpci/header: Emulate legacy capability list for dom0

2025-04-23 Thread Jan Beulich
On 23.04.2025 05:31, Chen, Jiqian wrote: > On 2025/4/23 00:01, Jan Beulich wrote: >> On 21.04.2025 08:18, Jiqian Chen wrote: >>> @@ -759,10 +759,11 @@ static int vpci_init_capability_list(struct pci_dev >>> *pdev) >>> PCI_CAP_ID_MSI, >>> PCI_CAP_ID_MSIX, >>> }; >

Re: [PATCH v3 03/11] vpci/header: Emulate legacy capability list for dom0

2025-04-22 Thread Chen, Jiqian
On 2025/4/23 00:01, Jan Beulich wrote: > On 21.04.2025 08:18, Jiqian Chen wrote: >> @@ -759,10 +759,11 @@ static int vpci_init_capability_list(struct pci_dev >> *pdev) >> PCI_CAP_ID_MSI, >> PCI_CAP_ID_MSIX, >> }; >> +const unsigned int *caps = is_hwdom ?

Re: [PATCH v3 03/11] vpci/header: Emulate legacy capability list for dom0

2025-04-22 Thread Jan Beulich
On 21.04.2025 08:18, Jiqian Chen wrote: > @@ -759,10 +759,11 @@ static int vpci_init_capability_list(struct pci_dev > *pdev) > PCI_CAP_ID_MSI, > PCI_CAP_ID_MSIX, > }; > +const unsigned int *caps = is_hwdom ? NULL : supported_caps; > +const unsigne