August 2020 - Virt - mailweb.openeuler.org

Re: Kunpeng920 virtualization performance
by Ying Fang 17 Sep '20

17 Sep '20

On 7/2/2020 3:18 PM, Haibin Zhang wrote: > Hi, Ying Fang. > Hi Haibin, Thanks for report this issue for us. We will verify and response to you later. > I use qemu create a VM (96 cores and 360g ram) on my kunpeng 920-4826 server, then do unixbench tests. > The performance of pipe-based context switching decreases severely, which shows below: > > Guest# ./context1 60 > COUNT|4779535|1|lps > COUNT|4779536|1|lps > > Host# ./context1 60 > COUNT|13990745|1|lps > COUNT|13990746|1|lps > Could you provide more details about your OS and virtualization software version information for us? > As you know, pipe-based context switching measures the number of times two processes can exchange an > increasing integer through a pipe in a duration (like 60 seconds). Times of guest is only 34% as that > of host. Attachment is the context1.c from unixbench. It looks simple, just spawn a child process with > which it carries on a bi-directional pipe conversation. Yes, we had knowledge about this context test now. Thanks. > > Guest# taskset -c 20 ./context1 60 > COUNT|18059443|1|lps > COUNT|18059443|1|lps > > Host# taskset -c 20 ./context1 60 > COUNT|17881974|1|lps > COUNT|17881975|1|lps > > Use taskset to set cpu affinity, which makes results better. > > Can you help me fix this issue? Maybe WFE/WFI traps lead the performance cost? Is there PLE(Pause Loop Exit) feature on Kunpeng? > We had some performance tuning techniques in the openEuler OS. And Xie XiangYou is the expert on this area, maybe he could help you with it. Moreover, you can drop us an issue on gitee via: https://gitee.com/src-openeuler/qemu >

2 20

add document about custom CPU mode
by Peng Liang 29 Aug '20

29 Aug '20

1 0

[PATCH 0/6] Add RISC-V vm migration support
by Yifei Jiang 26 Aug '20

26 Aug '20

This series adds RISC-V vm migration support. Yifei Jiang (6): target/riscv: raise exception to HS mode at get_physical_address target/riscv: Add sifive_plic vmstate target/riscv: Support riscv cpu vmstate target/riscv: Add kvm_riscv_get/put_regs_timer target/riscv: Implement virtual time adjusting with vm state changing target/riscv: Support virtual time context synchronization hw/riscv/sifive_plic.c | 24 +++++++++- include/hw/riscv/sifive_plic.h | 1 + target/riscv/cpu.c | 31 +++++++++++- target/riscv/cpu.h | 7 +++ target/riscv/cpu_helper.c | 12 ++++- target/riscv/kvm.c | 86 ++++++++++++++++++++++++++++++++++ 6 files changed, 156 insertions(+), 5 deletions(-) -- 2.19.1

1 6

[PATCH 0/9] Add riscv kvm accel support
by Yifei Jiang 24 Aug '20

24 Aug '20

