>Hello,
>
>On 5/19/25 02:01, edmund.raile wrote:
>>>> Restore SR-IOV Intel iGPU VF passthrough capability:
>>>> Check x-igd-opregion=off parameter in vfio_pci_igd_config_quirk and
>>>> vfio_pci_kvmgt_config_quirk to ensure x-igd-opregion=off is
>>>> respected despite subsequent attempt of automatic
>>>> IGD opregion detection.
>>>>
>>>> Fixes: 7be29f2f1a3f ("Merge tag 'pull-vfio-20250509' of
>>>> https://github.com/legoater/qemu into staging")
>>>
>>> Can you bisect to a specific commit from the merge? The merge may be
>>> where the issue was introduced to mainline, but the merge commit itself
>>> is more than likely not the source of the issue. Thanks,
>>>
>>> Alex
>>
>> I have to admit, I have no idea how to pluck apart
>> that merge pull using git.
>
>Please use git-bisect. The manual contains enough information to get
>you on the right track.
I'm quite impressed that git bisect in main repo has the power
to bisect into commits on a branch of a fork repo despite
being summarized into one commit on the main repo.
I did not think this was possible which is why I said I don't know
how to do this.
c0273e77f2d7aab3312eb557b49332da528ff66b is the first bad commit
So merging it into the main qemu repo changed the commit number
but it's the very commit I found; it adds the automatic IGD
opregion detection.
Should I send in a patch v2 and correct the Fixes tag or can you do
this while committing?
This would then be the correct tag:
Fixes: c0273e77f2d7 ("vfio/igd: Detect IGD device by OpRegion")
>
>
>Thanks,
>
>C.
