On Thu, 14 Oct 2010 01:24:12 -0300
Lucas Meneghel Rodrigues l...@redhat.com wrote:
Recent qemu can handle virtio without boot without boot=on,
and qemu.git will simply state the option as invalid. So
remove it from the default config on tests_base.cfg, just
leave it there commented in case
On Wed, Oct 13, 2010 at 12:47 AM, Lucas Meneghel Rodrigues
l...@redhat.com wrote:
On Tue, 2010-10-12 at 18:24 +0200, Avi Kivity wrote:
On 10/12/2010 06:18 PM, Lucas Meneghel Rodrigues wrote:
On Fri, 2010-10-08 at 15:02 -0300, Eduardo Habkost wrote:
On Thu, Oct 07, 2010 at 05:22:17PM -0300,
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm currently running -rc7). Effects disappears when
downgrading to kvm-kmod-2.6.35.6. Will see if I can bisect later, but
maybe someone
Michael S. Tsirkin m...@redhat.com wrote on 10/12/2010 10:39:07 PM:
Sorry for the delay, I was sick last couple of days. The results
with your patch are (%'s over original code):
Code BW% CPU% RemoteCPU
MQ (#txq=16) 31.4% 38.42% 6.41%
MQ+MST
On Thu, Oct 14, 2010 at 01:28:58PM +0530, Krishna Kumar2 wrote:
Michael S. Tsirkin m...@redhat.com wrote on 10/12/2010 10:39:07 PM:
Sorry for the delay, I was sick last couple of days. The results
with your patch are (%'s over original code):
Code BW% CPU%
These patches do the following changes.
1. Clean up:
- Making the similar parts as one shared function.
- modularizing the functions of SRAO and SRAR data setting.
2. Unify sigbus handling:
- kvm_handle_sigbus can handle both cases of SIGBUS listed as
And restruct this block to call kvm_mce_in_exception() only when it is
required.
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Tested-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
---
qemu-kvm.c | 15 +--
1 files changed, 9 insertions(+), 6 deletions(-)
diff --git
Share the same error handling.
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Tested-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
---
qemu-kvm.c | 31 +++
1 files changed, 19 insertions(+), 12 deletions(-)
diff --git a/qemu-kvm.c b/qemu-kvm.c
index
Share same error handing, and put it in #ifdef MCE i386.
Rename this function after MCIP (Machine Check In Progress) flag.
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Tested-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
---
qemu-kvm.c | 47
Refactor codes for maintainability.
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Tested-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
---
qemu-kvm.c | 96 ---
1 files changed, 58 insertions(+), 38 deletions(-)
diff
Pass a table instead of multiple args.
Note:
kvm_inject_x86_mce(env, bank, status, mcg_status, addr, misc,
abort_on_error);
is equal to:
struct kvm_x86_mce mce = {
.bank = bank,
.status = status,
.mcg_status = mcg_status,
.addr = addr,
.misc = misc,
};
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Tested-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
---
qemu-kvm.c | 14 +++---
1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/qemu-kvm.c b/qemu-kvm.c
index 0ba42fc..89ae524 100644
--- a/qemu-kvm.c
+++
There are 2 similar functions to handle SIGBUS:
sigbus_handler(int n, struct qemu_signalfd_siginfo *siginfo,
void *ctx)
kvm_on_sigbus(CPUState *env, siginfo_t *siginfo)
The former is used when main thread receives SIGBUS via signalfd,
while latter is used when vcpu thread
Now kvm_handle_sigbus can handle both cases of SIGBUS.
Note that env is NULL when main thread receives SIGBUS via
signalfd, otherwise env points vcpu thread that receives SIGBUS.
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Tested-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
Explicitly duplicate blocks for next cleanup.
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Tested-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
---
qemu-kvm.c | 56 +---
1 files changed, 33 insertions(+), 23 deletions(-)
Cleanup to finish unification.
Signed-off-by: Hidetoshi Seto seto.hideto...@jp.fujitsu.com
Tested-by: Jin Dongming jin.dongm...@np.css.fujitsu.com
---
qemu-kvm.c | 41 -
1 files changed, 12 insertions(+), 29 deletions(-)
diff --git a/qemu-kvm.c
There is no reason why SRAO event received by the main thread
is the only one that being broadcasted.
According to the x86 ASDM vol.3A 15.10.4.1,
MCE signal is broadcast on processor version 06H_EH or later.
This change is required to handle SRAR in the guest.
Signed-off-by: Hidetoshi Seto
Michael S. Tsirkin m...@redhat.com
What other shared TX/RX locks are there? In your setup, is the same
macvtap socket structure used for RX and TX? If yes this will create
cacheline bounces as sk_wmem_alloc/sk_rmem_alloc share a cache line,
there might also be contention on the lock
From: Gleb Natapov g...@redhat.com
Send async page fault to a PV guest if it accesses swapped out memory.
Guest will choose another task to run upon receiving the fault.
Allow async page fault injection only when guest is in user mode since
otherwise guest may be in non-sleepable context and
From: Gleb Natapov g...@redhat.com
If guest can detect that it runs in non-preemptable context it can
handle async PFs at any time, so let host know that it can send async
PF even if guest cpu is not in userspace.
Acked-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
From: Gleb Natapov g...@redhat.com
Async PF also needs to hook into smp_prepare_boot_cpu so move the hook
into generic code.
Acked-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
---
arch/x86/include/asm/kvm_para.h |1 +
arch/x86/kernel/kvm.c | 11
From: Gleb Natapov g...@redhat.com
When page is swapped in it is mapped into guest memory only after guest
tries to access it again and generate another fault. To save this fault
we can map it immediately since we know that guest is going to access
the page. Do it only when tdp is enabled for
From: Gleb Natapov g...@redhat.com
This patch add get_user_pages() variant that only succeeds if getting
a reference to a page doesn't require major fault.
Reviewed-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
---
fs/ncpfs/mmap.c|2 ++
include/linux/mm.h
From: Gleb Natapov g...@redhat.com
If guest indicates that it can handle async pf in kernel mode too send
it, but only if interrupts are enabled.
Acked-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
---
arch/x86/kvm/x86.c |3 ++-
1 files changed, 2
From: Gleb Natapov g...@redhat.com
If a guest accesses swapped out memory do not swap it in from vcpu thread
context. Schedule work to do swapping and put vcpu into halted state
instead.
Interrupts will still be delivered to the guest and if interrupt will
cause reschedule guest will continue to
From: Gleb Natapov g...@redhat.com
KVM virtualizes guest memory by means of shadow pages or HW assistance
like NPT/EPT. Not all memory used by a guest is mapped into the guest
address space or even present in a host memory at any given time.
When vcpu tries to access memory page that is not
From: Gleb Natapov g...@redhat.com
When async PF capability is detected hook up special page fault handler
that will handle async page fault events and bypass other page faults to
regular page fault handler. Also add async PF handling to nested SVM
emulation. Async PF always generates exit to L1
From: Gleb Natapov g...@redhat.com
If async page fault is received by idle task or when preemp_count is
not zero guest cannot reschedule, so do sti; hlt and wait for page to be
ready. vcpu can still process interrupts while it waits for the page to
be ready.
Acked-by: Rik van Riel
From: Gleb Natapov g...@redhat.com
Guest enables async PF vcpu functionality using this MSR.
Reviewed-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
---
Documentation/kvm/cpuid.txt |3 +++
Documentation/kvm/msr.txt | 36
From: Gleb Natapov g...@redhat.com
Keep track of memslots changes by keeping generation number in memslots
structure. Provide kvm_write_guest_cached() function that skips
gfn_to_hva() translation if memslots was not changed since previous
invocation.
Acked-by: Rik van Riel r...@redhat.com
Ignore this please. Something bad happened to From: header.
On Thu, Oct 14, 2010 at 11:16:58AM +0200, y...@redhat.com wrote:
From: Gleb Natapov g...@redhat.com
KVM virtualizes guest memory by means of shadow pages or HW assistance
like NPT/EPT. Not all memory used by a guest is mapped into
If guest indicates that it can handle async pf in kernel mode too send
it, but only if interrupts are enabled.
Acked-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
---
arch/x86/kvm/x86.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git
If async page fault is received by idle task or when preemp_count is
not zero guest cannot reschedule, so do sti; hlt and wait for page to be
ready. vcpu can still process interrupts while it waits for the page to
be ready.
Acked-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov
When async PF capability is detected hook up special page fault handler
that will handle async page fault events and bypass other page faults to
regular page fault handler. Also add async PF handling to nested SVM
emulation. Async PF always generates exit to L1 where vcpu thread will
be scheduled
Send async page fault to a PV guest if it accesses swapped out memory.
Guest will choose another task to run upon receiving the fault.
Allow async page fault injection only when guest is in user mode since
otherwise guest may be in non-sleepable context and will not be able
to reschedule.
Vcpu
This patch add get_user_pages() variant that only succeeds if getting
a reference to a page doesn't require major fault.
Reviewed-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
---
fs/ncpfs/mmap.c|2 ++
include/linux/mm.h |5 +
mm/filemap.c |
If guest can detect that it runs in non-preemptable context it can
handle async PFs at any time, so let host know that it can send async
PF even if guest cpu is not in userspace.
Acked-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
---
Documentation/kvm/msr.txt
If a guest accesses swapped out memory do not swap it in from vcpu thread
context. Schedule work to do swapping and put vcpu into halted state
instead.
Interrupts will still be delivered to the guest and if interrupt will
cause reschedule guest will continue to run another task.
Acked-by: Rik
Async PF also needs to hook into smp_prepare_boot_cpu so move the hook
into generic code.
Acked-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
---
arch/x86/include/asm/kvm_para.h |1 +
arch/x86/kernel/kvm.c | 11 +++
KVM virtualizes guest memory by means of shadow pages or HW assistance
like NPT/EPT. Not all memory used by a guest is mapped into the guest
address space or even present in a host memory at any given time.
When vcpu tries to access memory page that is not mapped into the guest
address space KVM
Keep track of memslots changes by keeping generation number in memslots
structure. Provide kvm_write_guest_cached() function that skips
gfn_to_hva() translation if memslots was not changed since previous
invocation.
Acked-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov
Guest enables async PF vcpu functionality using this MSR.
Reviewed-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
---
Documentation/kvm/cpuid.txt |3 +++
Documentation/kvm/msr.txt | 36 +++-
Enable async PF in a guest if async PF capability is discovered.
Acked-by: Rik van Riel r...@redhat.com
Signed-off-by: Gleb Natapov g...@redhat.com
---
Documentation/kernel-parameters.txt |3 +
arch/x86/include/asm/kvm_para.h |6 ++
arch/x86/kernel/kvm.c | 92
This patch is for Ping6 testing
* ping6 with various message sizes guest to/from local/remote host
using link-local addresses
By default IPv6 seems to be disabled on virbr0. Enable it by
doing echo 0 /proc/sys/net/ipv6/conf/virbr0/disable_ipv6
Please find the below
When page is swapped in it is mapped into guest memory only after guest
tries to access it again and generate another fault. To save this fault
we can map it immediately since we know that guest is going to access
the page. Do it only when tdp is enabled for now. Shadow paging case is
more
Changes for tests_base.cfg to include ping6 test
Please find below attached patch.
Thanks
Pradeep
ipv6_2
Description: Binary data
On Thu, Oct 14, 2010 at 02:56:59PM +0530, pradeep wrote:
This patch is for Ping6 testing
* ping6 with various message sizes guest to/from local/remote host
using link-local addresses
By default IPv6 seems to be disabled on virbr0. Enable it by
doing echo 0
On 10/11/2010 08:31 PM, Marcelo Tosatti wrote:
Port qemu-kvm's KVM MCE (Machine Check Exception) handling to qemu. It
allows qemu to propagate MCEs to the guest.
v2:
- rename do_qemu_ram_addr_from_host.
- fix kvm_on_sigbus/kvm_on_sigbus_vcpu naming.
- fix bank register restoration (Dean
On 10/10/2010 05:46 PM, Gleb Natapov wrote:
We should log both errno and exit_reason. If we want to be clever,
we can display strerror(errno) if it's nonzero, and exit_reason
otherwise (easy to do in a trace-cmd plugin).
For starters we should remove KVM_EXIT_INTR exit reason. Looking
On Thu, Oct 14, 2010 at 12:27:15PM +0200, Avi Kivity wrote:
On 10/10/2010 05:46 PM, Gleb Natapov wrote:
We should log both errno and exit_reason. If we want to be clever,
we can display strerror(errno) if it's nonzero, and exit_reason
otherwise (easy to do in a trace-cmd plugin).
On Thu, 14 Oct 2010 18:05:04 +0800
Amos Kong ak...@redhat.com wrote:
On Thu, Oct 14, 2010 at 02:56:59PM +0530, pradeep wrote:
This patch is for Ping6 testing
* ping6 with various message sizes guest to/from local/remote
host using link-local addresses
By default IPv6 seems
On 10/14/2010 12:29 PM, Gleb Natapov wrote:
On Thu, Oct 14, 2010 at 12:27:15PM +0200, Avi Kivity wrote:
On 10/10/2010 05:46 PM, Gleb Natapov wrote:
We should log both errno and exit_reason. If we want to be clever,
we can display strerror(errno) if it's nonzero, and exit_reason
On Thu, Oct 14, 2010 at 01:11:20PM +0200, Avi Kivity wrote:
On 10/14/2010 12:29 PM, Gleb Natapov wrote:
On Thu, Oct 14, 2010 at 12:27:15PM +0200, Avi Kivity wrote:
On 10/10/2010 05:46 PM, Gleb Natapov wrote:
We should log both errno and exit_reason. If we want to be clever,
On 10/14/2010 01:28 PM, Gleb Natapov wrote:
On Thu, Oct 14, 2010 at 01:11:20PM +0200, Avi Kivity wrote:
On 10/14/2010 12:29 PM, Gleb Natapov wrote:
On Thu, Oct 14, 2010 at 12:27:15PM +0200, Avi Kivity wrote:
On 10/10/2010 05:46 PM, Gleb Natapov wrote:
We should log
On Thu, Oct 14, 2010 at 01:32:14PM +0200, Avi Kivity wrote:
On 10/14/2010 01:28 PM, Gleb Natapov wrote:
On Thu, Oct 14, 2010 at 01:11:20PM +0200, Avi Kivity wrote:
On 10/14/2010 12:29 PM, Gleb Natapov wrote:
On Thu, Oct 14, 2010 at 12:27:15PM +0200, Avi Kivity wrote:
On 10/10/2010
On Thu, Oct 14, 2010 at 01:43:52PM +0200, Avi Kivity wrote:
On 10/14/2010 01:41 PM, Gleb Natapov wrote:
So what do you propose? I see no issue with my original patch.
Record both errno and exit_reason. While they're never both valid
at the same time, they're both
Breaks otherwise if CONFIG_IOMMU_API is not set.
Signed-off-by: Jan Kiszka jan.kis...@siemens.com
---
include/linux/kvm_host.h |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index 0b89d00..866ed30 100644
---
On 10/14/2010 09:27 AM, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm currently running -rc7). Effects disappears when
downgrading to kvm-kmod-2.6.35.6. Will
On 10/14/2010 12:54 AM, Anthony Liguori wrote:
On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
Hi,
Using the legacy way of starting up NICs, I am hitting a limitation
after 29
NICs ie no more than 29 are detected (that's because of the 32 PCI slot
limit on a single bus- 3 are already taken
On 10/14/2010 01:47 PM, Gleb Natapov wrote:
You can always filter excess information away. If you're looking
for exits to userspace (a major performance issue) then you want to
see both normal exits and signal exits.
How do I do it via /debug file system? Now I just echo name of the
On 10/14/2010 02:09 PM, Avi Kivity wrote:
On 10/14/2010 01:47 PM, Gleb Natapov wrote:
You can always filter excess information away. If you're looking
for exits to userspace (a major performance issue) then you want to
see both normal exits and signal exits.
How do I do it via /debug
Am 14.10.2010 09:27, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm currently running -rc7). Effects disappears when
downgrading to kvm-kmod-2.6.35.6. Will
On 10/14/2010 02:04 PM, Avi Kivity wrote:
On 10/14/2010 09:27 AM, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm currently running -rc7). Effects disappears
On Thu, Oct 14, 2010 at 02:07:17PM +0200, Avi Kivity wrote:
On 10/14/2010 12:54 AM, Anthony Liguori wrote:
On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
Hi,
Using the legacy way of starting up NICs, I am hitting a limitation
after 29
NICs ie no more than 29 are detected (that's
Am 14.10.2010 14:11, Avi Kivity wrote:
On 10/14/2010 02:04 PM, Avi Kivity wrote:
On 10/14/2010 09:27 AM, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm
On 10/14/2010 02:10 PM, Jan Kiszka wrote:
Am 14.10.2010 09:27, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm currently running -rc7). Effects
Krishna Kumar2/India/IBM wrote on 10/14/2010 02:34:01 PM:
void vhost_poll_queue(struct vhost_poll *poll)
{
struct vhost_virtqueue *vq = vhost_find_vq(poll);
vhost_work_queue(vq, poll-work);
}
Since poll batches packets, find_vq does not seem to add much
to the CPU
On 10/14/2010 02:13 PM, Avi Kivity wrote:
and this commit just makes the
corruptions more likely. This may even be a QEMU issue in the cirrus/vga
model (both qemu-kvm and upstream show the effect).
What about -no-kvm?
Doesn't happen there.
My guess is the initial dirty log after the
Am 14.10.2010 14:13, Avi Kivity wrote:
On 10/14/2010 02:10 PM, Jan Kiszka wrote:
Am 14.10.2010 09:27, Jan Kiszka wrote:
Hi,
I'm seeing quite frequent corruptions of the VESA frame buffer with
Linux guests (vga=0x317) that are starting with KVM kernel modules of
upcoming 2.6.36 (I'm
Avi Kivity a...@redhat.com writes:
On 10/14/2010 12:54 AM, Anthony Liguori wrote:
On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
Hi,
Using the legacy way of starting up NICs, I am hitting a limitation
after 29
NICs ie no more than 29 are detected (that's because of the 32 PCI slot
limit
On 10/14/2010 02:36 PM, Jan Kiszka wrote:
and this commit just makes the
corruptions more likely. This may even be a QEMU issue in the cirrus/vga
model (both qemu-kvm and upstream show the effect).
What about -no-kvm?
Just booted it (took ages), and the result was actually a
Am 14.10.2010 13:59, Jan Kiszka wrote:
Breaks otherwise if CONFIG_IOMMU_API is not set.
Actually, it only broke a special local version. It doesn't break with
current KVM due to
[__kvm_set_memory_region:]
#ifdef CONFIG_DMAR
/* map the pages in iommu page table */
if (npages) {
Krishna Kumar2/India/IBM wrote on 10/14/2010 05:47:54 PM:
Sorry, it should read txq=8 below.
- KK
There's a significant reduction in CPU/SD utilization with your
patch. Following is the performance of ORG vs MQ+mm patch:
_
Org
On 10/14/2010 07:07 AM, Avi Kivity wrote:
On 10/14/2010 12:54 AM, Anthony Liguori wrote:
On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
Hi,
Using the legacy way of starting up NICs, I am hitting a limitation
after 29
NICs ie no more than 29 are detected (that's because of the 32 PCI slot
On 10/14/2010 07:10 AM, Daniel P. Berrange wrote:
On Thu, Oct 14, 2010 at 02:07:17PM +0200, Avi Kivity wrote:
On 10/14/2010 12:54 AM, Anthony Liguori wrote:
On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
Hi,
Using the legacy way of starting up NICs, I am hitting a
On 10/14/2010 07:36 AM, Markus Armbruster wrote:
Avi Kivitya...@redhat.com writes:
On 10/14/2010 12:54 AM, Anthony Liguori wrote:
On 10/13/2010 05:32 PM, Anjali Kulkarni wrote:
Hi,
Using the legacy way of starting up NICs, I am hitting a limitation
after 29
NICs ie no
On 10/14/2010 02:54 PM, Anthony Liguori wrote:
The key is to make the virtio-net devices multifunction and to fill
out all 8 functions for each slot.
This is unlikely to work right wrt pci hotplug.
Yes. Our hotplug design is based on devices.. This is wrong, it
should be based on
On Tue, Sep 14, 2010 at 1:56 AM, H. Peter Anvin h...@zytor.com wrote:
On 09/13/2010 06:37 PM, Amos Kong wrote:
I've heard wonderful music (guest:win7), but mixed with a litte noise, not
so fluent.
The following debug msg is normal?
Yes, all of that is normal. I talked to malc earlier
On 10/14/2010 08:23 AM, Avi Kivity wrote:
On 10/14/2010 02:54 PM, Anthony Liguori wrote:
The key is to make the virtio-net devices multifunction and to fill
out all 8 functions for each slot.
This is unlikely to work right wrt pci hotplug.
Yes. Our hotplug design is based on devices..
On 10/14/2010 04:11 PM, Anthony Liguori wrote:
On 10/14/2010 08:23 AM, Avi Kivity wrote:
On 10/14/2010 02:54 PM, Anthony Liguori wrote:
The key is to make the virtio-net devices multifunction and to
fill out all 8 functions for each slot.
This is unlikely to work right wrt pci hotplug.
On 10/14/2010 06:51 AM, Mike Snitzer wrote:
Was just wondering if you've been able to put some time to the
rate-matching issues?
Has this usb-audio patch evolved and I'm just missing it?
Thanks for doing this work!
Mike
The sad result really is: it doesn't work, and it probably will
On 10/10/2010 12:44 PM, Alexander Graf wrote:
Hi Marcelo / Avi,
Scott has found some bugs in the BookE implementation of KVM, so please pull
the fixes for them to the kvm tree.
The following changes since commit 3c4504636ab1ff41ec162980bf85121aee14e58f:
Huang Ying (1):
KVM: MCE:
- H. Peter Anvin h...@zytor.com wrote:
On 10/14/2010 06:51 AM, Mike Snitzer wrote:
Was just wondering if you've been able to put some time to the
rate-matching issues?
Has this usb-audio patch evolved and I'm just missing it?
Thanks for doing this work!
Mike
The sad
On Thu, Oct 14, 2010 at 12:25:34PM +0200, Avi Kivity wrote:
On 10/11/2010 08:31 PM, Marcelo Tosatti wrote:
Port qemu-kvm's KVM MCE (Machine Check Exception) handling to qemu. It
allows qemu to propagate MCEs to the guest.
v2:
- rename do_qemu_ram_addr_from_host.
- fix
On 10/14/2010 09:18 AM, Alon Levy wrote:
Can you elaborate?
The quality of rate information is too low, and the delays in the system
are too large to enable consistent convergence.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on
We can't let the compiler define the alignment for qemu_cfg data.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
0.13 stable candidate?
hw/pc.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
index 69b13bf..90839bd 100644
---
Otherwise the guest might try to use the range for device hotplug.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/vga.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/hw/vga.c b/hw/vga.c
index 966185e..90f9dc0 100644
--- a/hw/vga.c
+++
On 10/14/10 20:33, Alex Williamson wrote:
We can't let the compiler define the alignment for qemu_cfg data.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
0.13 stable candidate?
ACK I would say so.
Jes
--
To unsubscribe from this list: send the line unsubscribe kvm in
the
On 10/14/2010 02:44 PM, Jes Sorensen wrote:
On 10/14/10 20:33, Alex Williamson wrote:
We can't let the compiler define the alignment for qemu_cfg data.
Signed-off-by: Alex Williamsonalex.william...@redhat.com
---
0.13 stable candidate?
ACK I would say so.
fw_cfg interfaces
On Thu, 2010-10-14 at 14:48 -0500, Anthony Liguori wrote:
On 10/14/2010 02:44 PM, Jes Sorensen wrote:
On 10/14/10 20:33, Alex Williamson wrote:
We can't let the compiler define the alignment for qemu_cfg data.
Signed-off-by: Alex Williamsonalex.william...@redhat.com
---
0.13
On 10/14/2010 02:58 PM, Alex Williamson wrote:
On Thu, 2010-10-14 at 14:48 -0500, Anthony Liguori wrote:
On 10/14/2010 02:44 PM, Jes Sorensen wrote:
On 10/14/10 20:33, Alex Williamson wrote:
We can't let the compiler define the alignment for qemu_cfg data.
Signed-off-by:
On Thursday 14 October 2010 21:58:08 Alex Williamson wrote:
If it works anywhere (I assume it works on 32bit), then it's only
because it happened to get the alignment right. This just makes 64bit
hosts get it right too. I don't see any compatibility issues,
non-packed + 64bit = broken.
On Thu, 2010-10-14 at 22:20 +0200, Arnd Bergmann wrote:
On Thursday 14 October 2010 21:58:08 Alex Williamson wrote:
If it works anywhere (I assume it works on 32bit), then it's only
because it happened to get the alignment right. This just makes 64bit
hosts get it right too. I don't see
On Thursday 14 October 2010 22:59:04 Alex Williamson wrote:
The structs in question only contain 4 8 byte elements, so there
shouldn't be any change on x86-32 using one-byte aligned packing.
I'm talking about the alignment of the structure, not the members
within the structure. The data
Hi,
I'm starting a thread related to the TODO item mentioned in the
subject. Currently still gathering info and trying to make kvm
macvtap play nicely together. I have used this [1] guide to set it up
but qemu is still complaining about the PCI device address of the
virtio-net-pci. Tried
On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel P. Berrange wrote:
Or a PCI bridge to wire up more PCI buses, so we raise the max limit for
any type of device we emulate.
Break the 29/30/31 virtio-blk limit ... please!
Rich.
--
Richard Jones, Virtualization Group, Red Hat
Can you send me pointers to the qdev documentation? How can I use it? Will
it allow us to scale above the 32 PCI limit?
Anjali
On 10/14/10 2:57 PM, Anthony Liguori anth...@codemonkey.ws wrote:
On 10/14/2010 04:42 PM, Richard W.M. Jones wrote:
On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel
On Thu, Oct 14, 2010 at 04:57:36PM -0500, Anthony Liguori wrote:
On 10/14/2010 04:42 PM, Richard W.M. Jones wrote:
On Thu, Oct 14, 2010 at 01:10:47PM +0100, Daniel P. Berrange wrote:
Or a PCI bridge to wire up more PCI buses, so we raise the max limit for
any type of device we emulate.
Break
On 10/14/2010 05:00 PM, Anjali Kulkarni wrote:
Can you send me pointers to the qdev documentation? How can I use it? Will
it allow us to scale above the 32 PCI limit?
It's all below. You just have to create a PCI device and mark the
multifunction flag to on and then assign it a PCI
Thanks. Does this work for e1000 as well?
Also, does it support pci hotplug?
Anjali
On 10/14/10 3:09 PM, Anthony Liguori anth...@codemonkey.ws wrote:
On 10/14/2010 05:00 PM, Anjali Kulkarni wrote:
Can you send me pointers to the qdev documentation? How can I use it? Will
it allow us to scale
1 - 100 of 112 matches
Mail list logo
