On 6/27/25 02:26, Alex Williamson wrote:
> On Tue, 17 Jun 2025 08:56:41 +0800
> Tomita Moeko wrote:
>
>> On 2025/5/29 18:41, Tomita Moeko wrote:
>>> On 2025/5/29 2:30, Alex Williamson wrote:
On Wed, 28 May 2025 23:55:48 +0800
Tomita Moeko wrote:
> Introduce x-pci-class-cod
On Tue, 17 Jun 2025 08:56:41 +0800
Tomita Moeko wrote:
> On 2025/5/29 18:41, Tomita Moeko wrote:
> > On 2025/5/29 2:30, Alex Williamson wrote:
> >> On Wed, 28 May 2025 23:55:48 +0800
> >> Tomita Moeko wrote:
> >>
> >>> Introduce x-pci-class-code option to allow users to override PCI class
>
On 2025/5/29 18:41, Tomita Moeko wrote:
> On 2025/5/29 2:30, Alex Williamson wrote:
>> On Wed, 28 May 2025 23:55:48 +0800
>> Tomita Moeko wrote:
>>
>>> Introduce x-pci-class-code option to allow users to override PCI class
>>> code of a device, similar to the existing x-pci-vendor-id option. Only
On 2025/5/29 2:30, Alex Williamson wrote:
> On Wed, 28 May 2025 23:55:48 +0800
> Tomita Moeko wrote:
>
>> Introduce x-pci-class-code option to allow users to override PCI class
>> code of a device, similar to the existing x-pci-vendor-id option. Only
>> the lower 24 bits of this option are used,
On Wed, 28 May 2025 23:55:48 +0800
Tomita Moeko wrote:
> Introduce x-pci-class-code option to allow users to override PCI class
> code of a device, similar to the existing x-pci-vendor-id option. Only
> the lower 24 bits of this option are used, though a uint32 is used here
> for determining whet
Introduce x-pci-class-code option to allow users to override PCI class
code of a device, similar to the existing x-pci-vendor-id option. Only
the lower 24 bits of this option are used, though a uint32 is used here
for determining whether the value is valid and set by user.
Additionally, to prevent
