Revision b5861e5cf2fcf83031ea3e26b0a69d887adf7d21 authored by Liran Alon on 03 September 2018, 12:20:22 UTC, committed by Radim Krčmář on 07 September 2018, 16:38:42 UTC
Consider the case L1 had a IRQ/NMI event until it executed VMLAUNCH/VMRESUME which wasn't delivered because it was disallowed (e.g. interrupts disabled). When L1 executes VMLAUNCH/VMRESUME, L0 needs to evaluate if this pending event should cause an exit from L2 to L1 or delivered directly to L2 (e.g. In case L1 don't intercept EXTERNAL_INTERRUPT). Usually this would be handled by L0 requesting a IRQ/NMI window by setting VMCS accordingly. However, this setting was done on VMCS01 and now VMCS02 is active instead. Thus, when L1 executes VMLAUNCH/VMRESUME we force L0 to perform pending event evaluation by requesting a KVM_REQ_EVENT. Note that above scenario exists when L1 KVM is about to enter L2 but requests an "immediate-exit". As in this case, L1 will disable-interrupts and then send a self-IPI before entering L2. Reviewed-by: Nikita Leshchenko <nikita.leshchenko@oracle.com> Co-developed-by: Sean Christopherson <sean.j.christopherson@intel.com> Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com> Signed-off-by: Liran Alon <liran.alon@oracle.com> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
1 parent 564ad0a
File | Mode | Size |
---|---|---|
1.Intro.rst | -rw-r--r-- | 14.3 KB |
2.Process.rst | -rw-r--r-- | 23.6 KB |
3.Early-stage.rst | -rw-r--r-- | 10.7 KB |
4.Coding.rst | -rw-r--r-- | 21.3 KB |
5.Posting.rst | -rw-r--r-- | 15.6 KB |
6.Followthrough.rst | -rw-r--r-- | 11.8 KB |
7.AdvancedTopics.rst | -rw-r--r-- | 9.5 KB |
8.Conclusion.rst | -rw-r--r-- | 3.1 KB |
adding-syscalls.rst | -rw-r--r-- | 26.2 KB |
applying-patches.rst | -rw-r--r-- | 16.9 KB |
changes.rst | -rw-r--r-- | 12.5 KB |
clang-format.rst | -rw-r--r-- | 6.4 KB |
code-of-conflict.rst | -rw-r--r-- | 1.4 KB |
coding-style.rst | -rw-r--r-- | 36.1 KB |
conf.py | -rw-r--r-- | 260 bytes |
development-process.rst | -rw-r--r-- | 810 bytes |
email-clients.rst | -rw-r--r-- | 10.8 KB |
howto.rst | -rw-r--r-- | 26.9 KB |
index.rst | -rw-r--r-- | 1.3 KB |
kernel-docs.rst | -rw-r--r-- | 24.2 KB |
kernel-driver-statement.rst | -rw-r--r-- | 4.1 KB |
kernel-enforcement-statement.rst | -rw-r--r-- | 4.9 KB |
license-rules.rst | -rw-r--r-- | 13.7 KB |
magic-number.rst | -rw-r--r-- | 10.2 KB |
maintainer-pgp-guide.rst | -rw-r--r-- | 37.1 KB |
management-style.rst | -rw-r--r-- | 13.1 KB |
stable-api-nonsense.rst | -rw-r--r-- | 9.3 KB |
stable-kernel-rules.rst | -rw-r--r-- | 6.6 KB |
submit-checklist.rst | -rw-r--r-- | 4.9 KB |
submitting-drivers.rst | -rw-r--r-- | 6.6 KB |
submitting-patches.rst | -rw-r--r-- | 36.8 KB |
volatile-considered-harmful.rst | -rw-r--r-- | 5.6 KB |
Computing file changes ...