This series adds both riscv32 and riscv64 kvm support, It is based on https://gitee.com/openeuler/kernel/tree/kernel-5.5/. Several steps to use this: 1. Build emulation $ ./configure --target-list=riscv64-softmmu $ make -j$(nproc) 2. Build kernel https://gitee.com/openeuler/kernel/tree/kernel-5.5/ 3. Build QEMU VM cross built in riscv toolchain. $ PKG_CONFIG_LIBDIR=<toolchain pkgconfig path> $ export PKG_CONFIG_SYSROOT_DIR=<toolchain sysroot path> $ ./configure --target-list=riscv64-softmmu --enable-kvm \ --cross-prefix=riscv64-linux-gnu- --disable-libiscsi --disable-glusterfs \ --disable-libusb --disable-usb-redir --audio-drv-list= --disable-opengl \ --disable-libxml2 $ make -j$(nproc) 4. Start emulation $ ./qemu-system-riscv64 -M virt -m 4096M -cpu rv64,x-h=true -nographic \ -name guest=riscv-hyp,debug-threads=on \ -smp 4 \ -bios ./fw_jump.bin \ -kernel ./Image \ -drive file=./hyp.img,format=raw,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -append "root=/dev/vda rw console=ttyS0 earlycon=sbi" 5. Start kvm-acceled QEMU VM in emulation $ ./qemu-system-riscv64 -M virt,accel=kvm -m 1024M -cpu host -nographic \ -name guest=riscv-guset \ -smp 2 \ -bios none \ -kernel ./Image \ -drive file=./guest.img,format=raw,id=hd0 \ -device virtio-blk-device,drive=hd0 \ -append "root=/dev/vda rw console=ttyS0 earlycon=sbi" Yifei Jiang (9): linux-header: Update linux/kvm.h target/riscv: Add target/riscv/kvm.c to place the public kvm interface target/riscv: Implement function kvm_arch_init_vcpu target/riscv: Implement kvm_arch_get_registers target/riscv: Implement kvm_arch_put_registers target/riscv: Support start kernel directly by KVM hw/riscv: PLIC update external interrupt by KVM when kvm enabled target/riscv: Handler KVM_EXIT_RISCV_SBI exit target/riscv: add host cpu type configure | 1 + hw/riscv/sifive_plic.c | 31 +- hw/riscv/virt.c | 15 +- linux-headers/linux/kvm.h | 8 + target/riscv/Makefile.objs | 1 + target/riscv/cpu.c | 10 + target/riscv/cpu.h | 4 + target/riscv/kvm.c | 501 +++++++++++++++++++++++++++++ target/riscv/kvm_riscv.h | 25 ++ target/riscv/sbi_ecall_interface.h | 72 +++++ 10 files changed, 657 insertions(+), 11 deletions(-) create mode 100644 target/riscv/kvm.c create mode 100644 target/riscv/kvm_riscv.h create mode 100644 target/riscv/sbi_ecall_interface.h -- 2.19.1

1 9

CPU feature及依赖补丁
by Peng Liang 19 Aug '20

19 Aug '20

1 0

reschedule the Virt sig meeting//FW: 转发：【Meeting Notice】Virt sig meeting Time: 2020-08-17 14:30-16:30
by Chenzhendong (alex) 14 Aug '20

14 Aug '20

Hi all, Due to the meeting time conflict, the Virt sig meeting time is changed to 14:30 p.m. on August 17. Sorry for any inconvenience. If you have any questions, please feel free to contact me. -------- 原始邮件 -------- 发件人： Meeting Book <uMeeting(a)huawei.com<mailto:uMeeting@huawei.com>> 日期： 2020年8月14日周五 10:39 收件人： zdchenhn(a)163.com<mailto:zdchenhn@163.com> 主题：【Meeting Notice】Virt sig meeting Time: 2020-08-17 14:30-16:30 Topic Virt sig meeting Time 2020-08-17 14:30-16:30((UTC+08:00)Beijing) Join Conference Join (External) >><https://welink-meeting.zoom.us/j/360440806> Meeting ID 360 440 806 Convener 陈振东 Tips: Dial the access number to join conference<http://app.huawei.com/eshare/voiceMeetings> 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 如果加入会议提示“会议已结束或会议号不存在”，请在官网下载最新版本入会。立即下载<https://zoom.us/download> If a message is displayed, indicating that the meeting has ended or the meeting ID does not exist, download the latest meeting client and try again.Download<https://zoom.us/download>

1 0

[PATCH hulk-4.19-next v3 00/17] KVM: arm64 support vCPU preempted check and PV qspinlock
by Zengruan Ye 13 Aug '20

13 Aug '20

