On 05/25/2010 09:28 AM, Sheng Yang wrote:
@@ -3354,6 +3356,29 @@ static int handle_wbinvd(struct kvm_vcpu *vcpu)
return 1;
}
+static int handle_xsetbv(struct kvm_vcpu *vcpu)
+{
+ u64 new_bv = kvm_read_edx_eax(vcpu);
+
+ if (kvm_register_read(vcpu, VCPU_REGS_RCX) != 0)
On Tue, May 25, 2010 at 11:10:36AM +0530, Krishna Kumar wrote:
> From: Krishna Kumar
>
> Missed a boundary value check in vhost_set_vring. The host panics if
> idx == nvqs is used in ioctl commands in vhost_virtqueue_init.
>
> Signed-off-by: Krishna Kumar
Thanks, applied.
> ---
> drivers/vho
On Mon, May 24, 2010 at 11:20 PM, Anthony Liguori
wrote:
>> +# check if trace backend exists
>> +
>> +sh tracetool "--$trace_backend" --check-backend> /dev/null 2> /dev/null
>>
>
> This will fail if objdir != srcdir. You have to qualify tracetool with the
> path to srcdir.
Thanks Anthony, fixe
On 05/24/2010 11:07 PM, Neo Jia wrote:
hi,
I am using KVM/Qemu to debug my Windows guest according to KVM wiki
page (http://www.linux-kvm.org/page/WindowsGuestDrivers/GuestDebugging).
It works for me and also I can only use one Windows guest and bind its
serial port to a TCP port and run "Virtua
On Mon, May 24, 2010 at 08:10:16PM +, Blue Swirl wrote:
> On Mon, May 24, 2010 at 3:40 PM, Joerg Roedel wrote:
> >> +
> >> +#define MMIO_SIZE 0x2028
> >
> > This size should be a power-of-two value. In this case probably 0x4000.
>
> Not really, the devices can reserve regions of
Introduce ft_tranx_ready() which kicks the FT transaction cycle. When
ft_mode is on, migrate_fd_put_ready() would open ft_transaction file
and turn on event_tap. To end or cancel ft_transaction, ft_mode and
event_tap is turned off.
Signed-off-by: Yoshiaki Tamura
---
migration.c | 78
The option looks like, -incoming ::,ft_mode
Signed-off-by: Yoshiaki Tamura
---
migration.c | 14 +-
1 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/migration.c b/migration.c
index 3334650..a4850f9 100644
--- a/migration.c
+++ b/migration.c
@@ -42,7 +42,19 @@ static
Record mmio write event to replay it upon failover.
Signed-off-by: Yoshiaki Tamura
---
exec.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/exec.c b/exec.c
index d5c2a05..e9ed477 100644
--- a/exec.c
+++ b/exec.c
@@ -44,6 +44,7 @@
#include "hw/hw.h"
#include "osdep
Skip assert(!cpu_single_env) in resume_all_threads() when
event_tap_state weren't EVENT_TAP_OFF.
Signed-off-by: Yoshiaki Tamura
---
qemu-kvm.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/qemu-kvm.c b/qemu-kvm.c
index 1414f49..e28bf59 100644
--- a/qemu-kvm.c
+++ b/
Modifies ram_save_block() and ram_save_remaining() to use
cpu_physical_memory_get_dirty_range() to check multiple dirty and non-dirty
pages at once.
Signed-off-by: Yoshiaki Tamura
Signed-off-by: OHMURA Kei
---
vl.c | 52 +---
1 files changed, 33
Currently FdMigrationState doesn't support read(), and this patch
introduces it to get response from the other side.
Signed-off-by: Yoshiaki Tamura
---
migration-tcp.c | 14 ++
migration.c | 12
migration.h |3 +++
3 files changed, 29 insertions(+), 0 del
Replaces byte-based phys_ram_dirty bitmap with four (MASTER, VGA,
CODE, MIGRATION) bit-based phys_ram_dirty bitmap. On allocation, it
sets all bits in the bitmap. It uses ffs() to convert DIRTY_FLAG to
DIRTY_IDX.
Modifies wrapper functions for byte-based phys_ram_dirty bitmap to
bit-based phys_r
Hi,
This patch series is a revised version of Kemari for KVM, which applied comments
for the previous post. The current code is based on qemu-kvm.git
2b644fd0e737407133c88054ba498e772ce01f27.
On the contrary to the previous version, this series doesn't require any
modifications to KVM. The I/O
Currently buf size is fixed at 32KB. It would be useful if it could
be flexible.
Signed-off-by: Yoshiaki Tamura
---
hw/hw.h |2 ++
savevm.c | 21 -
2 files changed, 22 insertions(+), 1 deletions(-)
diff --git a/hw/hw.h b/hw/hw.h
index 05131a0..fc9ed29 100644
--- a/hw
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: Yoshiaki Tamura
Signed-off-by: OHMURA Kei
---
Makefile.objs
Introduce qemu_savevm_state_all() to send the memory and device info
together, while avoiding cancelling memory state tracking.
Signed-off-by: Yoshiaki Tamura
---
savevm.c | 60
sysemu.h |1 +
2 files changed, 61 insertions(+), 0
Hi,
This patch series is a revised version of Kemari for KVM, which applied comments
for the previous post. The current code is based on qemu-kvm.git
2b644fd0e737407133c88054ba498e772ce01f27.
On the contrary to the previous version, this series doesn't require any
modifications to KVM. The I/O
event-tap controls when to start ft transaction, and inserts callbacks
to the net/block.
Signed-off-by: Yoshiaki Tamura
---
Makefile.target |1 +
event-tap.c | 184 +++
event-tap.h | 32 ++
3 files changed, 217 insertions
When -k option is set to migrate command, it will turn on ft_mode to
start FT migration mode (Kemari).
Signed-off-by: Yoshiaki Tamura
---
migration.c |3 +++
qemu-monitor.hx |7 ---
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/migration.c b/migration.c
index 5b9
Modifies kvm_get_dirty_pages_log_range to use
cpu_physical_memory_set_dirty_range() to update the row of the
bit-based phys_ram_dirty bitmap at once.
Signed-off-by: Yoshiaki Tamura
Signed-off-by: OHMURA Kei
---
qemu-kvm.c | 19 +++
1 files changed, 7 insertions(+), 12 deletion
To utilize ft_transaction function, savevm needs interfaces to be
exported.
Signed-off-by: Yoshiaki Tamura
---
hw/hw.h |5 +
savevm.c | 41 +
2 files changed, 46 insertions(+), 0 deletions(-)
diff --git a/hw/hw.h b/hw/hw.h
index fc9ed29..5a48a9
When ft_mode is set in the header, tcp_accept_incoming_migration()
receives ft_transaction iteratively. We also need a hack no to close
fd before moving to ft_transaction mode, so that we can reuse the fd
for it.
Signed-off-by: Yoshiaki Tamura
---
migration-tcp.c | 36
Signed-off-by: Yoshiaki Tamura
---
vl.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/vl.c b/vl.c
index 70a8aed..56d12c7 100644
--- a/vl.c
+++ b/vl.c
@@ -169,6 +169,8 @@ int main(int argc, char **argv)
#include "qemu-queue.h"
+#include "event-tap.h"
+
//#define
Record ioport event to replay it upon failover.
Signed-off-by: Yoshiaki Tamura
---
ioport.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/ioport.c b/ioport.c
index 53dd87a..ad7a017 100644
--- a/ioport.c
+++ b/ioport.c
@@ -26,6 +26,7 @@
*/
#include "ioport.h"
+#in
Signed-off-by: Yoshiaki Tamura
---
osdep.c | 13 +
qemu-char.c | 25 -
qemu_socket.h |4
3 files changed, 41 insertions(+), 1 deletions(-)
diff --git a/osdep.c b/osdep.c
index 3bab79a..63444e7 100644
--- a/osdep.c
+++ b/osdep.c
@@ -201,6 +
Call event_tap_replay() at vm_start() to replay the last ioport/mmio
event upon failover.
Signed-off-by: Yoshiaki Tamura
---
vl.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/vl.c b/vl.c
index 56d12c7..762440d 100644
--- a/vl.c
+++ b/vl.c
@@ -3094,6 +3094,7 @@ void vm
Introduce skip_header parameter to qemu_loadvm_state() so that it can
be called iteratively without reading the header.
Signed-off-by: Yoshiaki Tamura
---
migration-exec.c |2 +-
migration-fd.c |2 +-
migration-tcp.c |2 +-
migration-unix.c |2 +-
savevm.c | 24 +
Introduce event-tap callbacks to functions which actually fire outputs
at net/block layer. By synchronizing VMs before outputs are fired, we
can failover to the receiver upon failure.
Signed-off-by: Yoshiaki Tamura
---
block.c | 22 ++
block.h |4
net/queu
It checks the first row and puts dirty addr in the array. If the
first row is empty, it skips to the first non-dirty row or the end
addr, and put the length in the first entry of the array.
Signed-off-by: Yoshiaki Tamura
Signed-off-by: OHMURA Kei
---
cpu-all.h |4 +++
exec.c| 67
Modify inuse type to uint16_t, let save/load to handle, and revert
last_avail_idx with inuse if there are outstanding emulation.
Signed-off-by: Yoshiaki Tamura
---
hw/virtio.c |8 +++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/hw/virtio.c b/hw/virtio.c
index 7c020a3.
On 05/24/2010 12:15 AM, Riccardo wrote:
Please try with kvmclock disabled.
I have recompile gentoo-sources-2.6.34 without kvm-clock:
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
tsc
# dmesg | grep clock
[0.00] hpet clockevent registered
[0.661050] Sw
On 05/25/2010 01:07 AM, Anthony Liguori wrote:
Interesting approach as it lets us defer the tracing backend decision.
Also, it's compatible with the multiplatform nature of qemu.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "u
On 05/24/2010 10:38 PM, Anthony Liguori wrote:
- Building a plugin API seems a bit simpler to me, although I'm to
sure if I'd get the
idea correctly:
The block layer has already some kind of api (.bdrv_file_open,
.bdrv_read). We
could simply compile the block-drivers as shared objects
On 05/24/2010 10:16 PM, Anthony Liguori wrote:
On 05/24/2010 06:56 AM, Avi Kivity wrote:
On 05/24/2010 02:42 PM, MORITA Kazutaka wrote:
The server would be local and talk over a unix domain socket, perhaps
anonymous.
nbd has other issues though, such as requiring a copy and no
support for
On 05/24/2010 10:19 PM, Anthony Liguori wrote:
On 05/24/2010 06:03 AM, Avi Kivity wrote:
On 05/24/2010 11:27 AM, Stefan Hajnoczi wrote:
On Sun, May 23, 2010 at 1:01 PM, Avi Kivity wrote:
On 05/21/2010 12:29 AM, Anthony Liguori wrote:
I'd be more interested in enabling people to build these ty
On 05/15/2010 11:12 AM, Asias He wrote:
fix test/x86/msr.c fail to build on i386
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 majord...@vger.kernel.org
More ma
On 05/24/2010 10:41 AM, Xiao Guangrong wrote:
Allow more page become asynchronous at getting sp time, if need create new
shadow page for gfn but it not allow unsync(level> 1), we should unsync all
gfn's unsync page
Both applied, thanks.
--
error compiling committee.c: too many arguments t
On Mon, 2010-05-24 at 10:54 -0700, Rose, Gregory V wrote:
> We look forward to it and will be happy to provide feedback.
I have submitted the patch to make macvlan on PF works when SRIOV is
enabled.
> One thing you can do is allocate VFs and then load the VF driver in
> your host domain and then a
On 05/13/2010 11:15 PM, Mohammed Gamal wrote:
On Thu, May 13, 2010 at 9:24 AM, Avi Kivity wrote:
On 05/11/2010 07:52 PM, Mohammed Gamal wrote:
- Add 's' and 'g' field checks on segment registers
- Correct SS checks for request and descriptor privilege levels
Signed-off-by: Mohammed
On 05/19/2010 11:20 AM, Christoph Hellwig wrote:
It's time we get a proper bugzilla.qemu.org for both qemu and qemu-kvm
that can be used sanely. If you ask nicely you might even get a virtual
instance of bugzilla.kernel.org which works quite nicely.
That would be my preference too but the
Copying netdev, bridge mailing lists.
On 05/24/2010 11:23 AM, Hao, Xudong wrote:
Hi all
I build latest kvm 37dec075a7854f0f550540bf3b9bbeef37c11e2a, based on kernel
2.6.34, after kvm and kvm_intel module loaded, then /etc/init.d/kvm start, a
few minutes later, the system will panic.
kernel: 2
After the RFC discussion, updated patches which I propose for review and merge:
The following patches against qemu.git allow static trace events to be declared
in QEMU. Trace events use a lightweight syntax and are independent of the
backend tracing system (e.g. LTTng UST).
Supported backends ar
Sometimes it is useful to disable a trace event. Removing the event
from trace-events is not enough since source code will call the
trace_*() function for the event.
This patch makes it easy to build without specific trace events by
marking them disabled in trace-events:
disable multiwrite_cb(vo
This patch introduces the trace-events file where trace events can be
declared like so:
qemu_malloc(size_t size) "size %zu"
qemu_free(void *ptr) "ptr %p"
These trace event declarations are processed by a new tool called
tracetool to generate code for the trace events. Trace event
declarations ar
This patch adds LTTng Userspace Tracer (UST) backend support. The UST
system requires no kernel support but libust and liburcu must be
installed.
$ ./configure --trace-backend ust
$ make
Start the UST daemon:
$ ustd &
List available tracepoints and enable some:
$ ustctl --list-markers $(pgrep q
This patch adds trace events for virtqueue operations including
adding/removing buffers, notifying the guest, and receiving a notify
from the guest.
Signed-off-by: Stefan Hajnoczi
---
v2:
* This patch is new in v2
hw/virtio.c |8
trace-events |8
2 files changed, 16
This patch adds trace events that make it possible to observe
virtio-blk.
Signed-off-by: Stefan Hajnoczi
---
block.c|7 +++
hw/virtio-blk.c|7 +++
posix-aio-compat.c |2 ++
trace-events | 14 ++
4 files changed, 30 insertions(+), 0 deletion
It is often useful to instrument memory management functions in order to
find leaks or performance problems. This patch adds trace events for
the memory allocation primitives.
Signed-off-by: Stefan Hajnoczi
---
v2:
* Record pointer result from allocation functions
osdep.c | 24 +++
This patch adds a simple tracer which produces binary trace files and is
built into QEMU. The main purpose of this patch is to show how new
tracing backends can be added to tracetool.
To try out the simple backend:
./configure --trace-backend=simple
make
After running QEMU you can pretty-print
On Tue, May 25, 2010 at 12:37 PM, Avi Kivity wrote:
> On 05/13/2010 11:15 PM, Mohammed Gamal wrote:
>>
>> On Thu, May 13, 2010 at 9:24 AM, Avi Kivity wrote:
>>
>>>
>>> On 05/11/2010 07:52 PM, Mohammed Gamal wrote:
>>>
- Add 's' and 'g' field checks on segment registers
- Correct SS
Am 23.05.2010 14:01, schrieb Avi Kivity:
> On 05/21/2010 12:29 AM, Anthony Liguori wrote:
>>
>> I'd be more interested in enabling people to build these types of
>> storage systems without touching qemu.
>>
>> Both sheepdog and ceph ultimately transmit I/O over a socket to a
>> central daemon, ri
Michael Tokarev wrote:
23.05.2010 13:55, Peter Lieven wrote:
Hi,
after live migrating ubuntu 9.10 server (2.6.31-14-server) and suse
linux 10.1 (2.6.16.13-4-smp)
it happens sometimes that the guest runs into irq problems. i mention
these 2 guest oss
since i have seen the error there. there ar
On 05/25/2010 01:36 PM, Mohammed Gamal wrote:
Any reference to back this up? I think rpl is valid regardless of
ss.unusable (i.e. loading selector 0003 results in an unusable segment with
rpl=3), but I don't see how dpl can be valid in an unusable segment.
Intel 64 and IA-32 Architectu
On Tue, May 25, 2010 at 10:39:22AM +0200, Joerg Roedel wrote:
> On Mon, May 24, 2010 at 08:10:16PM +, Blue Swirl wrote:
> > On Mon, May 24, 2010 at 3:40 PM, Joerg Roedel wrote:
> > >> +
> > >> +#define MMIO_SIZE ? ? ? ? ? ? ? 0x2028
> > >
> > > This size should be a power-of-two value. In this
On 05/25/2010 02:02 PM, Kevin Wolf wrote:
So could we not standardize a protocol for this that both sheepdog and
ceph could implement?
The protocol already exists, nbd. It doesn't support snapshotting etc.
but we could extend it.
But IMO what's needed is a plugin API for the block
On 05/24/2010 01:01 AM, Mohammed Gamal wrote:
The vmexit handler returns KVM_EXIT_UNKNOWN since there is no handler
for vmentry failures. This intercepts vmentry failures and returns
KVM_FAIL_ENTRY to userspace instead.
Signed-off-by: Mohammed Gamal
---
arch/x86/kvm/vmx.c |7 +++
1 fi
On 05/24/2010 01:01 AM, Mohammed Gamal wrote:
For the sake of completeness, this patch adds a symbolic
constant for VMX exit reason 0x21 (invalid guest state).
Applied, thanks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "
On Tue, May 25, 2010 at 2:45 PM, Avi Kivity wrote:
> On 05/24/2010 01:01 AM, Mohammed Gamal wrote:
>>
>> The vmexit handler returns KVM_EXIT_UNKNOWN since there is no handler
>> for vmentry failures. This intercepts vmentry failures and returns
>> KVM_FAIL_ENTRY to userspace instead.
>>
>> Signed-
On Tue, May 25, 2010 at 02:25:53PM +0300, Avi Kivity wrote:
> Currently if someone wants to add a new block format, they have to
> upstream it and wait for a new qemu to be released. With a plugin API,
> they can add a new block format to an existing, supported qemu.
So? Unless we want a sta
On 05/25/2010 01:24 PM, Stefan Hajnoczi wrote:
This patch adds trace events for virtqueue operations including
adding/removing buffers, notifying the guest, and receiving a notify
from the guest.
diff --git a/trace-events b/trace-events
index 48415f8..a533414 100644
--- a/trace-events
+++ b/trac
On 05/25/2010 03:01 PM, Mohammed Gamal wrote:
How does the user distinguish between KVM_EXIT_FAIL_ENTRY due to an exit
reason with bit 31 set and vmlauch/vmresume failure (vmx->fail set)? We
need separate exit codes (with documentation in api.txt).
In both cases the vm fails entry, and I
On 05/25/2010 03:03 PM, Christoph Hellwig wrote:
On Tue, May 25, 2010 at 02:25:53PM +0300, Avi Kivity wrote:
Currently if someone wants to add a new block format, they have to
upstream it and wait for a new qemu to be released. With a plugin API,
they can add a new block format to an existi
On Tue, May 25, 2010 at 3:10 PM, Avi Kivity wrote:
> On 05/25/2010 03:01 PM, Mohammed Gamal wrote:
>>>
>>> How does the user distinguish between KVM_EXIT_FAIL_ENTRY due to an exit
>>> reason with bit 31 set and vmlauch/vmresume failure (vmx->fail set)? We
>>> need separate exit codes (with docume
On 05/25/2010 04:14 AM, Avi Kivity wrote:
On 05/24/2010 10:38 PM, Anthony Liguori wrote:
- Building a plugin API seems a bit simpler to me, although I'm to
sure if I'd get the
idea correctly:
The block layer has already some kind of api (.bdrv_file_open,
.bdrv_read). We
could simply
On 05/25/2010 06:25 AM, Avi Kivity wrote:
On 05/25/2010 02:02 PM, Kevin Wolf wrote:
So could we not standardize a protocol for this that both sheepdog and
ceph could implement?
The protocol already exists, nbd. It doesn't support snapshotting etc.
but we could extend it.
But IMO what's ne
On 05/25/2010 04:17 PM, Anthony Liguori wrote:
On 05/25/2010 04:14 AM, Avi Kivity wrote:
On 05/24/2010 10:38 PM, Anthony Liguori wrote:
- Building a plugin API seems a bit simpler to me, although I'm to
sure if I'd get the
idea correctly:
The block layer has already some kind of api (.b
At Mon, 24 May 2010 14:16:32 -0500,
Anthony Liguori wrote:
>
> On 05/24/2010 06:56 AM, Avi Kivity wrote:
> > On 05/24/2010 02:42 PM, MORITA Kazutaka wrote:
> >>
> >>> The server would be local and talk over a unix domain socket, perhaps
> >>> anonymous.
> >>>
> >>> nbd has other issues though, suc
On Tue, May 25, 2010 at 1:04 PM, Avi Kivity wrote:
> Those %ps are more or less useless. We need better ways of identifying
> them.
You're right, the vq pointer is useless in isolation. We don't know
which virtio device or which virtqueue number.
With the full context of a trace it would be po
On 05/25/2010 08:25 AM, Avi Kivity wrote:
On 05/25/2010 04:17 PM, Anthony Liguori wrote:
On 05/25/2010 04:14 AM, Avi Kivity wrote:
On 05/24/2010 10:38 PM, Anthony Liguori wrote:
- Building a plugin API seems a bit simpler to me, although I'm to
sure if I'd get the
idea correctly:
The b
On 05/25/2010 04:25 PM, Anthony Liguori wrote:
Currently if someone wants to add a new block format, they have to
upstream it and wait for a new qemu to be released. With a plugin
API, they can add a new block format to an existing, supported qemu.
Whether we have a plugin or protocol based
On 05/25/2010 04:29 PM, Anthony Liguori wrote:
The current situation is that those block format drivers only exist
in qemu.git or as patches. Surely that's even more unhappiness.
Confusion could be mitigated:
$ qemu -module my-fancy-block-format-driver.so
my-fancy-block-format-driver.so d
On 05/25/2010 04:35 PM, Anthony Liguori wrote:
On 05/25/2010 08:31 AM, Avi Kivity wrote:
A protocol based mechanism has the advantage of being more robust in
the face of poorly written block backends so if it's possible to
make it perform as well as a plugin, it's a preferable approach.
May b
On 05/25/2010 08:31 AM, Avi Kivity wrote:
A protocol based mechanism has the advantage of being more robust in
the face of poorly written block backends so if it's possible to make
it perform as well as a plugin, it's a preferable approach.
May be hard due to difficulty of exposing guest memor
Am 24.05.2010 08:34, schrieb MORITA Kazutaka:
> At Fri, 21 May 2010 18:57:36 +0200,
> Kevin Wolf wrote:
>>
>> Am 20.05.2010 07:36, schrieb MORITA Kazutaka:
>>> +
>>> +/*
>>> + * Append an option list (list) to an option list (dest).
>>> + *
>>> + * If dest is NULL, a new copy of list is created.
>>
On 05/25/2010 04:27 PM, Stefan Hajnoczi wrote:
On Tue, May 25, 2010 at 1:04 PM, Avi Kivity wrote:
Those %ps are more or less useless. We need better ways of identifying
them.
You're right, the vq pointer is useless in isolation. We don't know
which virtio device or which virtqueue
Am 25.05.2010 15:25, schrieb Anthony Liguori:
> On 05/25/2010 06:25 AM, Avi Kivity wrote:
>> On 05/25/2010 02:02 PM, Kevin Wolf wrote:
>>>
> So could we not standardize a protocol for this that both sheepdog and
> ceph could implement?
The protocol already exists, nbd. It doesn't
On 05/25/2010 08:36 AM, Avi Kivity wrote:
We'd need a kernel-level generic snapshot API for this eventually.
or (2) implement BUSE to complement FUSE and CUSE to enable proper
userspace block devices.
Likely slow due do lots of copying. Also needs a snapshot API.
The kernel could use spli
On 05/25/2010 08:38 AM, Avi Kivity wrote:
On 05/25/2010 04:35 PM, Anthony Liguori wrote:
On 05/25/2010 08:31 AM, Avi Kivity wrote:
A protocol based mechanism has the advantage of being more robust
in the face of poorly written block backends so if it's possible to
make it perform as well as a
On 05/25/2010 04:53 PM, Kevin Wolf wrote:
I'm still not convinced that we need either. I share Christoph's concern
that we would make our life harder for almost no gain. It's probably a
very small group of users (if it exists at all) that wants to add new
block drivers themselves, but at the sam
On 05/25/2010 04:54 PM, Anthony Liguori wrote:
On 05/25/2010 08:36 AM, Avi Kivity wrote:
We'd need a kernel-level generic snapshot API for this eventually.
or (2) implement BUSE to complement FUSE and CUSE to enable proper
userspace block devices.
Likely slow due do lots of copying. Also n
On Tue, May 25, 2010 at 2:52 PM, Avi Kivity wrote:
> Hm. Perhaps we can convert %{type} to %p for backends which don't support
> it, and to whatever format they do support for those that do.
True.
Stefan
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message
On 05/25/2010 04:55 PM, Anthony Liguori wrote:
On 05/25/2010 08:38 AM, Avi Kivity wrote:
On 05/25/2010 04:35 PM, Anthony Liguori wrote:
On 05/25/2010 08:31 AM, Avi Kivity wrote:
A protocol based mechanism has the advantage of being more robust
in the face of poorly written block backends so if
Am 25.05.2010 15:25, schrieb Avi Kivity:
> On 05/25/2010 04:17 PM, Anthony Liguori wrote:
>> On 05/25/2010 04:14 AM, Avi Kivity wrote:
>>> On 05/24/2010 10:38 PM, Anthony Liguori wrote:
> - Building a plugin API seems a bit simpler to me, although I'm to
> sure if I'd get the
>
Memory allocation may fail. Propagate such errors.
Signed-off-by: Jan Kiszka
---
arch/x86/include/asm/kvm_host.h |2 +-
arch/x86/kvm/svm.c |7 ++-
arch/x86/kvm/vmx.c |4 +++-
arch/x86/kvm/x86.c | 11 +--
4 files changed, 19 inserti
Signed-off-by: Jan Kiszka
---
arch/x86/kvm/svm.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 5f25e59..3c03c36 100644
--- a/arch/x86/kvm/svm.c
+++ b/arch/x86/kvm/svm.c
@@ -1491,8 +1491,6 @@ static void svm_handle_mce(struc
On 05/25/2010 08:57 AM, Avi Kivity wrote:
On 05/25/2010 04:54 PM, Anthony Liguori wrote:
On 05/25/2010 08:36 AM, Avi Kivity wrote:
We'd need a kernel-level generic snapshot API for this eventually.
or (2) implement BUSE to complement FUSE and CUSE to enable proper
userspace block devices.
On 05/25/2010 08:55 AM, Avi Kivity wrote:
On 05/25/2010 04:53 PM, Kevin Wolf wrote:
I'm still not convinced that we need either. I share Christoph's concern
that we would make our life harder for almost no gain. It's probably a
very small group of users (if it exists at all) that wants to add n
When guest notifier is assigned, we set mask notifier,
which will assign kvm irqfd.
When guest notifier is unassigned, mask notifier is unset,
which should unassign kvm irqfd.
The way to do this is to call mask notifier telling it to mask the vector.
This, unless vector is already masked which una
On 05/25/2010 09:01 AM, Avi Kivity wrote:
On 05/25/2010 04:55 PM, Anthony Liguori wrote:
On 05/25/2010 08:38 AM, Avi Kivity wrote:
On 05/25/2010 04:35 PM, Anthony Liguori wrote:
On 05/25/2010 08:31 AM, Avi Kivity wrote:
A protocol based mechanism has the advantage of being more robust
in the
Am 25.05.2010 15:55, schrieb Avi Kivity:
> On 05/25/2010 04:53 PM, Kevin Wolf wrote:
>>
>> I'm still not convinced that we need either. I share Christoph's concern
>> that we would make our life harder for almost no gain. It's probably a
>> very small group of users (if it exists at all) that wants
Ah right, thanks :)
On Tue, May 25, 2010 at 10:02:15AM -0400, Jan Kiszka wrote:
> Signed-off-by: Jan Kiszka
Acked-by: Joerg Roedel
> ---
> arch/x86/kvm/svm.c |2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> index 5f25e59
On (Tue) May 25 2010 [17:00:43], Michael S. Tsirkin wrote:
> When guest notifier is assigned, we set mask notifier,
> which will assign kvm irqfd.
> When guest notifier is unassigned, mask notifier is unset,
> which should unassign kvm irqfd.
>
> The way to do this is to call mask notifier telling
"Michael S. Tsirkin" wrote:
> When guest notifier is assigned, we set mask notifier,
> which will assign kvm irqfd.
> When guest notifier is unassigned, mask notifier is unset,
> which should unassign kvm irqfd.
>
> The way to do this is to call mask notifier telling it to mask the vector.
> This,
On Tue, May 25, 2010 at 04:37:36PM +0200, Juan Quintela wrote:
> "Michael S. Tsirkin" wrote:
> > When guest notifier is assigned, we set mask notifier,
> > which will assign kvm irqfd.
> > When guest notifier is unassigned, mask notifier is unset,
> > which should unassign kvm irqfd.
> >
> > The w
On 05/25/10 16:00, Michael S. Tsirkin wrote:
When guest notifier is assigned, we set mask notifier,
which will assign kvm irqfd.
When guest notifier is unassigned, mask notifier is unset,
which should unassign kvm irqfd.
The way to do this is to call mask notifier telling it to mask the vector.
On Tue, 2010-05-11 at 17:03 +0800, Jason Wang wrote:
> The guest console is useful for failure troubleshooting especially for
> the one who has calltrace. And as we plan to push the network related
> test in the next few weeks, we found the serial session in more
> reliable during the network testi
"Michael S. Tsirkin" wrote:
> On Tue, May 25, 2010 at 04:37:36PM +0200, Juan Quintela wrote:
>> we have:
>>
>> if (msix_is_masked())
>>return 0
>> r = msix_mask_notifier(., !msix_is_masked());
>>
>> i.e. at that point msix_is_masked() is false, or we really, really needs
>> locking.
>>
Generic Asynchronous task offloading
- keep vcpu thread from blocking
- generic approach is useful, comes down to specifics
- e.g. what is done in worker threads, how locking is handled
- offload blocking work to worker threads
- need to make device model reentrant
- can be simple w/ lock per
On 05/25/2010 05:05 PM, Anthony Liguori wrote:
On 05/25/2010 09:01 AM, Avi Kivity wrote:
On 05/25/2010 04:55 PM, Anthony Liguori wrote:
On 05/25/2010 08:38 AM, Avi Kivity wrote:
On 05/25/2010 04:35 PM, Anthony Liguori wrote:
On 05/25/2010 08:31 AM, Avi Kivity wrote:
A protocol based mechanism
On 05/25/2010 05:09 PM, Kevin Wolf wrote:
The first part of your argument may be true, but the second isn't. No
user can run upstream qemu.git. It's not tested or supported, and has
no backwards compatibility guarantees.
The second part was basically meant to say "developers don't coun
1 - 100 of 150 matches
Mail list logo
