On 08/16/2011 08:56 PM, Umesh Deshpande wrote:
+qemu_mutex_lock_ramlist();
Taken locks: iothread, ramlist
+qemu_mutex_unlock_iothread();
Taken locks: ramlist
+s->wait_for_unfreeze(s);
+qemu_mutex_lock_iothread();
Taken locks: ramlist, ioth
On 08/16/2011 08:56 PM, Umesh Deshpande wrote:
diff --git a/qemu-thread-posix.c b/qemu-thread-posix.c
index 2bd02ef..0d18b35 100644
--- a/qemu-thread-posix.c
+++ b/qemu-thread-posix.c
@@ -115,6 +115,16 @@ void qemu_cond_wait(QemuCond *cond, QemuMutex *mutex)
error_exit(err, __func__);
Hi guys,
After objdump the driver, I found that the access to the pci-memmap
register was optimized by GCC, and no code was generated.
And the EPT in 2.6.39 is fine.
Thanks,
Pierce
On Fri, Aug 12, 2011 at 4:33 PM, liu pf wrote:
> Hi guys,
>
> When I develop a PCI device driver for qemu-kvm, I
Replace the wrong rng virtio id with the correct balloon id.
Signed-off-by: Liming Wang
---
tools/kvm/virtio/balloon.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/tools/kvm/virtio/balloon.c b/tools/kvm/virtio/balloon.c
index c5853a5..aba52d6 100644
--- a/tools/kvm/v
Becasue virtio random generator is a single device, change its option
type to boolean.
Signed-off-by: Liming Wang
---
tools/kvm/builtin-run.c |7 +++
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/tools/kvm/builtin-run.c b/tools/kvm/builtin-run.c
index 2816774..646ba21 10
On 8/17/11 12:44 PM, Liming Wang wrote:
Becasue virtio random generator is a single device, change its option
type to boolean.
Signed-off-by: Liming Wang
I suppose the idea here was to support multiple rng devices. Sasha?
---
tools/kvm/builtin-run.c |7 +++
1 files changed, 3 inse
On Wed, Aug 17, 2011 at 2:44 PM, Pekka Enberg wrote:
> On 8/17/11 12:44 PM, Liming Wang wrote:
>>
>> Becasue virtio random generator is a single device, change its option
>> type to boolean.
>>
>> Signed-off-by: Liming Wang
>
> I suppose the idea here was to support multiple rng devices. Sasha?
I
On Fri, 12 Aug 2011 09:55:51 +0800, Jason Wang wrote:
> From: Krishna Kumar
>
> Implement mq virtio-net driver.
>
> Though struct virtio_net_config changes, it works with the old qemu
> since the last element is not accessed unless qemu sets
> VIRTIO_NET_F_MULTIQUEUE.
>
...
> +
> +#if 1
<...>
This patch contain two tests.
1) Try kill guest when guest netwok is under loading.
2) Try kill guest after multiple adding and removing network drivers.
Signed-off-by: Jiří Župka
---
client/tests/kvm/tests_base.cfg.sample| 23 +
client/virt/tests/netstress_kill_guest.py | 146 +++
On Wed, Aug 17, 2011 at 03:02:55PM +0300, Sasha Levin wrote:
>On Wed, Aug 17, 2011 at 2:44 PM, Pekka Enberg wrote:
>> On 8/17/11 12:44 PM, Liming Wang wrote:
>>>
>>> Becasue virtio random generator is a single device, change its option
>>> type to boolean.
>>>
>>> Signed-off-by: Liming Wang
>>
>>
On Wed, Aug 17, 2011 at 6:14 PM, walimis wrote:
> On Wed, Aug 17, 2011 at 03:02:55PM +0300, Sasha Levin wrote:
>>On Wed, Aug 17, 2011 at 2:44 PM, Pekka Enberg wrote:
>>> On 8/17/11 12:44 PM, Liming Wang wrote:
Becasue virtio random generator is a single device, change its option
ty
Hello, Gleb,
I was looking at KVM's call to rcu_virt_note_context_switch()
in kvm_guest_enter(), and noting the comment talking about treating
guest mode like user-mode execution is. One difference between RCU's
treatment of KVM guest execution and user-mode execution is that RCU
notes a context
On Wed, Aug 17, 2011 at 01:43:27PM -0700, Paul E. McKenney wrote:
> Hello, Gleb,
>
> I was looking at KVM's call to rcu_virt_note_context_switch()
> in kvm_guest_enter(), and noting the comment talking about treating
> guest mode like user-mode execution is. One difference between RCU's
> treatme
On Thu, Aug 18, 2011 at 12:50:15AM +0300, Gleb Natapov wrote:
> On Wed, Aug 17, 2011 at 01:43:27PM -0700, Paul E. McKenney wrote:
> > Hello, Gleb,
> >
> > I was looking at KVM's call to rcu_virt_note_context_switch()
> > in kvm_guest_enter(), and noting the comment talking about treating
> > guest
On 08/16/2011 12:47 PM, Sasha Levin wrote:
This patch adds support for an optional stats vq that works similary to the
stats vq provided by virtio-balloon.
The purpose of this change is to allow collection of statistics about working
virtio-blk devices to easily analyze performance without havin
On Wed, Aug 17, 2011 at 03:05:20PM -0700, Paul E. McKenney wrote:
> On Thu, Aug 18, 2011 at 12:50:15AM +0300, Gleb Natapov wrote:
> > On Wed, Aug 17, 2011 at 01:43:27PM -0700, Paul E. McKenney wrote:
> > > Hello, Gleb,
> > >
> > > I was looking at KVM's call to rcu_virt_note_context_switch()
> > >
On Thu, Aug 18, 2011 at 02:55:29AM +0300, Gleb Natapov wrote:
> On Wed, Aug 17, 2011 at 03:05:20PM -0700, Paul E. McKenney wrote:
> > On Thu, Aug 18, 2011 at 12:50:15AM +0300, Gleb Natapov wrote:
> > > On Wed, Aug 17, 2011 at 01:43:27PM -0700, Paul E. McKenney wrote:
> > > > Hello, Gleb,
> > > >
>
On 08/17/2011 05:25 PM, Paul E. McKenney wrote:
> >
> Wouldn't scheduling-clock interrupt kick vcpu out of a guest mode much
> earlier then 30 seconds?
The scheduling-clock interrupt would happen, but I do not know whether
or not it would kick the vcpu out of guest mode in such a way that
wou
On Wed, Aug 17, 2011 at 05:25:13PM -0700, Paul E. McKenney wrote:
> On Thu, Aug 18, 2011 at 02:55:29AM +0300, Gleb Natapov wrote:
> > On Wed, Aug 17, 2011 at 03:05:20PM -0700, Paul E. McKenney wrote:
> > > On Thu, Aug 18, 2011 at 12:50:15AM +0300, Gleb Natapov wrote:
> > > > On Wed, Aug 17, 2011 at
On Wed, Aug 17, 2011 at 05:28:46PM -0700, Avi Kivity wrote:
> On 08/17/2011 05:25 PM, Paul E. McKenney wrote:
> >> >
> >> Wouldn't scheduling-clock interrupt kick vcpu out of a guest mode much
> >> earlier then 30 seconds?
> >
> >The scheduling-clock interrupt would happen, but I do not know whe
On 08/17/2011 05:44 PM, Paul E. McKenney wrote:
>
> The result can only be one of
>
>reenter guest (and rcu_virt_note_context_switch)
>schedule()
>exit to userspace
Very good, thank you both for bearing with me on this!
Hey, it's our pleasure. Pester us as often as you'll like a
When kvm emulates repeation io read instruction, it can exit to user-space with
'count' > 1, we need to emulate io access for many times
Signed-off-by: Xiao Guangrong
---
tools/kvm/ioport.c | 17 +++--
1 files changed, 11 insertions(+), 6 deletions(-)
diff --git a/tools/kvm/ioport
'count' parameter in io emulation callbacks is useless, just remove it
Signed-off-by: Xiao Guangrong
---
tools/kvm/hw/i8042.c |4 ++--
tools/kvm/hw/rtc.c |6 +++---
tools/kvm/hw/serial.c |6 +++---
tools/kvm/hw/vesa.c|4 ++--
tools/kvm/i
On Wed, 2011-08-17 at 16:00 -0700, Avi Kivity wrote:
> On 08/16/2011 12:47 PM, Sasha Levin wrote:
> > This patch adds support for an optional stats vq that works similary to the
> > stats vq provided by virtio-balloon.
> >
> > The purpose of this change is to allow collection of statistics about
>
Hi,
On Thu, Aug 18, 2011 at 6:06 AM, Xiao Guangrong
wrote:
> When kvm emulates repeation io read instruction, it can exit to user-space
> with
> 'count' > 1, we need to emulate io access for many times
>
> Signed-off-by: Xiao Guangrong
The KVM tool is not actually maintained by Avi and Marcelo
25 matches
Mail list logo
