X-Git-Url: http://ftp.safe.ca/?a=blobdiff_plain;f=Documentation%2Fkvm%2Fapi.txt;fp=Documentation%2Fkvm%2Fapi.txt;h=beb444a9501306a9f0e7f181284806c5c815d2e2;hb=679613442f84702c06a80f2320cb8a50089200bc;hp=c6416a398163155bc64341754b99039aba529502;hpb=1ef6ce7a340f9ed139a73147ff9cf7ad56889414;p=safe%2Fjmp%2Flinux-2.6

diff --git a/Documentation/kvm/api.txt b/Documentation/kvm/api.txt
index c6416a3..beb444a 100644
--- a/Documentation/kvm/api.txt
+++ b/Documentation/kvm/api.txt
@@ -820,6 +820,13 @@ executed a memory-mapped I/O instruction which could not be satisfied
 by kvm.  The 'data' member contains the written data if 'is_write' is
 true, and should be filled by application code otherwise.
 
+NOTE: For KVM_EXIT_IO and KVM_EXIT_MMIO, the corresponding operations
+are complete (and guest state is consistent) only after userspace has
+re-entered the kernel with KVM_RUN.  The kernel side will first finish
+incomplete operations and then check for pending signals.  Userspace
+can re-enter the guest with an unmasked signal pending to complete
+pending operations.
+
 		/* KVM_EXIT_HYPERCALL */
 		struct {
 			__u64 nr;