Then please remove these useless varaibles. Please submit another patch for this logic.

"chenli.wei" <chenli.wei@...> writes: Reviewed-by: Junjie Mao <junjie.mao@...> -- Best Regards Junjie Mao

Kunhui-Li <kunhuix.li@...> writes: Reviewed-by: Junjie Mao <junjie.mao@...> -- Best Regards Junjie Mao

Kunhui-Li <kunhuix.li@...> writes: The slicing algorithm is designed not to touch sequences because they are ordered lists of nodes and the removal of some in the middle creates a different

Current physical memory segmentation UI have an redundant title when user select the advance mode, so we set the MemoryInfo element title to NULL to fix this issue. Signed-off-by: Chenli Wei

Add restriction for Maximum Virtual CLOS configuration that don't allow negative numbers. Tracked-On: #7530 Signed-off-by: Kunhui-Li <kunhuix.li@...> --- misc/config_tools/schema/config.xsd |

1. update schema_slicer.py to slice xs:sequence elements. 2. update backend type to "BasicVirtioConsoleBackendType" to call the sliced value. Tracked-On: #6691 Signed-off-by: Kunhui-Li

[Sun, Peng] Correct, I remove it. I will update the commit message in next version. [Sun, Peng] Yes. [Sun, Peng] We don't want user use the resolutions which bigger than window size for simple. But

Also you have removed 720p and changed the default one, right? Please update the commit message. After remove these 3 lines, the h_pixelmax, v_pixelmax and b_param are meaningless, right? BTW, what

Generated launch scripts tracks the options to ACRN device model in an array `dm_params`. Those scripts use `${dm_params[*]}` to join all elements in the array and pass the joined string to

Hi Yonghua IMHO, you could only unmap the ACRN_MEMMAP_RAM memory region which Page-ranges managed without "struct page", just pure PFN (VM_PFNMAP set in vm_flags). Thanks.

acrn_vm_memseg_unmap can't do EPT unmapping for memory type of ACRN_MEMMAP_RAM, while such kind of unmapping is required for case that user memory pages are taggeg with VM_PFNMAP flag. This

From: Sun Peng <peng.p.sun@...> Add 1280x1024@75, 1024x768@75, 1600x1200@60, 1600x900@60 modes. Tracked-On: #7507 Signed-off-by: Sun Peng <peng.p.sun@...> ---

OK We also check the CONFIG_MAX_PT_IRQ_ENTRIES by config tool before we align it.

Now we did this check #if ((MAX_IR_ENTRIES < 256U) || (MAX_IR_ENTRIES > 0x10000U) || (MAX_IR_ENTRIES & (MAX_IR_ENTRIES -1)) != 0U) #error "MAX_IR_ENTRIES must in the region of [256,0x10000] and be

Done >

"chenli.wei" <chenli.wei@...> writes: Reviewed-by: Junjie Mao <junjie.mao@...> One minor comment below. Add "VM" before "{$vm_name}" to say explicitly that it is a VM. -- Best

The current UI have no live-check to check whether a VM connect to itself. So we add an assert to the schema and return error when user connect a VM to itself. v1-->v2: 1. change the remind msg