From: y00379943 <yezengruan(a)huawei.com> This patch set aims to support the vCPU preempted check and PV qspinlock under KVM/arm64. Changes from v2: * Remove Wanpeng Li's patches from this patch set * Bunch of typo fixes. Changes from v1: * Fix pv_time_ops undeclared in drivers/xen/time.c * Fix native_queued_spin_lock_slowpath undeclared in arch/arm64/kernel/alternative.c Christoffer Dall (1): KVM: arm/arm64: Factor out hypercall handling from PSCI code Qian Cai (1): arm64/spinlock: fix a -Wunused-function warning Steven Price (3): KVM: Implement kvm_put_guest() arm/arm64: Provide a wrapper for SMCCC 1.1 calls arm/arm64: Make use of the SMCCC 1.1 wrapper Waiman Long (1): locking/osq: Use optimized spinning loop for arm64 Zengruan Ye (11): arm/paravirt: Use a single ops structure KVM: arm64: Document PV-sched interface KVM: arm64: Implement PV_SCHED_FEATURES call KVM: arm64: Support pvsched preempted via shared structure KVM: arm64: Add interface to support vCPU preempted check KVM: arm64: Support the vCPU preemption check KVM: arm64: Add SMCCC PV-sched to kick cpu KVM: arm64: Implement PV_SCHED_KICK_CPU call KVM: arm64: Add interface to support PV qspinlock KVM: arm64: Enable PV qspinlock KVM: arm64: Add tracepoints for PV qspinlock Documentation/virtual/kvm/arm/pvsched.txt | 64 +++++++ arch/arm/include/asm/kvm_host.h | 25 +++ arch/arm/include/asm/paravirt.h | 9 +- arch/arm/kernel/paravirt.c | 4 +- arch/arm/kvm/Makefile | 2 +- arch/arm/kvm/handle_exit.c | 2 +- arch/arm/mm/proc-v7-bugs.c | 13 +- arch/arm64/Kconfig | 14 ++ arch/arm64/include/asm/kvm_host.h | 20 ++ arch/arm64/include/asm/paravirt.h | 63 ++++++- arch/arm64/include/asm/pvsched-abi.h | 16 ++ arch/arm64/include/asm/qspinlock.h | 15 +- arch/arm64/include/asm/qspinlock_paravirt.h | 12 ++ arch/arm64/include/asm/spinlock.h | 26 +++ arch/arm64/kernel/Makefile | 3 +- arch/arm64/kernel/alternative.c | 5 +- arch/arm64/kernel/cpu_errata.c | 82 +++------ arch/arm64/kernel/paravirt-spinlocks.c | 18 ++ arch/arm64/kernel/paravirt.c | 192 +++++++++++++++++++- arch/arm64/kernel/setup.c | 2 + arch/arm64/kernel/trace-paravirt.h | 66 +++++++ arch/arm64/kvm/Makefile | 2 + arch/arm64/kvm/handle_exit.c | 5 +- drivers/xen/time.c | 4 + include/kvm/arm_hypercalls.h | 43 +++++ include/kvm/arm_psci.h | 2 +- include/linux/arm-smccc.h | 65 +++++++ include/linux/cpuhotplug.h | 1 + include/linux/kvm_host.h | 22 +++ include/linux/kvm_types.h | 2 + kernel/locking/osq_lock.c | 23 +-- virt/kvm/arm/arm.c | 12 +- virt/kvm/arm/hypercalls.c | 68 +++++++ virt/kvm/arm/psci.c | 76 +------- virt/kvm/arm/pvsched.c | 73 ++++++++ virt/kvm/arm/trace.h | 18 ++ 36 files changed, 899 insertions(+), 170 deletions(-) create mode 100644 Documentation/virtual/kvm/arm/pvsched.txt create mode 100644 arch/arm64/include/asm/pvsched-abi.h create mode 100644 arch/arm64/include/asm/qspinlock_paravirt.h create mode 100644 arch/arm64/kernel/paravirt-spinlocks.c create mode 100644 arch/arm64/kernel/trace-paravirt.h create mode 100644 include/kvm/arm_hypercalls.h create mode 100644 virt/kvm/arm/hypercalls.c create mode 100644 virt/kvm/arm/pvsched.c -- 2.19.1

2 19

Virt sig会议议程纪要0731//RE: 【Meeting Notice】Virt sig meeting Time: 2020-07-31 14:30-16:30
by Chenzhendong (alex) 06 Aug '20

06 Aug '20

