At Fri, 21 May 2010 06:28:42 +0100,
Stefan Hajnoczi wrote:
On Thu, May 20, 2010 at 11:16 PM, Christian Brunner c...@muc.de wrote:
2010/5/20 Anthony Liguori anth...@codemonkey.ws:
Both sheepdog and ceph ultimately transmit I/O over a socket to a central
daemon, right? So could we not
On Thursday 20 May 2010 17:46:40 Avi Kivity wrote:
On 05/20/2010 12:16 PM, Sheng Yang wrote:
From: Dexuan Cuidexuan@intel.com
Enable XSAVE/XRSTORE for guest.
Change from V2:
Addressed comments from Avi.
Change from V1:
1. Use FPU API.
2. Fix CPUID issue.
3.
On 15.05.2010 10:26, Alexander Graf wrote:
On S390, I'm also still sceptical if the implementation we have really works. A
device injects an S390_INTERRUPT with its address and on the next vcpu_run, an
according interrupt is issued. But what happens if two devices trigger an
S390_INTERRUPT
On 05/21/2010 10:26 AM, Sheng Yang wrote:
+
+static void update_cpuid(struct kvm_vcpu *vcpu)
+{
+ struct kvm_cpuid_entry2 *best;
+
+ best = kvm_find_cpuid_entry(vcpu, 1, 0);
+ if (!best)
+ return;
+
+ /* Update OSXSAVE bit */
+ if (cpu_has_xsave
From: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
include/linux/skbuff.h | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git
From: Xin Xiaohui xiaohui@intel.com
If the driver want to allocate external buffers,
then it can export it's capability, as the skb
buffer header length, the page length can be DMA, etc.
The external buffers owner may utilize this.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
From: Xin Xiaohui xiaohui@intel.com
Currently, it can get external buffers from mp device.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
include/linux/skbuff.h | 12
From: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
include/linux/netdevice.h |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git
From: Xin Xiaohui xiaohui@intel.com
If buffer is external, then use the callback to destruct
buffers.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
net/core/skbuff.c | 11 +++
1 files
From: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
net/core/dev.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/net/core/dev.c
From: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
include/linux/mpassthru.h | 25 +
1 files changed, 25 insertions(+), 0 deletions(-)
From: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
drivers/vhost/Kconfig | 10 ++
drivers/vhost/Makefile |2 ++
2 files changed, 12 insertions(+), 0 deletions(-)
diff --git
From: Xin Xiaohui xiaohui@intel.com
Currently, vhost-net is only user to the mp device.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
drivers/vhost/mpassthru.c | 330
From: Xin Xiaohui xiaohui@intel.com
The vhost-net backend now only supports synchronous send/recv
operations. The patch provides multiple submits and asynchronous
notifications. This is needed for zero-copy case.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
---
From: Xin, Xiaohuixiaohui@intel.com
How external buffer comes from, how to destroy.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
drivers/vhost/mpassthru.c | 253
From: Xin Xiaohui xiaohui@intel.com
The ioctl is used by mp device to bind an underlying
NIC, it will query hardware capability and declare the
NIC to use external buffers.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike
From: Xin Xiaohui xiaohui@intel.com
The hook is called in netif_receive_skb().
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
net/core/dev.c | 35 +++
1 files
From: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
net/core/skbuff.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/net/core/skbuff.c
From: Xin Xiaohui xiaohui@intel.com
Make the skb-data and skb-head from external buffer
to be consistent, we ignore the room reserved by driver
for kernel skb.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike
From: Xin Xiaohui xiaohui@intel.com
Add a dev parameter to __alloc_skb(), skb-data
points to external buffer, recompute skb-head,
maintain shinfo of the external buffer, record
external buffer info into destructor_arg field.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by:
From: Xin Xiaohui xiaohui@intel.com
The external buffer owner can use the functions to get
the capability of the underlying NIC driver.
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
From: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
include/linux/netdevice.h |3 +++
net/core/dev.c| 28
2 files
From: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Xin Xiaohui xiaohui@intel.com
Signed-off-by: Zhao Yu yzhao81...@gmail.com
Reviewed-by: Jeff Dike jd...@linux.intel.com
---
include/linux/netdevice.h | 19 ++-
1 files changed, 18 insertions(+), 1 deletions(-)
diff
We provide an zero-copy method which driver side may get external
buffers to DMA. Here external means driver don't use kernel space
to allocate skb buffers. Currently the external buffer can be from
guest virtio-net driver.
The idea is simple, just to pin the guest VM user space and then
let host
Trace events in QEMU/KVM can be very useful for debugging and performance
analysis. I'd like to discuss tracing support and hope others have an interest
in this feature, too.
Following this email are patches I am using to debug virtio-blk and storage.
The patches provide trivial tracing support,
Trace events should be defined in trace.h. Events are written to
/tmp/trace.log and can be formatted using trace.py. Remember to add
events to trace.py for pretty-printing.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
Makefile.objs |2 +-
trace.c | 64
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
block.c|7 +++
hw/virtio-blk.c|6 ++
posix-aio-compat.c |2 ++
trace.h| 42 +-
trace.py |8
5 files changed, 64
On 02/27/2010 12:38 AM, Antoine Martin wrote:
1 0 0 98 0 1| 0 0 | 66B 354B| 0 0 | 3011
1 1 0 98 0 0| 0 0 | 66B 354B| 0 0 | 2911
From that point onwards, nothing will happen.
The host has disk IO to spare... So what is it waiting for??
I should have used the [RFC] tag to make it clear that I'm not
proposing these patches for merge, sorry.
Stefan
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Stefan Hajnoczi wrote:
Trace events should be defined in trace.h. Events are written to
/tmp/trace.log and can be formatted using trace.py. Remember to add
events to trace.py for pretty-printing.
When already writing to a file, why not reusing QEMU's logging
infrastructure (log foo / -d
Hi Stefan,
Nice to see the patchset.
I am working on something similar, on the lines of static trace events
for QEMU, that collect traces in a qemu-internal buffer. This would
employ monitor commands to read traces, as well as enable/disable trace
events at runtime.
I plan to post a
Am 20.05.2010 07:36, schrieb MORITA Kazutaka:
This patch enables protocol drivers to use their create options which
are not supported by the format. For example, protcol drivers can use
a backing_file option with raw format.
Signed-off-by: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
Hm,
On 05/12/10 12:41, Harald Dunkel wrote:
Hi folks,
I am trying to run Solaris 10u8 as a guest in kvm (kernel
2.6.33.2). Problem: The virtual network devices don't work
with this Solaris version.
Short update: Virtualbox 3.1.6 seems to be more reliable in
this case.
Regards
Harri
--
To
On 05/21/2010 04:42 AM, Stefan Hajnoczi wrote:
Trace events should be defined in trace.h. Events are written to
/tmp/trace.log and can be formatted using trace.py. Remember to add
events to trace.py for pretty-printing.
Signed-off-by: Stefan Hajnoczistefa...@linux.vnet.ibm.com
---
So, what's the current state of the bug tracking system?
As far as I can see, qemu is moving to launchpad.
Where qemu-kvm-related issues should be submitted nowadays?
Thanks!
/mjt
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to
On Fri, May 21, 2010 at 12:13 PM, Jan Kiszka jan.kis...@siemens.com wrote:
Stefan Hajnoczi wrote:
Trace events should be defined in trace.h. Events are written to
/tmp/trace.log and can be formatted using trace.py. Remember to add
events to trace.py for pretty-printing.
When already
Stefan Hajnoczi wrote:
On Fri, May 21, 2010 at 12:13 PM, Jan Kiszka jan.kis...@siemens.com wrote:
Stefan Hajnoczi wrote:
Trace events should be defined in trace.h. Events are written to
/tmp/trace.log and can be formatted using trace.py. Remember to add
events to trace.py for
21.05.2010 16:36, Harald Dunkel wrote:
On 05/12/10 12:41, Harald Dunkel wrote:
Hi folks,
I am trying to run Solaris 10u8 as a guest in kvm (kernel
2.6.33.2). Problem: The virtual network devices don't work
with this Solaris version.
Short update: Virtualbox 3.1.6 seems to be more reliable in
Anthony Liguori wrote:
On 05/21/2010 04:42 AM, Stefan Hajnoczi wrote:
Trace events should be defined in trace.h. Events are written to
/tmp/trace.log and can be formatted using trace.py. Remember to add
events to trace.py for pretty-printing.
Signed-off-by: Stefan
On 05/21/2010 08:46 AM, Jan Kiszka wrote:
Anthony Liguori wrote:
On 05/21/2010 04:42 AM, Stefan Hajnoczi wrote:
Trace events should be defined in trace.h. Events are written to
/tmp/trace.log and can be formatted using trace.py. Remember to add
events to trace.py for
There are almost impossible to debug.
Try copying vmlinux out of your guest and attach with gdb when it
hangs. Then issue the command
(gdb) thread apply all backtrace
to see what the guest is doing.
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
On 5/20/2010 3:22 PM, Paul Menage wrote:
On Tue, May 18, 2010 at 5:04 PM, Sridhar Samudrala
samudrala.srid...@gmail.com wrote:
Add a new kernel API to attach a task to current task's cgroup
in all the active hierarchies.
Signed-off-by: Sridhar Samudralas...@us.ibm.com
Reviewed-by:
On 05/21/2010 04:16 PM, Riccardo wrote:
...
There are almost impossible to debug.
Try copying vmlinux out of your guest and attach with gdb when it
hangs. Then issue the command
(gdb) thread apply all backtrace
to see what the guest is doing.
--
Do not meddle in the internals of
-- Original Message ---
From: Avi Kivity a...@redhat.com
To: Riccardo andrighetto.ricca...@gmail.com
Cc: kvm@vger.kernel.org
Sent: Fri, 21 May 2010 18:21:20 +0300
Subject: Re: Gentoo guest with smp: emerge freeze while recompile world
On 05/21/2010 04:16 PM, Riccardo
On 05/21/2010 07:45 AM, Michael Tokarev wrote:
So, what's the current state of the bug tracking system?
As far as I can see, qemu is moving to launchpad.
Where qemu-kvm-related issues should be submitted nowadays?
Kernel issues should be filed in bugzilla.kernel.org.
qemu issues should be
On 05/21/2010 06:50 PM, Anthony Liguori wrote:
On 05/21/2010 07:45 AM, Michael Tokarev wrote:
So, what's the current state of the bug tracking system?
As far as I can see, qemu is moving to launchpad.
Where qemu-kvm-related issues should be submitted nowadays?
Kernel issues should be filed in
21.05.2010 19:56, Avi Kivity wrote:
On 05/21/2010 06:50 PM, Anthony Liguori wrote:
On 05/21/2010 07:45 AM, Michael Tokarev wrote:
So, what's the current state of the bug tracking system?
As far as I can see, qemu is moving to launchpad.
Where qemu-kvm-related issues should be submitted
On Friday, May 21, 2010 10:46:10 am Riccardo wrote:
-- Original Message ---
From: Avi Kivity a...@redhat.com
To: Riccardo andrighetto.ricca...@gmail.com
Cc: kvm@vger.kernel.org
Sent: Fri, 21 May 2010 18:21:20 +0300
Subject: Re: Gentoo guest with smp: emerge freeze while
-- Original Message ---
From: Brian Jackson i...@theiggy.com
To: Riccardo andrighetto.ricca...@gmail.com
Cc: kvm@vger.kernel.org
Sent: Fri, 21 May 2010 11:35:36 -0500
Subject: Re: Gentoo guest with smp: emerge freeze while recompile world
On Friday, May 21, 2010
Anthony Liguori wrote:
On 05/21/2010 08:46 AM, Jan Kiszka wrote:
Anthony Liguori wrote:
On 05/21/2010 04:42 AM, Stefan Hajnoczi wrote:
Trace events should be defined in trace.h. Events are written to
/tmp/trace.log and can be formatted using trace.py. Remember to add
events to
Am 20.05.2010 07:36, schrieb MORITA Kazutaka:
This patch enables protocol drivers to use their create options which
are not supported by the format. For example, protcol drivers can use
a backing_file option with raw format.
Signed-off-by: MORITA Kazutaka morita.kazut...@lab.ntt.co.jp
---
Hello Jeff,
macvlan doesn't work on PF when SRIOV is enabled. Creating macvlan has
been successful, but ping (icmp request) goes to VF interface not
PF/macvlan even arp entry is correct. I patched ixgbe driver, and
macvlan/PF has worked with the patch. But I am not sure whether it is
right since
On Fri, May 21, 2010 at 5:52 PM, Jan Kiszka jan.kis...@siemens.com wrote:
I would just like to avoid that too much efforts are spent on
re-inventing smart trace buffers, trace daemons, or trace visualization
tools. Then better pick up some semi-perfect approach (e.g. [1], it
unfortunately
On 05/21/2010 11:52 AM, Jan Kiszka wrote:
Anthony Liguori wrote:
On 05/21/2010 08:46 AM, Jan Kiszka wrote:
Anthony Liguori wrote:
On 05/21/2010 04:42 AM, Stefan Hajnoczi wrote:
Trace events should be defined in trace.h. Events are written to
/tmp/trace.log and
On Fri, May 21, 2010 at 09:49:56PM +0100, Stefan Hajnoczi wrote:
http://sourceware.org/systemtap/wiki/AddingUserSpaceProbingToApps
Requires kernel support - not sure if enough of utrace is in mainline
for this to work out-of-the-box across distros.
Nothing of utrace is in mainline, nevermind
Stefan Hajnoczi wrote:
On Fri, May 21, 2010 at 5:52 PM, Jan Kiszka jan.kis...@siemens.com wrote:
I would just like to avoid that too much efforts are spent on
re-inventing smart trace buffers, trace daemons, or trace visualization
tools. Then better pick up some semi-perfect approach (e.g.
Anthony Liguori wrote:
I'm not opposed to using a framework, but I'd rather have an equivalent
to kvm_stat tomorrow than wait 3 years for LTTng to not get merged.
So let's have a dirt-simple tracing mechanism and focus on adding useful
trace points. Then when we have a framework we can use,
On 05/21/2010 04:41 PM, Jan Kiszka wrote:
Anthony Liguori wrote:
I'm not opposed to using a framework, but I'd rather have an equivalent
to kvm_stat tomorrow than wait 3 years for LTTng to not get merged.
So let's have a dirt-simple tracing mechanism and focus on adding useful
trace
On 15.05.2010 10:26, Alexander Graf wrote:
On S390, I'm also still sceptical if the implementation we have really works. A
device injects an S390_INTERRUPT with its address and on the next vcpu_run, an
according interrupt is issued. But what happens if two devices trigger an
S390_INTERRUPT
59 matches
Mail list logo
