The xHCI emulation greatly depends on the user space library libusb which is based on the usbfs module in Linux kernel. The libusb will bind usbfs to physical USB device which makes hardware control

Current design cannot get physical USB device information without the creation of pci_xhci_dev_emu. This brings some dificulties in certain situations, hence struct usb_native_devinfo is introduced to

Current DM design use two variables to do the indexing of xHCI Event Ring: er_enq_idx and er_events_cnt. They are members of the struct pci_xhci_rtsregs. In UOS, during the process of xHCI resuming,

PORTSC (Port Status and Control Register) register play a very important role in USB sub-system. This patch is used to refine related manipulation functions. Signed-off-by: Xiaoguang Wu

This patchset enable the USB xHCI S3 feature. Xiaoguang Wu (6): DM USB: xHCI: fix an xHCI issue to enable UOS s3 feature DM USB: xHCI: refine xHCI PORTSC Register related functions DM USB:

Hi Eddie/Anthony, Do you have any comments on this one?

HI Eddie, do you mean misra violation that mingqiang addressed? If so, please give me a ACK in my V2 patch. BR, Victor

Acked-by: Eddie Dong <eddie.dong@...>

Ok then. The sbuf has a hypercall, we need compile option to cover all sbuf code...

LGTM, with one issue to fix.

Under multiple VQ use case, it is possible to have concurrent requests. Added support to return multiple vq index from all vcpu. Signed-off-by: Ong Hock Yu <ong.hock.yu@...> ---

When running longevity test and capture acrntrace, generated acrntrace files sizes are too big. Sometimes we don't care very old trace. This patch adds ring buffer mode, fixes acrntrace file size and

- clear run context when reset vcpu; - destroy trusty without erase trusty memory when reset vm; changelog: v1 -> v2: fix misra violation on calling memset(); Signed-off-by: Sun Victor

shell command "vmexit" is the only one user of vmexit_time/cnt and we use the get_vmexit_profile, enclosed by HV_DEBUG, to access these variables. I can't follow here. Can you make it more

Thanks Mingqiang, I will update it soon. BR, Victor

If it is physical out of ranger, returning what hardware returns is better than fixed-zero. We want the code to be slim to save FuSa effort. Thx Eddie

The series are fine. Please go PR with my ACK.

This is part of SBUF component, what kind of compile option do we use? Let us use same one. BTW, hcall side also needs this kind of compile option.