Virt sig会议议程纪要： 1、openEuler 20.09 虚拟化特性进展： a) KVM支持custom模式：整体进展80%，涉及两个组件：libvirt开发50%，qemu部分90%。 b) Vmtop：整体进展80%，用户态：将源码文件拆分，目录进行规范化，完成README以及相关文档；内核：检视后等待合入。 c) SmartPolling：整体进展80%，smartpoll的x86，已经检视通过，等待合入，arm的支持还在开发中。 d) PMU nmi watchdog：整体进展90%，开源方案分析完成，本地预验证通过，待版本验证。 e) 双层调度：整体进展80%，代码正在检视。 f) 安全启动：整体进展90%，edk2代码已经合入，待版本验证。 g) 可信启动：整体进展80%，qemu开源patch已经根据openEuler完成适配，验证功能中。 h) 轻量虚拟化：整体进展80%，基本功能开发完成，目前在进行可靠性、安全等增强。 2、EulerRobot质量体系构建进展： a) 当前Avocado-vt/tp-libvirt/tp-qemu等集成测试框架及用例，已经开源（见openEuler社区中相关仓库的openEuler-20.03分支）； b) crystal-ci平台在开发过程中，本地已经基于LKP调试对接了VT用例基本流程，待crystal-ci平台环境ready后即可与其快速对接。 3、virt 技术路标讨论： a) openEuler 20.09以后的特性待后续讨论。 From: Chenzhendong (alex) Sent: Thursday, July 30, 2020 3:10 PM To: 'dev(a)openeuler.org' <dev(a)openeuler.org>; 'tc(a)openeuler.org' <tc(a)openeuler.org>; 'virt(a)openeuler.org' <virt(a)openeuler.org> Cc: Zhangxiaofeng (F) <victor.zhangxiaofeng(a)huawei.com> Subject: 【Meeting Notice】Virt sig meeting Time: 2020-07-31 14:30-16:30 Virt sig会议议程： 1、openEuler 20.09 虚拟化特性进展 alexchen 2、EulerRobot质量体系构建进展 kuhnchen 3、virt 技术路标讨论 all -------- 原始邮件 -------- 发件人： Meeting Book <uMeeting(a)huawei.com<mailto:uMeeting@huawei.com>> 日期： 2020年7月30日周四 10:12 收件人： zdchenhn(a)163.com<mailto:zdchenhn@163.com> 主题：【Meeting Notice】Virt sig meeting Time: 2020-07-31 14:30-16:30 Topic Virt sig meeting Time 2020-07-31 14:30-16:30((UTC+08:00)Beijing) Join Conference Join (External) >><https://welink-meeting.zoom.us/j/623832541> Meeting ID 623 832 541 Convener 陈振东 Tips: Dial the access number to join conference<http://app.huawei.com/eshare/voiceMeetings> 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 如果加入会议提示“会议已结束或会议号不存在”，请在官网下载最新版本入会。立即下载<https://zoom.us/download> If a message is displayed, indicating that the meeting has ended or the meeting ID does not exist, download the latest meeting client and try again.Download<https://zoom.us/download>

1 0

[PATCH v5 1/2] hw/smbios: add options for type 4 max-speed and current-speed
by Ying Fang 05 Aug '20

05 Aug '20

