On 07/16/18 11:45, Liu, Jing2 wrote:
> Hi Laszlo,
>
> On 7/12/2018 3:29 PM, Laszlo Ersek wrote:
>> On 07/12/18 07:43, Liu, Jing2 wrote:
>>> Yep, thanks for the advice.
>>> But hotplugging on pci-bridge is the actual use case
>>> request so we would better solve and fix this.
>>
>>
>> You can
Hi Laszlo,
On 7/12/2018 3:29 PM, Laszlo Ersek wrote:
On 07/12/18 07:43, Liu, Jing2 wrote:
Yep, thanks for the advice.
But hotplugging on pci-bridge is the actual use case
request so we would better solve and fix this.
You can cold-plug a PCI Express Root Port in the Q35 root complex
On 07/12/18 07:43, Liu, Jing2 wrote:
> Yep, thanks for the advice.
> But hotplugging on pci-bridge is the actual use case
> request so we would better solve and fix this.
It doesn't take a bugfix, but a feature. The firmware needs to be told
to reserve PCI resources in advance, in preparation for
Yep, thanks for the advice.
But hotplugging on pci-bridge is the actual use case
request so we would better solve and fix this.
On 7/11/2018 6:38 PM, Laszlo Ersek wrote:
On 07/11/18 05:12, Liu, Jing2 wrote:
Hi,
Recently, we tried some hotplug issues. The case is: when hotplug a
device (e.g.
On 07/11/18 05:12, Liu, Jing2 wrote:
> Hi,
>
> Recently, we tried some hotplug issues. The case is: when hotplug a
> device (e.g. iGPU) onto pci-bridge after guest booting up, guest reports
> "BAR 2: no space for [mem size 0x4000 64bit pref]" etc.
>
> Seabios checks all the devices under the
Hi,
Recently, we tried some hotplug issues. The case is: when hotplug a
device (e.g. iGPU) onto pci-bridge after guest booting up, guest reports
"BAR 2: no space for [mem size 0x4000 64bit pref]" etc.
Seabios checks all the devices under the pci-bridge when qemu launching
the guest, and
