start(void);
*/
void memory_global_dirty_log_stop(void);
+typedef void (*write_protect_all_fn)(bool write);
+void memory_register_write_protect_all(write_protect_all_fn func);
+
void mtree_info(fprintf_function mon_printf, void *f);
--
Best Regards,
Jay Zhou
-off-by: Jay Zhou
---
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/include/uapi/asm/kvm.h | 2 ++
arch/x86/kvm/x86.c | 7 ---
3 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
index 695605e..6dd21ff
-off-by: Jay Zhou
---
hw/i386/kvm/clock.c | 12 ++--
linux-headers/asm-x86/kvm.h | 2 ++
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/hw/i386/kvm/clock.c b/hw/i386/kvm/clock.c
index 13eca37..fcc4f62 100644
--- a/hw/i386/kvm/clock.c
+++ b/hw/i386/kvm/clock.c
Hi Radim,
On 2017/6/13 3:52, Radim Krčmář wrote:
2017-06-12 21:23+0800, Jay Zhou:
Guest using kvmclock will be hanged when migrating from unstable
tsc host to stable tsc host occasionally.
Sometimes, the tsc timestamp saved at the source side will be
backward when the guest stopped, and this
Hi Radim,
On 2017/6/13 4:03, Radim Krčmář wrote:
2017-06-12 21:30+0800, Jay Zhou:
Guest using kvmclock will be hanged when migrating from unstable
tsc host to stable tsc host occasionally.
Sometimes, the tsc timestamp saved at the source side will be
backward when the guest stopped, and this
dTLB-stores
(16.50%)
93,793 iTLB-load-misses #7.43% of all
iTLB cache hits (16.67%)
1,262,137 iTLB-loads
(33.33%)
10.000709900 seconds time elapsed
Regards,
Jay Zhou
Regards,
Wanpeng Li
These are the st
x440 [kvm]
[139574.369205] [] kvm_vcpu_ioctl+0x2b1/0x640 [kvm]
[139574.369209] [] ? do_futex+0x122/0x5b0
[139574.369212] [] do_vfs_ioctl+0x2e5/0x4c0
[139574.369223] [] ? kvm_on_user_return+0x75/0xb0 [kvm]
[139574.369225] [] SyS_ioctl+0xa1/0xc0
[139574.369229] [] system_call_fastpath+0x16/0x1b
Any suggestion will be appreciated, Thanks!
Regards,
Jay Zhou
Hi Xiao,
On 2017/5/19 16:32, Xiao Guangrong wrote:
I do not know why i was removed from the list.
I was CCed to you...
Your comments are very valuable to us, and thank for your quick response.
On 05/19/2017 04:09 PM, Jay Zhou wrote:
Hi Paolo and Wanpeng,
On 2017/5/17 16:38, Wanpeng Li
the active_mmu_pages list to
zap the unsync sptes.
I think it can be optimized:
(1) source vm will be destroyed if the migration is successfully done,
so the resources will be cleanuped automatically by the system
(2) delay the cleanup if the migration failed
Signed-off-by: Jay Zhou
Hi Dave,
On 2017/7/21 17:49, Dr. David Alan Gilbert wrote:
* Jay Zhou (jianjay.z...@huawei.com) wrote:
Qemu_savevm_state_cleanup() takes about 300ms in my ram migration tests
with a 8U24G vm(20G is really occupied), the main cost comes from
KVM_SET_USER_MEMORY_REGION ioctl when mem.memory_size
On 2017/7/24 23:35, Dr. David Alan Gilbert wrote:
* Jay Zhou (jianjay.z...@huawei.com) wrote:
Hi Dave,
On 2017/7/21 17:49, Dr. David Alan Gilbert wrote:
* Jay Zhou (jianjay.z...@huawei.com) wrote:
Qemu_savevm_state_cleanup() takes about 300ms in my ram migration tests
with a 8U24G vm(20G is
On 2017/7/25 0:33, Paolo Bonzini wrote:
On 24/07/2017 17:35, Dr. David Alan Gilbert wrote:
* Jay Zhou (jianjay.z...@huawei.com) wrote:
Hi Dave,
On 2017/7/21 17:49, Dr. David Alan Gilbert wrote:
* Jay Zhou (jianjay.z...@huawei.com) wrote:
Qemu_savevm_state_cleanup() takes about 300ms in my
active_mmu_pages list to
zap the unsync sptes.
It can be optimized by delaying memory_global_dirty_log_stop to the next
vm_start.
Changes v1->v2:
- create a VMChangeStateHandler in memory.c to reduce the coupling [Paolo]
Signed-off-by: Jay Zhou
---
memory.c | 27 ++-
Hi Paolo,
On 2017/7/27 22:15, Paolo Bonzini wrote:
On 27/07/2017 04:36, Jay Zhou wrote:
Qemu_savevm_state_cleanup takes about 300ms in my ram migration tests
with a 8U24G vm(20G is really occupied), the main cost comes from
KVM_SET_USER_MEMORY_REGION ioctl when mem.memory_size = 0 in
v1->v2:
- create a VMChangeStateHandler in memory.c to reduce the coupling [Paolo]
Signed-off-by: Jay Zhou
---
memory.c | 36 +++-
1 file changed, 35 insertions(+), 1 deletion(-)
diff --git a/memory.c b/memory.c
index a7bc70a..c0adc35 100644
--- a/memory.c
Hi Dave,
On 2017/7/25 18:34, Dr. David Alan Gilbert wrote:
After checking the codes of the newest libvirt, I think it is the same
in the qemuMigrationWaitForCompletion function, which is used to poll
qemu every 50ms.
Checking with Jiri Denemark (added to cc), newer libvirt should use
events wh
initialize
but without vhostforce flag. So the followed up device_add can fall
back to userspace virtio successfully.
Suggested-by: Michael S. Tsirkin
Suggested-by: Igor Mammedov
Suggested-by: Jason Wang
Signed-off-by: Jay Zhou
---
net/tap.c | 40
1 file
On 2018/2/2 1:06, Michael S. Tsirkin wrote:
Yes, I plan to merge it in the next pull.
Pls don't assume anything until it's merged upstream though,
some issues surface late.
Okay, I see. Thanks for reviewing!
Regards,
Jay
On Thu, Feb 01, 2018 at 11:29:15AM +, Zhoujian (jay) wrote:
Hi M
Hi Jason,
On 2018/2/2 11:11, Jason Wang wrote:
On 2018年01月26日 11:08, Jay Zhou wrote:
If netdev_add tap,id=net0,...,vhost=on failed in net_init_tap_one(),
the followed up device_add virtio-net-pci,netdev=net0 will fail
too, prints:
TUNSETOFFLOAD ioctl() failed: Bad file descriptor
Hi Jason,
On 2018/2/2 14:56, Jason Wang wrote:
On 2018年02月02日 11:53, Jay Zhou wrote:
Hi Jason,
On 2018/2/2 11:11, Jason Wang wrote:
On 2018年01月26日 11:08, Jay Zhou wrote:
If netdev_add tap,id=net0,...,vhost=on failed in net_init_tap_one(),
the followed up device_add virtio-net-pci,netdev
failed to open or
initialize but without vhostforce flag. So the followed up
device_add can fall back to userspace virtio successfully.
Suggested-by: Michael S. Tsirkin
Suggested-by: Igor Mammedov
Suggested-by: Jason Wang
Signed-off-by: Jay Zhou
---
net/tap.c | 44
Hi,
Does this document update make sense?
Regards,
Jay
On 2017/11/23 16:47, Jay Zhou wrote:
Since the commit 11808bb0c422134bf09119f4aa22c59b0ce84bf3 removed
the put_buffer callback and using an iovec based write handler instead,
the docs should be sync with the code too.
Signed-off-by: Jay
means it can not reduce the number of memslots, it must be failed
at last.
Signed-off-by: Jay Zhou
---
hw/virtio/vhost.c | 3 +++
include/hw/virtio/vhost.h | 2 ++
net/vhost-user.c | 5 +
3 files changed, 10 insertions(+)
diff --git a/hw/virtio/vhost.c b/hw/virtio/vhost.c
index e
memory slots can be used by vhost user, it is failed to hot plug
a new memory RAM because vhost_has_free_slot just returned false,
but we can hot plug it safely in fact.
Signed-off-by: Jay Zhou
Signed-off-by: Zhe Liu
---
hw/virtio/vhost-user.c| 31 +++
hw/
If the VM already has N(N>=8) available memory slots for vhost user,
the VM will be crashed in vhost_user_set_mem_table if we try to
hotplug the first vhost user NIC.
This patch checks if memslot number exceeded or not after updating
vhost_user_used_memslots.
Signed-off-by: Jay Zhou
---
Jay Zhou (2):
vhost: add used memslot number for vhost-user
vhost: double check memslot number
hw/virtio/vhost-user.c| 31 +
hw/virtio/vhost.c | 49 ++-
include/hw/virtio/vhost-backend.h | 4
3
Since the commit 11808bb0c422134bf09119f4aa22c59b0ce84bf3 removed
the put_buffer callback and using an iovec based write handler instead,
the docs should be sync with the code too.
Signed-off-by: Jay Zhou
---
docs/devel/migration.txt | 31 ++-
1 file changed, 18
From: Gonglei
Introduce two vhost-user meassges: VHOST_USER_CREATE_CRYPTO_SESSION
and VHOST_USER_CLOSE_CRYPTO_SESSION. At this point, the QEMU side
support crypto operation in cryptodev host-user backend.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
From: Gonglei
I posted the RFC verion a few months ago for DPDK
vhost-crypto implmention, and now it's time to send
the formal version. Because we need an user space scheme
for better performance.
The vhost user crypto server side patches had been
sent to DPDK community, pls see
[RFC PATCH 0/6]
From: Gonglei
Usage:
-chardev socket,id=charcrypto0,path=/path/to/your/socket
-object cryptodev-vhost-user,id=cryptodev0,chardev=charcrypto0
-device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends
works.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends/cryptodev-builtin.c | 1 +
backends/cryptodev-vhost-user.c | 16 +++
backends/cryptodev-vhost.c| 224 ++
hw/virtio/Makefile
From: Gonglei
Signed-off-by: Gonglei
---
backends/cryptodev-vhost-user.c | 4
include/sysemu/cryptodev-vhost-user.h | 3 +++
2 files changed, 7 insertions(+)
diff --git a/backends/cryptodev-vhost-user.c b/backends/cryptodev-vhost-user.c
index 061c0e5..c7a9848 100644
--- a/backends/c
works.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends/cryptodev-builtin.c | 1 +
backends/cryptodev-vhost-user.c | 16 +++
backends/cryptodev-vhost.c| 224 ++
hw/virtio/Makefile
From: Gonglei
Usage:
-chardev socket,id=charcrypto0,path=/path/to/your/socket
-object cryptodev-vhost-user,id=cryptodev0,chardev=charcrypto0
-device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends
From: Gonglei
Signed-off-by: Gonglei
---
backends/cryptodev-vhost-user.c | 4
include/sysemu/cryptodev-vhost-user.h | 3 +++
2 files changed, 7 insertions(+)
diff --git a/backends/cryptodev-vhost-user.c b/backends/cryptodev-vhost-user.c
index 061c0e5..c7a9848 100644
--- a/backends/c
From: Gonglei
Signed-off-by: Jay Zhou
---
backends/Makefile.objs | 4 +++-
backends/cryptodev-vhost.c | 57 +++---
configure | 15
vl.c | 2 ++
4 files changed, 74 insertions(+), 4 deletions
From: Gonglei
I posted the RFC verion a few months ago for DPDK
vhost-crypto implmention, and now it's time to send
the formal version. Because we need an user space scheme
for better performance.
The vhost user crypto server side patches had been
sent to DPDK community, pls see
[RFC PATCH 0/6]
From: Gonglei
Introduce two vhost-user meassges: VHOST_USER_CREATE_CRYPTO_SESSION
and VHOST_USER_CLOSE_CRYPTO_SESSION. At this point, the QEMU side
support crypto operation in cryptodev host-user backend.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
From: Gonglei
I posted the RFC verion a few months ago for DPDK
vhost-crypto implmention, and now it's time to send
the formal version. Because we need an user space scheme
for better performance.
The vhost user crypto server side patches had been
sent to DPDK community, pls see
[RFC PATCH 0/6]
From: Gonglei
Signed-off-by: Gonglei
---
backends/cryptodev-vhost-user.c | 4
include/sysemu/cryptodev-vhost-user.h | 3 +++
2 files changed, 7 insertions(+)
diff --git a/backends/cryptodev-vhost-user.c b/backends/cryptodev-vhost-user.c
index 061c0e5..c7a9848 100644
--- a/backends/c
From: Gonglei
Introduce two vhost-user meassges: VHOST_USER_CREATE_CRYPTO_SESSION
and VHOST_USER_CLOSE_CRYPTO_SESSION. At this point, the QEMU side
support crypto operation in cryptodev host-user backend.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
works.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends/cryptodev-builtin.c | 1 +
backends/cryptodev-vhost-user.c | 16 +++
backends/cryptodev-vhost.c| 258 ++
hw/virtio/Makefile
From: Gonglei
Usage:
-chardev socket,id=charcrypto0,path=/path/to/your/socket
-object cryptodev-vhost-user,id=cryptodev0,chardev=charcrypto0
-device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends
From: Gonglei
Usage:
-chardev socket,id=charcrypto0,path=/path/to/your/socket
-object cryptodev-vhost-user,id=cryptodev0,chardev=charcrypto0
-device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends
From: Gonglei
Signed-off-by: Gonglei
---
backends/cryptodev-vhost-user.c | 4
include/sysemu/cryptodev-vhost-user.h | 3 +++
2 files changed, 7 insertions(+)
diff --git a/backends/cryptodev-vhost-user.c b/backends/cryptodev-vhost-user.c
index 7bd0929..11b834b 100644
--- a/backends/c
From: Gonglei
I posted the RFC verion a few months ago for DPDK
vhost-crypto implmention, and now it's time to send
the formal version. Because we need an user space scheme
for better performance.
The vhost user crypto server side patches had been
sent to DPDK community, pls see
[RFC PATCH 0/6]
From: Gonglei
Introduce two vhost-user meassges: VHOST_USER_CREATE_CRYPTO_SESSION
and VHOST_USER_CLOSE_CRYPTO_SESSION. At this point, the QEMU side
support crypto operation in cryptodev host-user backend.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
works.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends/cryptodev-builtin.c | 1 +
backends/cryptodev-vhost-user.c | 16 +++
backends/cryptodev-vhost.c| 258 ++
hw/virtio/Makefile
v6 -> v7:
rebase on the master
Jay Zhou (2):
vhost: fix memslot limit check
vhost: used_memslots refactoring
hw/virtio/vhost-backend.c | 15 +++-
hw/virtio/vhost-user.c| 77 ++-
hw/virtio/vhost.c |
t will be failed to hotplug a new DIMM
device since vhost_has_free_slot() finds no free slot left. It
should be successful if only part of memory slots have file
descriptor, so setting used memslots for vhost-user and
vhost-kernel respectively.
Signed-off-by: Igor Mammedov
Signed-off-by: Jay Zhou
Since used_memslots will be updated to the actual value after
registering memory listener for the first time, move the
memslots limit checking to the right place.
Reviewed-by: Igor Mammedov
Signed-off-by: Jay Zhou
---
hw/virtio/vhost.c | 19 ---
1 file changed, 12 insertions
Since struct AddressSpaceOps isn't used anywhere else,
so just delete it.
Signed-off-by: Jay Zhou
---
memory.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/memory.c b/memory.c
index fc7f9b7..94b91f9 100644
--- a/memory.c
+++ b/memory.c
@@ -220,8 +220,6 @@ struct FlatRange {
This patch removes the dead code, which fixes Coverity (CID 1390600) issue.
Signed-off-by: Jay Zhou
---
backends/cryptodev-vhost-user.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/backends/cryptodev-vhost-user.c b/backends/cryptodev-vhost-user.c
index 862d4f2..67e65c6 100644
--- a
: invalid runstate transition: 'prelaunch' -> 'postmigrate'
Aborted
The run state transition is RUN_STATE_FINISH_MIGRATE to RUN_STATE_PRELAUNCH,
then the migration thread aborted when it tries to set RUN_STATE_POSTMIGRATE.
There is a race between the main loop thread and the migrat
From: Gonglei
I posted the RFC verion five months ago for DPDK
vhost-crypto implmention, and now it's time to send
the formal version. Because we need an user space scheme
for better performance.
The vhost user crypto server side patches had been
sent to DPDK community, pls see
[RFC PATCH 0/6]
works.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends/cryptodev-builtin.c | 1 +
backends/cryptodev-vhost-user.c | 16 +++
backends/cryptodev-vhost.c| 224 ++
hw/virtio/Makefile
From: Gonglei
Introduce two vhost-user meassges: VHOST_USER_CREATE_CRYPTO_SESSION
and VHOST_USER_CLOSE_CRYPTO_SESSION. At this point, the QEMU side
support crypto operation in cryptodev host-user backend.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
From: Gonglei
Signed-off-by: Gonglei
---
backends/cryptodev-vhost-user.c | 4
include/sysemu/cryptodev-vhost-user.h | 3 +++
2 files changed, 7 insertions(+)
diff --git a/backends/cryptodev-vhost-user.c b/backends/cryptodev-vhost-user.c
index 061c0e5..c7a9848 100644
--- a/backends/c
Signed-off-by: Jay Zhou
---
include/exec/memory.h | 27 +++
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a/include/exec/memory.h b/include/exec/memory.h
index a4cabdf..6e5684d 100644
--- a/include/exec/memory.h
+++ b/include/exec/memory.h
@@ -324,7 +324,7
v4 -> v5:
Making the followed up device_add to fall back to userspace
virtio when netdev_add fails if vhost force flag does not set.
Jay Zhou (4):
vhost: remove assertion to prevent crash
tap: do not close fd if only vhost failed to initialize
vhost: fix memslot limit check
vh
...@nongnu.org
Signed-off-by: Igor Mammedov
Signed-off-by: Jay Zhou
---
hw/virtio/vhost-user.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
index 093675e..8500562 100644
--- a/hw/virtio/vhost-user.c
+++ b/hw/virtio/vhost-user.c
t will be failed to hotplug a new DIMM
device since vhost_has_free_slot() finds no free slot left. It
should be successful if only part of memory slots have file
descriptor, so setting used memslots for vhost-user and
vhost-kernel respectively.
Signed-off-by: Igor Mammedov
Signed-off-by: Jay Zhou
Making the followed up device_add to fall back to userspace
virtio when netdev_add fails if vhost force flag does not set.
Suggested-by: Michael S. Tsirkin
Suggested-by: Igor Mammedov
Signed-off-by: Jay Zhou
---
net/tap.c | 25 ++---
1 file changed, 18 insertions(+), 7
Since used_memslots will be updated to the actual value after
registering memory listener for the first time, move the
memslots limit checking to the right place.
Signed-off-by: Jay Zhou
---
hw/virtio/vhost.c | 19 ---
1 file changed, 12 insertions(+), 7 deletions(-)
diff --git
Jay Zhou (3):
vhost: remove assertion to prevent crash
vhost: fix memslot limit check
vhost: used_memslots refactoring
hw/virtio/vhost-backend.c | 15 +++-
hw/virtio/vhost-user.c| 74 +++
hw/virtio/vhost.c | 30
t will be failed to hotplug a new DIMM
device since vhost_has_free_slot() finds no free slot left. It
should be successful if only part of memory slots have file
descriptor, so setting used memslots for vhost-user and
vhost-kernel respectively.
Signed-off-by: Igor Mammedov
Signed-off-by: Jay Zhou
gracefully.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Igor Mammedov
Signed-off-by: Jay Zhou
---
hw/virtio/vhost-user.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c
index 093675e..8500562 100644
--- a/hw/virtio/vhost
Since used_memslots will be updated to the actual value after
registering memory listener for the first time, move the
memslots limit checking to the right place.
Reviewed-by: Igor Mammedov
Signed-off-by: Jay Zhou
---
hw/virtio/vhost.c | 19 ---
1 file changed, 12 insertions
without vhostforce flag. So the followed up device_add
can fall back to userspace virtio successfully.
Suggested-by: Michael S. Tsirkin
Suggested-by: Igor Mammedov
Suggested-by: Jason Wang
Signed-off-by: Jay Zhou
---
net/tap.c | 18 +-
1 file changed, 13 insertions(+), 5
From: Gonglei
I posted the RFC verion a few months ago for DPDK
vhost-crypto implmention, and now it's time to send
the formal version. Because we need an user space scheme
for better performance.
The vhost user crypto server side patches had been
sent to DPDK community, pls see
[RFC PATCH 0/6]
works.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends/cryptodev-builtin.c | 1 +
backends/cryptodev-vhost-user.c | 16 +++
backends/cryptodev-vhost.c| 258 ++
hw/virtio/virtio-cry
From: Gonglei
Introduce two vhost-user meassges: VHOST_USER_CREATE_CRYPTO_SESSION
and VHOST_USER_CLOSE_CRYPTO_SESSION. At this point, the QEMU side
support crypto operation in cryptodev host-user backend.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
From: Gonglei
Signed-off-by: Gonglei
---
backends/cryptodev-vhost-user.c | 4
include/sysemu/cryptodev-vhost-user.h | 3 +++
2 files changed, 7 insertions(+)
diff --git a/backends/cryptodev-vhost-user.c b/backends/cryptodev-vhost-user.c
index 9cd06c4..862d4f2 100644
--- a/backends/c
From: Gonglei
Usage:
-chardev socket,id=charcrypto0,path=/path/to/your/socket
-object cryptodev-vhost-user,id=cryptodev0,chardev=charcrypto0
-device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends
works.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends/cryptodev-builtin.c | 1 +
backends/cryptodev-vhost-user.c | 16 +++
backends/cryptodev-vhost.c| 258 ++
hw/virtio/virtio-cry
From: Gonglei
Usage:
-chardev socket,id=charcrypto0,path=/path/to/your/socket
-object cryptodev-vhost-user,id=cryptodev0,chardev=charcrypto0
-device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends
From: Gonglei
Introduce two vhost-user meassges: VHOST_USER_CREATE_CRYPTO_SESSION
and VHOST_USER_CLOSE_CRYPTO_SESSION. At this point, the QEMU side
support crypto operation in cryptodev host-user backend.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
From: Gonglei
I posted the RFC verion a few months ago for DPDK
vhost-crypto implmention, and now it's time to send
the formal version. Because we need an user space scheme
for better performance.
The vhost user crypto server side patches had been
sent to DPDK community, pls see
[RFC PATCH 0/6]
From: Gonglei
Signed-off-by: Gonglei
---
backends/cryptodev-vhost-user.c | 4
include/sysemu/cryptodev-vhost-user.h | 3 +++
2 files changed, 7 insertions(+)
diff --git a/backends/cryptodev-vhost-user.c b/backends/cryptodev-vhost-user.c
index 9cd06c4..862d4f2 100644
--- a/backends/c
t will be failed to hotplug a new DIMM
device since vhost_has_free_slot() finds no free slot left. It
should be successful if only part of memory slots have file
descriptor, so setting used memslots for vhost-user and
vhost-kernel respectively.
Signed-off-by: Igor Mammedov
Signed-off-by: Jay Zhou
Since used_memslots will be updated to the actual value after
registering memory listener for the first time, move the
memslots limit checking to the right place.
Reviewed-by: Igor Mammedov
Signed-off-by: Jay Zhou
---
hw/virtio/vhost.c | 19 ---
1 file changed, 12 insertions
v8:
- rebased on the master
v7:
- rebased on the master
v2 ... v6:
- delete the "used_memslots" global variable, and add it
for vhost-user and vhost-kernel separately
- refine the function, commit log
- used_memslots refactoring
Jay Zhou (2):
vhost: fix memslot limit che
v1 -> v2:
* delete the "used_memslots" global variable, and add it
for vhost-user and vhost-kernel separately
Jay Zhou (2):
vhost: add used memslot number for vhost-user and vhost-kernel
separately
vhost: double check used memslots number
hw/virtio/vhost-backend.c
If the VM already has N(N>8) available memory slots for vhost user,
the VM will be crashed in vhost_user_set_mem_table if we try to
hotplug the first vhost user NIC.
This patch checks if memslots number exceeded or not after updating
vhost_user_used_memslots.
Signed-off-by: Jay Zhou
---
memory slots can be used by vhost user, it is failed to hot plug
a new memory RAM because vhost_has_free_slot just returned false,
but we can hot plug it safely in fact.
Signed-off-by: Jay Zhou
Signed-off-by: Zhe Liu
---
hw/virtio/vhost-backend.c | 14 ++
hw/virtio/vhost-
fixed the VM crash issue.
Suggested-by: Igor Mammedov
Signed-off-by: Jay Zhou
Signed-off-by: Zhe Liu
---
hw/virtio/vhost-backend.c | 14 +++
hw/virtio/vhost-user.c| 84 +--
hw/virtio/vhost.c | 16
include/hw/
fixed the VM crash issue.
Suggested-by: Igor Mammedov
Signed-off-by: Jay Zhou
Signed-off-by: Zhe Liu
---
hw/virtio/vhost-backend.c | 15 +++-
hw/virtio/vhost-user.c| 73 +++
hw/virtio/vhost.c | 18 +-
incl
fixed the VM crash issue.
Suggested-by: Igor Mammedov
Signed-off-by: Jay Zhou
Signed-off-by: Liuzhe
---
hw/virtio/vhost-backend.c | 15 +++-
hw/virtio/vhost-user.c| 74 +++
hw/virtio/vhost.c | 18 +-
incl
From: Gonglei
Usage:
-chardev socket,id=charcrypto0,path=/path/to/your/socket
-object cryptodev-vhost-user,id=cryptodev0,chardev=charcrypto0
-device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends
t will be failed to hotplug a new DIMM
device since vhost_has_free_slot() finds no free slot left. It
should be successful if only part of memory slots have file
descriptor, so setting used memslots for vhost-user and
vhost-kernel respectively.
Signed-off-by: Igor Mammedov
Signed-off-by: Jay Zhou
t will be failed to hotplug a new DIMM
device since vhost_has_free_slot() finds no free slot left. It
should be successful if only part of memory slots have file
descriptor, so setting used memslots for vhost-user and
vhost-kernel respectively.
Signed-off-by: Igor Mammedov
Signed-off-by: Jay Zhou
failed to open or
initialize but without vhostforce flag. So the followed up
device_add can fall back to userspace virtio successfully.
Suggested-by: Michael S. Tsirkin
Suggested-by: Igor Mammedov
Suggested-by: Jason Wang
Signed-off-by: Jay Zhou
---
v4: - reduce duplication
- close the fd by
From: Gonglei
Signed-off-by: Gonglei
---
backends/cryptodev-vhost-user.c | 4
include/sysemu/cryptodev-vhost-user.h | 3 +++
2 files changed, 7 insertions(+)
diff --git a/backends/cryptodev-vhost-user.c b/backends/cryptodev-vhost-user.c
index 9cd06c4..862d4f2 100644
--- a/backends/c
works.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends/cryptodev-builtin.c | 1 +
backends/cryptodev-vhost-user.c | 16 +++
backends/cryptodev-vhost.c| 258 ++
hw/virtio/virtio-cry
From: Gonglei
Introduce two vhost-user meassges: VHOST_USER_CREATE_CRYPTO_SESSION
and VHOST_USER_CLOSE_CRYPTO_SESSION. At this point, the QEMU side
support crypto operation in cryptodev host-user backend.
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
From: Gonglei
I posted the RFC verion a few months ago for DPDK
vhost-crypto implmention, and now it's time to send
the formal version. Because we need an user space scheme
for better performance.
The vhost user crypto server side patches had been
sent to DPDK community, pls see
[PATCH v2 00/10
From: Gonglei
Usage:
-chardev socket,id=charcrypto0,path=/path/to/your/socket
-object cryptodev-vhost-user,id=cryptodev0,chardev=charcrypto0
-device virtio-crypto-pci,id=crypto0,cryptodev=cryptodev0
Signed-off-by: Gonglei
Signed-off-by: Longpeng(Mike)
Signed-off-by: Jay Zhou
---
backends
fd should not be closed just because vhost failed to open or
initialize but without vhostforce flag. So the followed up
device_add can fall back to userspace virtio successfully.
Suggested-by: Michael S. Tsirkin
Suggested-by: Igor Mammedov
Suggested-by: Jason Wang
Signed-off-by: Jay Zhou
te the "used_memslots" global variable, and add it
for vhost-user and vhost-kernel separately
- refine the function, commit log
- used_memslots refactoring
Signed-off-by: Igor Mammedov
Signed-off-by: Jay Zhou
Signed-off-by: Liuzhe
---
hw/virtio/vhost-backend.c | 15 +++
Since the new capability KVM_DIRTY_LOG_INITIALLY_SET of
KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2 has been introduced in the
kernel, tweak the userspace side to detect and enable this
capability.
Signed-off-by: Jay Zhou
---
accel/kvm/kvm-all.c | 21 ++---
linux-headers/linux/kvm.h
100 matches
Mail list logo
