[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1888971] Re: SMI trigger causes hang with multiple cores
From: |
Laszlo Ersek (Red Hat) |
Subject: |
[Bug 1888971] Re: SMI trigger causes hang with multiple cores |
Date: |
Fri, 31 Jul 2020 09:44:41 -0000 |
> I guess fundamentally th issue is writing 0xXX in IO port 0xB2 should
> trigger SMI handler in all possible core but instead it triggers SMI
> only in Core#0.
For that, the guest needs to negotiate the "broadcast SMI" feature with
QEMU. See commit range 57bb40c9db40..b8bab8eb6934.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1888971
Title:
SMI trigger causes hang with multiple cores
Status in QEMU:
New
Bug description:
When using qemu , SMI trigger causes hang/reboot under following
conditions:
1. No KVM but there are more than 1 threads (-smp > 1)
2. When using KVM.
Info:
qemu-system-x86_64 --version
QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.29)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers
SMI trigger was done by writing 0x00 in IO port 0xB2.
Command:
No failure in SMI trigger when using the below command:
qemu-system-x86_64 -M pc-q35-bionic -smp 1 -bios build/coreboot.rom -serial
stdio -hda ../linux.img -m 2048 | tee 1.txt
Hang/resets with below commands:
qemu-system-x86_64 -M pc-q35-bionic -smp 2 -bios build/coreboot.rom -serial
stdio -hda ../linux.img -m 2048 | tee 1.txt
sudo qemu-system-x86_64 -M pc-q35-bionic,accel=kvm -smp 1 -bios
build/coreboot.rom -serial stdio -hda ../linux.img -m 2048 | tee
1.txt
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1888971/+subscriptions