Branch: refs/heads/next
Home: https://github.com/siemens/jailhouse
Commit: dd6269a94a50d091d5a76fe4011e5fc491e5bcc6
https://github.com/siemens/jailhouse/commit/dd6269a94a50d091d5a76fe4011e5fc491e5bcc6
Author: Jan Kiszka <jan.kis...@siemens.com>
Date: 2018-10-08 (Mon, 08 Oct 2018)
Changed paths:
M driver/cell.c
Log Message:
-----------
driver: x86: Catch unsupported assignment of CPU 0 to non-root cells
Due to the way how CPU 0 is offlined on x86, we cannot "steal" it from
the root cell and give it to a different owner. Catch any configuration
that tries to do so and reject this attempt.
Signed-off-by: Jan Kiszka <jan.kis...@siemens.com>
Commit: e20fe893a8a6b3108f06c96fd505732fd52aeda0
https://github.com/siemens/jailhouse/commit/e20fe893a8a6b3108f06c96fd505732fd52aeda0
Author: Jan Kiszka <jan.kis...@siemens.com>
Date: 2018-10-08 (Mon, 08 Oct 2018)
Changed paths:
M hypervisor/arch/x86/apic.c
Log Message:
-----------
x86: Clarify and improve rejection of NMI IPIs
While technically doable, re-injecting NMIs from the hypervisor into a
guest is far from being simple. On Intel, we need to take care of
various cases where injection could have failed. On AMD, it even takes
single-stepping over the IRET instruction in order to get to the end of
an NMI-blocking window.
So, remove the to-do note, replacing it with a hint that NMI IPIs will
likely remain unsupported for a longer time. At this chance augment the
printed message with the target CPU of the IPI. This may help to
correlate the effect of a missing NMI or the reason for the injection
(stalled CPU).
Signed-off-by: Jan Kiszka <jan.kis...@siemens.com>
Compare:
https://github.com/siemens/jailhouse/compare/06e3ecb5eefc...e20fe893a8a6
**NOTE:** This service has been marked for deprecation:
https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