Common VM users sometimes care about CPU speed, so we add two new options to allow VM vendors to present CPU speed to their users. Normally these information can be fetched from host smbios. Strictly speaking, the "max speed" and "current speed" in type 4 are not really for the max speed and current speed of processor, for "max speed" identifies a capability of the system, and "current speed" identifies the processor's speed at boot (see smbios spec), but some applications do not tell the differences. Signed-off-by: Ying Fang <fangying1(a)huawei.com> Signed-off-by: Heyi Guo <guoheyi(a)huawei.com> --- hw/smbios/smbios.c | 36 ++++++++++++++++++++++++++++++++---- qemu-options.hx | 2 +- 2 files changed, 33 insertions(+), 5 deletions(-) diff --git a/hw/smbios/smbios.c b/hw/smbios/smbios.c index 11d476c4a2..53181a58eb 100644 --- a/hw/smbios/smbios.c +++ b/hw/smbios/smbios.c @@ -93,9 +93,21 @@ static struct { const char *manufacturer, *version, *serial, *asset, *sku; } type3; +/* + * SVVP requires max_speed and current_speed to be set and not being + * 0 which counts as unknown (SMBIOS 3.1.0/Table 21). Set the + * default value to 2000MHz as we did before. + */ +#define DEFAULT_CPU_SPEED 2000 + static struct { const char *sock_pfx, *manufacturer, *version, *serial, *asset, *part; -} type4; + uint64_t max_speed; + uint64_t current_speed; +} type4 = { + .max_speed = DEFAULT_CPU_SPEED, + .current_speed = DEFAULT_CPU_SPEED +}; static struct { size_t nvalues; @@ -273,6 +285,14 @@ static const QemuOptDesc qemu_smbios_type4_opts[] = { .name = "version", .type = QEMU_OPT_STRING, .help = "version number", + },{ + .name = "max-speed", + .type = QEMU_OPT_NUMBER, + .help = "max speed in MHz", + },{ + .name = "current-speed", + .type = QEMU_OPT_NUMBER, + .help = "speed at system boot in MHz", },{ .name = "serial", .type = QEMU_OPT_STRING, @@ -587,9 +607,8 @@ static void smbios_build_type_4_table(MachineState *ms, unsigned instance) SMBIOS_TABLE_SET_STR(4, processor_version_str, type4.version); t->voltage = 0; t->external_clock = cpu_to_le16(0); /* Unknown */ - /* SVVP requires max_speed and current_speed to not be unknown. */ - t->max_speed = cpu_to_le16(2000); /* 2000 MHz */ - t->current_speed = cpu_to_le16(2000); /* 2000 MHz */ + t->max_speed = cpu_to_le16(type4.max_speed); + t->current_speed = cpu_to_le16(type4.current_speed); t->status = 0x41; /* Socket populated, CPU enabled */ t->processor_upgrade = 0x01; /* Other */ t->l1_cache_handle = cpu_to_le16(0xFFFF); /* N/A */ @@ -1130,6 +1149,15 @@ void smbios_entry_add(QemuOpts *opts, Error **errp) save_opt(&type4.serial, opts, "serial"); save_opt(&type4.asset, opts, "asset"); save_opt(&type4.part, opts, "part"); + type4.max_speed = qemu_opt_get_number(opts, "max-speed", + DEFAULT_CPU_SPEED); + type4.current_speed = qemu_opt_get_number(opts, "current-speed", + DEFAULT_CPU_SPEED); + if (type4.max_speed > UINT16_MAX || + type4.current_speed > UINT16_MAX) { + error_setg(errp, "SMBIOS CPU speed is too large (> %d)", + UINT16_MAX); + } return; case 11: qemu_opts_validate(opts, qemu_smbios_type11_opts, &err); diff --git a/qemu-options.hx b/qemu-options.hx index ea0638e92d..50b068423c 100644 --- a/qemu-options.hx +++ b/qemu-options.hx @@ -2073,7 +2073,7 @@ DEF("smbios", HAS_ARG, QEMU_OPTION_smbios, " [,sku=str]\n" " specify SMBIOS type 3 fields\n" "-smbios type=4[,sock_pfx=str][,manufacturer=str][,version=str][,serial=str]\n" - " [,asset=str][,part=str]\n" + " [,asset=str][,part=str][,max-speed=%d][,current-speed=%d]\n" " specify SMBIOS type 4 fields\n" "-smbios type=17[,loc_pfx=str][,bank=str][,manufacturer=str][,serial=str]\n" " [,asset=str][,part=str][,speed=%d]\n" -- 2.23.0

1 1

[PATCH v5 0/2] add new options to set smbios type 4 fields
by Ying Fang 05 Aug '20

05 Aug '20

From: fangying <fangying1(a)huawei.com> Common VM users sometimes care about CPU speed, so we add two new options to allow VM vendors to present CPU speed to their users. Normally these information can be fetched from host smbios. --- v4 -> v3: - Rebase patch for lastest upstream v3 -> v4: - Fix the default value when not specifying "-smbios type=4" option; it would be 0 instead of 2000 in previous versions - Use uint64_t type to check value overflow - Add test case to check smbios type 4 CPU speed v2 -> v3: - Refine comments per Igor's suggestion. v1 -> v2: - change "_" in option names to "-" - check if option value is too large to fit in SMBIOS type 4 speed fields. --- Ying Fang (2): hw/smbios: add options for type 4 max-speed and current-speed tests/bios-tables-test: add smbios cpu speed test hw/smbios/smbios.c | 36 ++++++++++++++++++++++++++++++---- qemu-options.hx | 2 +- tests/bios-tables-test.c | 42 ++++++++++++++++++++++++++++++++++++++++ 3 files changed, 75 insertions(+), 5 deletions(-) -- 2.23.0

1 0