From: Avi Kivity [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
diff --git a/kernel/hack-module.awk b/kernel/hack-module.awk
index a9ac1f2..ac03a37 100644
--- a/kernel/hack-module.awk
+++ b/kernel/hack-module.awk
@@ -70,6 +70,8 @@ BEGIN { split(INIT_WORK, compat_apis); }
{
On Mon, Aug 11, 2008 at 07:39:34PM +1200, james wrote:
This is what libvirt gives you (and lots more, eg. secure remote
access to hypervisors, bindings to Perl many other languages, etc.).
Can you be more specfic about what you couldn't do with libvirt?
I can give you such an example
Mohammed Gamal wrote:
On Sun, Aug 10, 2008 at 11:09 AM, Avi Kivity [EMAIL PROTECTED] wrote:
Mohammed Gamal wrote:
This patch aims to allow emulation whenever guest state is not valid for
VMX operation. This usually happens in mode switches with guests such as
older versions of gfxboot
(Please use [EMAIL PROTECTED], not [EMAIL PROTECTED])
Dave Hansen wrote:
On my machine with gcc 3.4, kvm uses ~2k of stack in a few
select functions. This is mostly because gcc fails to
notice that the different case: statements could have their
stack usage combined. It overflows very nicely
Dave Hansen wrote:
Same as the last one, but this time we use kmalloc()
for all of the uses.
Note that the kfree()s take advantage of the fact that
kfree() is OK on NULL.
Signed-off-by: Dave Hansen [EMAIL PROTECTED]
---
virt/kvm/kvm_main.c | 48
Mohammed Gamal wrote:
The emulator only supported opcode 0xb8 for mov r,imm. However 0xb9-0xbf
are also mov r,imm. This patch adds support for these instructions.
Looks good, but I'd like to merge this together with a testcase.
--
error compiling committee.c: too many arguments to function
Mohammed Gamal wrote:
This patch adds instructions 'in' and 'out' to the x86 emulator.
+ SrcNone | ByteOp | ImplicitOps, SrcNone |ImplicitOps,
Missing blank.
case 0xe8: /* call (near) */ {
long int rel;
switch (c-op_bytes) {
@@ -1732,6
Bugs item #2042889, was opened at 2008-08-08 13:16
Message generated for change (Comment added) made by ravpl
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2042889group_id=180599
Please note that this message will contain a full copy of the comment
Gerd Hoffmann wrote:
Hi,
However, the pvclock_clocksource_read() implementation is
over-engineered, because it checks for an odd version and uses very
strong rmb() barriers (which generates either an lfence or lock add
$0, (%esp)).
If we're happy to guarantee as an ABI issue that the
Bugs item #2019608, was opened at 2008-07-16 17:03
Message generated for change (Comment added) made by henrikholst
You can respond by visiting:
https://sourceforge.net/tracker/?func=detailatid=893831aid=2019608group_id=180599
Please note that this message will contain a full copy of the comment
Hi,
I made some VM migrations between several machines
(Intel-Intel and Intel-AMD) and when one VM has been
migrated onto a second machine, I cannot put it
back on the first one. I talked with Laurent and it
seems that there is no way (or no obvious one)
to do that.
This could be useful when
On my machine with gcc 3.4, kvm uses ~2k of stack in a few
select functions. This is mostly because gcc fails to
notice that the different case: statements could have their
stack usage combined. It overflows very nicely if interrupts
happen during one of these large uses.
This patch uses two
Jean-Pierre Dion wrote:
Hi,
I made some VM migrations between several machines
(Intel-Intel and Intel-AMD) and when one VM has been
migrated onto a second machine, I cannot put it
back on the first one. I talked with Laurent and it
seems that there is no way (or no obvious one)
to do
Hi Avi,
Sorry, I got distracted from this ...
On Sat, 2008-07-26 at 12:45 +0300, Avi Kivity wrote:
Mark McLoughlin wrote:
1) The length of the tx mitigation timer makes quite a difference to
throughput achieved; we probably need a good heuristic for
adjusting this on the fly.
The current virtio_net tx timer is 2ns, which doesn't make
any sense. Set it to a more reasonable 250us instead.
However, even though we were requesting a 2ns tx timer, it
was actually getting limited to MIN_TIMER_REARM_US which is
currently 250us.
So, even though the timer itself would only
Signed-off-by: Mark McLoughlin [EMAIL PROTECTED]
---
qemu/vl.c | 26 +-
1 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/qemu/vl.c b/qemu/vl.c
index 126944d..f5aacf0 100644
--- a/qemu/vl.c
+++ b/qemu/vl.c
@@ -4369,19 +4369,6 @@ typedef struct TAPState {
Once we know we have buffers available on the receive ring, we can
safely disable notifications.
Signed-off-by: Mark McLoughlin [EMAIL PROTECTED]
---
qemu/hw/virtio-net.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/qemu/hw/virtio-net.c b/qemu/hw/virtio-net.c
The virtio-net driver is the only one which wishes to deal
with virtio_net_hdr headers, so add a using_vnet_hdr flag
to allow it to indicate this.
Preferably, we'd prefer to only enable IFF_VNET_HDR when
we're using virtio-net, but qemu's various abstractions
would make this very messy.
virtio_net tries to guess when it has received a tx
notification from the guest whether it indicates that the
guest has no more room in the tx ring and it should
immediately flush the queued buffers.
The heuristic is based on the fact that there are 128
buffer entries in the ring and each packet
The idea here is that with GSO, packets are much larger
and we can allow the vcpu threads to e.g. process irq
acks during the window where we're reading these
packets from the tapfd.
One known issue with this is that it triggers a subtle
SMP race in the kernel's posix-timers and signalfd code.
Set the VIRTIO_F_NOTIFY_ON_EMPTY feature bit so the
guest can rely on us notifying them when the queue
is empty.
Also, only notify when the available queue is empty
*and* when we've finished with all the buffers we
had detached. Right now, when the queue is empty,
we notify the guest for every
Now that GSO support doesn't break e.g. e1000, we can
enable it.
Signed-off-by: Mark McLoughlin [EMAIL PROTECTED]
---
qemu/vl.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/qemu/vl.c b/qemu/vl.c
index 9bfe480..14a66e0 100644
--- a/qemu/vl.c
+++
GSO packets uses up a lot more buffer entries, so double
the size of the rings
Signed-off-by: Mark McLoughlin [EMAIL PROTECTED]
---
qemu/hw/virtio-net.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/qemu/hw/virtio-net.c b/qemu/hw/virtio-net.c
index
Some management apps like libvirt creates a tap interface,
adds it to a bridge and then passes the fd to qemu-kvm.
Since we have no way of querying whether the IFF_VNET_HDR
flag has been enabled on the interface, the app needs to
tell us if has enabled it.
Signed-off-by: Mark McLoughlin [EMAIL
The tun/tap driver in 2.6.27 contains a new IFF_VNET_HDR
flag which makes every packet read from or written to the
tap fd be preceded by a virtio_net_hdr header.
This allows us to pass larger packets and packets with
partial checkums between the guest and the host, greatly
increasing the
Mark McLoughlin wrote:
Hi Avi,
Here's the set of patches that I think make sense to apply.
We probably need to disable checksum offload on the RX side until we
figure out what to do about the broken dhclient. That's going to hit a
lot of users otherwise.
Regards,
Anthony
Mark McLoughlin wrote:
Some management apps like libvirt creates a tap interface,
adds it to a bridge and then passes the fd to qemu-kvm.
Since we have no way of querying whether the IFF_VNET_HDR
flag has been enabled on the interface, the app needs to
tell us if has enabled it.
Sounds
From 40df689b23263ffe2f2efed9950700d42f985b29 Mon Sep 17 00:00:00 2001
From: Xiantao Zhang [EMAIL PROTECTED]
Date: Tue, 12 Aug 2008 08:15:10 +0800
Subject: [PATCH] KVM:Userspace: Fix build issue for IA64.
1. Generating asm-offset.h @ build time with host kernel
2. Make -C user doesn't support for
Ben-Ami Yassour wrote:
On Thu, 2008-08-07 at 09:21 +0800, Han, Weidong wrote:
Ben-Ami Yassour wrote:
On Wed, 2008-08-06 at 17:12 +0800, Han, Weidong wrote:
Ben-Ami Yassour wrote:
On Wed, 2008-08-06 at 14:18 +0800, Han, Weidong wrote:
Ben-Ami Yassour wrote:
On Tue, 2008-08-05 at 22:46 +0800,
29 matches
Mail list logo