On 2013/5/20 15:43, Michael S. Tsirkin wrote:
On Mon, May 20, 2013 at 02:11:19AM +, Qinchuanyu wrote:
Vhost thread provide both tx and rx ability for virtio-net.
In the forwarding scenarios, tx and rx share the vhost thread, and throughput
is limited by single thread.
So I did a patch for
Hi,
To support linux guests with old kernel version, vitio driver backport
is needed. But I cannot find kvm-guest-drivers-linux.git now.
>From linux distributions' virtio backport versions, such as
virtio-0.1-18.el3.src.rpm for RHEl3 hat and
novell-virtio-drivers-2.6.27-sle10sp3.iso for SLES 10 sp3
On 2012/2/1,星期三 16:12, Amit Shah wrote:
Hi,
Sorry for the late reply.
On (Thu) 12 Jan 2012 [09:20:07], zanghongy...@huawei.com wrote:
From: Hongyong Zang
Add setup_port_vq(). Create the io ports' vqs when add_port.
Can you describe the changes in more detail, please?
The motivation of this
Pekka Enberg wrote:
On Mon, Dec 19, 2011 at 4:27 AM, wrote:
From: Hongyong Zang
If a guest's ram_size exceeds KVM_32BIT_GAP_START, the corresponding kvm tool's
virtual address size should be (ram_size + KVM_32BIT_GAP_SIZE), rather than
ram_size.
Signed-off-by: Hongyong Zang
Please CC me on
于 2011/12/19,星期一 15:26, Amit Shah 写道:
On (Mon) 19 Dec 2011 [14:09:43], Zang Hongyong wrote:
于 2011/12/16,星期五 17:39, Amit Shah 写道:
On (Fri) 16 Dec 2011 [09:14:26], zanghongy...@huawei.com wrote:
From: Hongyong Zang
In pci_enable_msix(), the guest's virtio-serial driver tries to set msi-x
于 2011/12/16,星期五 17:39, Amit Shah 写道:
On (Fri) 16 Dec 2011 [09:14:26], zanghongy...@huawei.com wrote:
From: Hongyong Zang
In pci_enable_msix(), the guest's virtio-serial driver tries to set msi-x
with one vector per queue. But it fails and eventually all virtio-serial
ports share one MSI-X vect
于 2011/12/16,星期五 17:46, Sasha Levin 写道:
On Fri, 2011-12-16 at 17:33 +0800, Zang Hongyong wrote:
Do you see an issue with increasing kvm->ram_size?
Yes, it will cause some problems after simply increase the kvm->ram_size.
For examples:
In kvm__init_ram() code we use kvm->ram_size to
于 2011/12/16,星期五 16:45, Sasha Levin 写道:
> On Fri, 2011-12-16 at 16:36 +0800, Zang Hongyong wrote:
>> 于 2011/12/16,星期五 15:23, Sasha Levin 写道:
>>> On Fri, 2011-12-16 at 15:02 +0800, Zang Hongyong wrote:
>>>> 于 2011/12/16,星期五 13:50, Sasha Levin 写道:
>>>>>
于 2011/12/16,星期五 15:23, Sasha Levin 写道:
> On Fri, 2011-12-16 at 15:02 +0800, Zang Hongyong wrote:
>> 于 2011/12/16,星期五 13:50, Sasha Levin 写道:
>>> On Fri, 2011-12-16 at 09:01 +0800, zanghongy...@huawei.com wrote:
>>>> If a guest's ram_size exceeds KVM_32B
于 2011/12/16,星期五 15:59, Sasha Levin 写道:
> On Fri, 2011-12-16 at 15:40 +0800, Zang Hongyong wrote:
>> 于 2011/12/16,星期五 15:05, Sasha Levin 写道:
>>> On Fri, 2011-12-16 at 13:32 +0800, zanghongy...@huawei.com wrote:
>>>> From: Hongyong Zang
>>>>
>>>&
于 2011/12/16,星期五 15:05, Sasha Levin 写道:
On Fri, 2011-12-16 at 13:32 +0800, zanghongy...@huawei.com wrote:
From: Hongyong Zang
Vhost-net uses its own vhost_memory, which results from user space (qemu) info,
to translate GPA to HVA. Since kernel's kvm structure already maintains the
address relat
于 2011/12/16,星期五 13:50, Sasha Levin 写道:
On Fri, 2011-12-16 at 09:01 +0800, zanghongy...@huawei.com wrote:
If a guest's ram_size exceeds KVM_32BIT_GAP_START, the corresponding kvm tool's
virtual address size should be (ram_size + KVM_32BIT_GAP_SIZE), rather than
ram_size.
You're right.
There a
Can this bug fix patch be applied yet?
With this bug, guest os cannot successfully boot with ioeventfd.
Thus the new PIO DoorBell patch cannot be posted.
Thanks,
Hongyong
于 2011/11/24,星期四 18:05, zanghongy...@huawei.com 写道:
> From: Hongyong Zang
>
> When a guest boots with ioeventfd, an error (by
于 2011/11/29,星期二 14:38, Cam Macdonell 写道:
On Thu, Nov 17, 2011 at 10:50 PM, wrote:
From: Hongyong Zang
This patch, adds a PIO BAR3 for guest notifying qemu. And we find the new
notification way of PIO BAR3 reduces 30% time in comparison with the original
MMIO BAR0 way.
Come to think of it,
于 2011/11/25,星期五 4:29, Cam Macdonell 写道:
On Thu, Nov 24, 2011 at 3:05 AM, wrote:
From: Hongyong Zang
When a guest boots with ioeventfd, an error (by gdb) occurs:
Program received signal SIGSEGV, Segmentation fault.
0x006009cc in setup_ioeventfds (s=0x171dc40)
at /home/louzhen
于 2011/11/16,星期三 2:43, Cam Macdonell 写道:
On Sun, Nov 13, 2011 at 8:56 PM, wrote:
From: Hongyong Zang
Ivshmem(nahanni) is a mechanism for sharing host memory with VMs running on the
same host. Currently, guest notifies qemu by reading or writing ivshmem
device's PCI MMIO BAR0(Doorbell).
This
16 matches
Mail list logo
