Gregory Haskins wrote:
This patch adds baseline support for interrupt preemption. This lets one
context (virtual SMP vcpu, PV driver, etc) preempt another vcpu which is
currently in guest context when an interrupt is posted. The patch consists
of the following:
1) Re-worked the vcpu
On Fri, Mar 16, 2007 at 3:03 AM, in message [EMAIL PROTECTED],
Avi Kivity [EMAIL PROTECTED] wrote:
Gregory Haskins wrote:
This patch adds baseline support for interrupt preemption. This lets one
context (virtual SMP vcpu, PV driver, etc) preempt another vcpu which is
currently in guest
Heiko Carstens wrote:
On Sun, Mar 11, 2007 at 03:53:12PM +0200, Avi Kivity wrote:
This patchset updates the kvm userspace interface to what I hope will
be the long-term stable interface. Provisions are included for extending
the interface later. The patches address performance and
What is the distinction between kvm_regs and kvm_sregs? As far as I can
see, kvm_regs is only used when emulating IO, emulating MMIO, and
emulating CPUID, where guest GPRs are directly modified. kvm_sregs is
only used for full CPU state save (for later restore).
When the kernel had to use
diff --git a/drivers/kvm/kvm_main.c b/drivers/kvm/kvm_main.c
index 747966e..376538c 100644
--- a/drivers/kvm/kvm_main.c
+++ b/drivers/kvm/kvm_main.c
@@ -2416,6 +2416,12 @@ static long kvm_dev_ioctl(struct file *filp,
r = 0;
break;
}
+ case
Avi Kivity wrote:
I'd also like to add a read-only memory type so that apic reads can
proceed natively rather than be emulated (the TODO has this now).
I don't understand how this can work. Instead, we should use the
hardware-based virtualization for the local APIC.
Jun
---
Intel Open Source
Hi, my only complaint about qemu is that it isn't gcc4
friendly. It's unbelievable that a software still requires gcc 3,
since gcc3 is now an obsolete compiler...
Well, is there a patch or something like that to qemu so it
will compile and work using gcc 4?
Thank
