sbuf is now only used for debug purpose, but later, it will be used as a common interfaces. So, move the sbuf related code out of the debug directory. Signed-off-by: Conghui <conghui.chen@...> Acked-b

Fix the bug in iothread handler, the event should be read out so that the next epoll_wait not return directly as the fd can still readable. Signed-off-by: Conghui <conghui.chen@...> --- devicemodel/co

Special Notes: If you have Zoom connection issue by using web browser, please install & launch Zoom application, manually input the meeting ID (320664063) to join the Zoom meeting. Agenda & Archives:

Add dispatch func for asyncio request, if the I/O base is found in asyncio list, queue the fd to the asyncio buffer. 'avail_idx' is updated by hv to show the available index which has request need to

From 8a754bc0618e2c05d95805a8729ca872ffe6c902 Mon Sep 17 00:00:00 2001 From: zihengL1 <ziheng.li@...> Date: Fri, 16 Sep 2022 10:47:43 +0800 Subject: [PATCH] config-tools: Missing tqdm python package i

PCI ROM is the firmware specific to PCI device and it is provided by the device vendor. The PCI rom resides in 0x30 offset of PCI config space. This can be used to check whether the PCI rom exists. An

Now the device model only supports the 0..5 PCI bar for PCI/PCIE devices. This tries to allocate the PCI_MEM32 resource for PCI ROM bar. V1->V2: Use the PCI_ROMBAR as bar index and PCIBAR_ROM bar type

The access to PCI config_space is handled in HV for Passthrough pci devices. And it also provides one mechanism to forward cfg_access of some registers to DM. For example: the opregion reg for GPU dev

Add the option of "romfile=file_location" to specify the rom file for rombar Signed-off-by: Zhao Yakui <yakui.zhao@...> Acked-by: Wang Yu <yu1.wang@...> --- devicemodel/hw/pci/passthrough.c | 6 ++++++

The pci_reg 0x30 of PCI config_space is used to check whether the PCI rom bar is supported. When the PCI rom is supported for the device in guest vm, the 0x30 pci_reg is emulated and it can return the

PCI ROM is the firmware specific to PCI device and it is provided by the device vendor. The PCI rom resides in 0x30 offset of PCI config space. This can be used to check whether the PCI rom exists. An

Add hypercall to add/remove asyncio request info. Hv will record the info in a list, and when a new ioreq is come, hv will check if it is in the asyncio list, if yes, queue the fd to asyncio buffer. S

Fix the truncate issue for virtio block parameter. Signed-off-by: Conghui <conghui.chen@...> --- devicemodel/hw/pci/virtio/virtio_block.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --gi

PCI ROM is the firmware specific to PCI device and it is provided by the device vendor. The PCI rom resides in 0x30 offset of PCI config space. This can be used to check whether the PCI rom exists. An

The access to PCI config_space is handled in HV for Passthrough pci devices. And it also provides one mechanism to forward cfg_access of some registers to DM. For example: the opregion reg for GPU dev

Add the option of "romfile=file_location" to specify the rom file for rombar Signed-off-by: Zhao Yakui <yakui.zhao@...> --- devicemodel/hw/pci/passthrough.c | 6 ++++++ 1 file changed, 6 insertions(+)

The pci_reg 0x30 of PCI config_space is used to check whether the PCI rom bar is supported. When the PCI rom is supported for the device in guest vm, the 0x30 pci_reg is emulated and it can return the

Now the device model only supports the 0..5 PCI bar for PCI/PCIE devices. This tries to allocate the PCI_MEM32 resource for PCI ROM bar. V1->V2: Use the PCI_ROMBAR as bar index and PCIBAR_ROM bar type

PCI ROM is the firmware specific to PCI device and it is provided by the device vendor. The PCI rom resides in 0x30 offset of PCI config space. This can be used to check whether the PCI rom exists. An

From b81449255c387f6de37dd3c53c8552576ba5210e Mon Sep 17 00:00:00 2001 From: zihengL1 <ziheng.li@...> Date: Fri, 16 Sep 2022 10:58:04 +0800 Subject: [PATCH] config-tools:config_summary.rst can't displ