From: Weidong Han [EMAIL PROTECTED]
Add missing comma.
Signed-off-by: Weidong Han [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
diff --git a/qemu/monitor.c b/qemu/monitor.c
index 4cb6d54..291e850 100644
--- a/qemu/monitor.c
+++ b/qemu/monitor.c
@@ -1529,7 +1529,7 @@ static const
From: Xiantao Zhang [EMAIL PROTECTED]
kvm/ia64 have supported vt-d support from 2.6.28rc1, this patch
enables its userspace's support.
Signed-off-by: Xiantao Zhang [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
diff --git a/kernel/ia64/Kbuild b/kernel/ia64/Kbuild
index
From: Nitin A Kamble [EMAIL PROTECTED]
The code to traverse the cpuid data array list for counting type of leaves is
currently broken.
This patches fixes the 2 things in it.
1. Set the 1st counting entry's flag KVM_CPUID_FLAG_STATE_READ_NEXT. Without
it the code will never find a valid
From: Hollis Blanchard [EMAIL PROTECTED]
Bad page translation and silent guest failure ensue if the userspace address is
not page-aligned. I hit this problem using large (host) pages with qemu,
because qemu currently has a hardcoded 4096-byte alignment for guest memory
allocations.
Mark McLoughlin wrote:
The way I see this (continuing with your example figures) playing out
is:
- If we have a packet rate of 2.5K packets/sec, we essentially have
zero added latency - each packet causes a vmexit and the packet is
dispatched immediately
- As soon as we go above
Greg KH wrote:
It's that second part that I'm worried about. How is that going to
happen? Do you have any patches that show this kind of assignment?
For kvm, this is in 2.6.28-rc.
Note there are two ways to assign a device to a guest:
- run the VF driver in the guest: this has the
Muli Ben-Yehuda wrote:
We've been talking about avoiding hardware passthrough entirely and
just backing a virtio-net backend driver by a dedicated VF in the
host. That avoids a huge amount of guest-facing complexity, let's
migration Just Work, and should give the same level of performance.
Alexander Graf wrote:
Compat modules need to use kvm_on_each_cpu instead on on_each_cpu
in order to be compatible throughout various kernel versions.
Unfortunately preempt.c uses on_each_cpu. This patch changes preempt.c
to also use the kvm version, so it is compatible with the rest of the
Bill Rieske wrote:
The field within the Memory Device type 17 is only a word with the MSB being
used to report MB/KB. Thereby, a guest with 32G and greater would report
incorrect memory device information rolling over to 0.
This presents more than one memory device and associated memory
On Sun, Nov 09, 2008 at 12:11:03PM +0200, Avi Kivity wrote:
Matthew Garrett wrote:
Hmm. But we're seeing some machines that end up very confused if
rebooted via ACPI. I guess we need to run Vista on them to find out how
they behave. What OSI strings did your KVM setup expose? We know that
Hollis Blanchard wrote:
Bad page translation and silent guest failure ensue if the userspace address is
not page-aligned. I hit this problem using large (host) pages with qemu,
because qemu currently has a hardcoded 4096-byte alignment for guest memory
allocations.
Applied, thanks.
--
Andi Kleen wrote:
Anthony Liguori [EMAIL PROTECTED] writes:
What we would rather do in KVM, is have the VFs appear in the host as
standard network devices. We would then like to back our existing PV
driver to this VF directly bypassing the host networking stack. A key
feature here is being
Greg KH wrote:
We've been talking about avoiding hardware passthrough entirely and
just backing a virtio-net backend driver by a dedicated VF in the
host. That avoids a huge amount of guest-facing complexity, let's
migration Just Work, and should give the same level of performance.
Does
Matthew Garrett wrote:
Hmm. But we're seeing some machines that end up very confused if
rebooted via ACPI. I guess we need to run Vista on them to find out how
they behave. What OSI strings did your KVM setup expose? We know that
Windows changes behaviour under various circumstances depending
Eduardo Habkost wrote:
On Thu, Nov 06, 2008 at 12:30:51PM +0200, Avi Kivity wrote:
Eric W. Biederman wrote:
If you want to be extra simple and safe, remove kvm from the equation. Make the
disabling code part of kdump/emergency_restart and only rely on the convention
that cr3.vmxe ==
Jan Kiszka wrote:
Applied, thanks.
--
error compiling committee.c: too many arguments to function
--
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
the uni wrote:
Sorry, just realized what you meant
(qemu) info registers
EAX=f3b3 EBX=0012 ECX=e080 EDX=0012
ESI= EDI=0008fdba EBP=ffb0 ESP=ff9e
EIP=08d2 EFL=00033202 [---] CPL=3 II=0 A20=1 SMM=0 HLT=0
ES =0080 0800 f300
CS =f000 000f
Zhang, Xiantao wrote:
From 45b40eecff85b9a7ae4caf4ae184905a79e5a139 Mon Sep 17 00:00:00 2001
From: Xiantao Zhang [EMAIL PROTECTED]
Date: Fri, 7 Nov 2008 18:13:13 +0800
Subject: [PATCH] KVM: Userspace: Make device-assignment work for kvm/ia64.
kvm/ia64 have supported vt-d from 2.6.28rc1, this
Matthew Wilcox wrote:
What we would rather do in KVM, is have the VFs appear in the host as
standard network devices. We would then like to back our existing PV
driver to this VF directly bypassing the host networking stack. A key
feature here is being able to fill the VF's receive queue
Hi!
If we do resource rebalance after system is up, do you think there is any
side effect or impact to other subsystem other than PCI (e.g. MTRR)?
I don't think so.
I haven't had much thinking on the dynamical resource rebalance. If you
have any idea about this, can you please
If we do resource rebalance after system is up, do you think
there is any
side effect or impact to other subsystem other than PCI (e.g.
MTRR)?
I don't think so.
I haven't had much thinking on the dynamical resource rebalance.
If you
have any idea about this, can you please suggest?
Yeah,
Sam Ravnborg wrote:
I have a vague memory that 'select' will not propagate (what's the word?
transitive?) - -that is, the 'select KVM' will enable KVM but will not
cause ANON_INODES and PREEMPT_NOTIFIERS to be set.
I'm glad to say your memory in this case is wrong.
Me, too.
On Sun, Nov 09, 2008 at 02:44:06PM +0200, Avi Kivity wrote:
Greg KH wrote:
It's that second part that I'm worried about. How is that going to
happen? Do you have any patches that show this kind of assignment?
For kvm, this is in 2.6.28-rc.
Where? I just looked and couldn't find
hi,
i've to repeat myself old mail again:
http://article.gmane.org/gmane.comp.emulators.kvm.devel/18095
i see there is a lots of development in kvm lately. there are many
people working on many thing, but most of them improvements and
extensions. and those who read the list can see there are many
My mistake: $eip + 0xf would be more informative.
(qemu) x/40b $eip + 0xf
000f08d2: 0xf4 0xb8 0x6c 0x04 0x50 0x31 0xc0 0x50
000f08da: 0xe8 0xa6 0xf7 0x89 0xd3 0x83 0xc4 0x04
000f08e2: 0x89 0x46 0xf0 0x89 0x5e 0xf2 0x8b 0x46
000f08ea: 0xf4 0x8b 0x5e 0xf6
* On Friday 07 Nov 2008 15:55:18 Zhang, Xiantao wrote:
--- a/qemu/vl.c
+++ b/qemu/vl.c
@@ -8694,7 +8694,7 @@ static void help(int exitcode)
#endif
-no-kvm-irqchip disable KVM kernel mode PIC/IOAPIC/LAPIC\n
-no-kvm-pit disable KVM kernel mode PIT\n
-#if
Amit Shah wrote:
* On Friday 07 Nov 2008 15:55:18 Zhang, Xiantao wrote:
--- a/qemu/vl.c
+++ b/qemu/vl.c
@@ -8694,7 +8694,7 @@ static void help(int exitcode) #endif
-no-kvm-irqchip disable KVM kernel mode PIC/IOAPIC/LAPIC\n
-no-kvm-pit disable KVM kernel mode PIT\n
I think that's one of the things that distro's are good for.
On Nov 9, 2008, at 3:13 PM, Farkas Levente wrote:
hi,
i've to repeat myself old mail again:
http://article.gmane.org/gmane.comp.emulators.kvm.devel/18095
i see there is a lots of development in kvm lately. there are many
people
From 39ca008b144e1e729223b1302fcdd7a435370487 Mon Sep 17 00:00:00 2001
From: Weidong Han [EMAIL PROTECTED]
Date: Mon, 10 Nov 2008 14:33:43 +0800
Subject: [PATCH] support ioperm for vcpu hotplug
Track ioperm settings, when a new VCPU comes online, issue ioperm.
Signed-off-by: Weidong Han [EMAIL
Greg KH wrote:
On Sun, Nov 09, 2008 at 02:44:06PM +0200, Avi Kivity wrote:
Greg KH wrote:
It's that second part that I'm worried about. How is that going to
happen? Do you have any patches that show this kind of assignment?
For kvm, this is in 2.6.28-rc.
Where? I
Hollis Blanchard wrote:
Bad page translation and silent guest failure ensue if the userspace address is
not page-aligned. I hit this problem using large (host) pages with qemu,
because qemu currently has a hardcoded 4096-byte alignment for guest memory
allocations.
Applied, thanks.
--
31 matches
Mail list logo
