Chenli Wei <chenli.wei@...> writes: Drop imports you do not use. Drop this useless variable. Drop the two variables which are never used. I still think it is not right to do per-level CLOS

1. add virtio gpu logic in the upgrader.py script. 2. fix the upgraded virtio elements issue. 3. add the logic to remove the element with an empty value in xml file to use the default

Kunhui-Li <kunhuix.li@...> writes: Reviewed-by: Junjie Mao <junjie.mao@...> This config item alone does not require any change to the upgrader (as it only adds a new optional item).

Kunhui-Li <kunhuix.li@...> writes: The description here is vague. You need to set two hugepage parameters (for 1GB and 2MB, respectively), but only specifies one formula. The number of huge

The current RDT setting requires users to calculate the CLOS mask and the details, it is not a user-friendly setting. So we redesigned RDT, users can easily specify the cache of each vcpu for

OK, i will add it in v2. Most modification is used to transformation between rtc register and time_t. In v2 i will refine some detail to reduce codes.

ACRN Project TCM - 20th April 2022 Location Online by Zoom: https://zoom.com.cn/j/320664063 Attendees (Total 20, 20/04) Agenda ACRN project update: N/A ‘WW17’22 ACRN DX: Overview and new

This name is inherit from the origin file, i will rename it as our rule.

When removing Service VM from UI, the post-launched VMs should also be removed. Besides, add a warning window when removing Service VM. v1->v2: add a warining window Signed-off-by: Conghui

Virtio gpu device UI will be implemented after 3.0. As a workaround, this patch simply adds the virtio gpu entry in schema and launch script generation logic. To do will update the upgrader python

update the hugepage algorithm to meet the following conditions. 1. Service vm cmdline setting HugepageN=total memory-3G -1G(memory need by service vm supporting virtio gpu)-300M*num(number of virtio

When removing Service OS from UI, the post-launched OS should also be removed. Signed-off-by: Conghui <conghui.chen@...> --- .../ConfigureSettingsForScenario.jsx | 10

"Li, Ziheng" <ziheng.li@...> writes: We need to check if the console is capable of handling escaped color codes before using them. If this is a temporary file, create one use the `tempfile`

"Li, Ziheng" <ziheng.li@...> writes: Reviewed-by: Junjie Mao <junjie.mao@...> -- Best Regards Junjie Mao

Today ACRN works only on platforms with a single PCI domain (which is true for most client and IoT platforms). This limitation is also used to simplify the implementation of the board inspector. As a

This patch adds the import of the `sys` module in platformbase.py which uses `sys.exit` to terminate the board inspector upon fatal errors. Signed-off-by: Junjie Mao <junjie.mao@...> ---

The lookup extractor of the board inspector filters out non-PCI or non-present devices by checking the presence of vendor ID and class code. The same logic applies to PCI buses as well, but is

I suggest to check leaf 0x2 just after cheching leaf 0x1. Could we use the default case to handle those CPUIDs which could get the value from physical directly ?