On 19.10.2008, at 12:06, Avi Kivity wrote:
Alexander Graf wrote:
--- a/arch/x86/kvm/svm.c
+++ b/arch/x86/kvm/svm.c
@@ -51,6 +51,9 @@ MODULE_LICENSE("GPL");
/* Turn on to get debugging output*/
/* #define NESTED_DEBUG */
+/* Not needed until device passthrough */
+/* #define NESTED_KVM_MERGE_IOPM */
+
Let's assume device assignment is coming and drop the ifdefs.
Will device assignment work with in-guest IO Passthrough or will it
rather emulate the IO accesses in userspace by issuing them again?
So far we're talking about reissuing pio. The only case where the
guest and host pio are likely to have the same addresses is the vga
ports, and these aren't heavily used.
So it's better to leave it disabled, I guess. The IOPM is only
relevant when passing through IO ports 1:1. And parsing the IOPM takes
a lot of effort (read: time). It's also only relevant if the same
device, the guest is exposed to, is passed through to the l2 guest.
IMHO speed is more important atm.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html