On Mon, Nov 14, 2016 at 08:36:39PM +0800, zhun...@gmail.com wrote:
> I have a question about qemu.is it a bug in qemu version 1.2?
> in qemu version 1.2 ,it set avail event by the code :
> if (vq->vdev->guest_features & (1 << VIRTIO_RING_F_EVENT_IDX)) {
> vring_avail_event(vq, vring_avail_
On Sat, Nov 12, 2016 at 04:43:21PM +0800, zhun...@gmail.com wrote:
> Thanks,the expression is not the key problem,I just write it wrong,the key
> problem is that what I get from the code is everytime dirver add a sg ,it
> will call virtqueue_kick,such as network driver,in start_xmit function ,it
I have a question about qemu.is it a bug in qemu version 1.2?
in qemu version 1.2 ,it set avail event by the code :
if (vq->vdev->guest_features & (1 << VIRTIO_RING_F_EVENT_IDX)) {
vring_avail_event(vq, vring_avail_idx(vq));
}
and in version 2.7 the code is
if (virtio_vdev_has_fe
??is qemu handle
buffer faster than driver add it??
thank you very much!
zhun...@gmail.com
From: Stefan Hajnoczi
Date: 2016-11-11 20:03
To: zhun...@gmail.com
CC: qemu
Subject: Re: Re: [Qemu-devel] virtIO question
On Thu, Nov 10, 2016 at 08:16:38PM +0800, zhun...@gmail.com wrote:
> From t
virtqueue_kick
,why it handle like this??can you explain it to me??thank you very much!!!
zhun...@gmail.com
From: Stefan Hajnoczi
Date: 2016-11-11 20:03
To: zhun...@gmail.com
CC: qemu
Subject: Re: Re: [Qemu-devel] virtIO question
On Thu, Nov 10, 2016 at 08:16:38PM +0800, zhun...@gmail.com
¼šqemu
主题：Re: Re: [Qemu-devel] virtIO question
On Thu, Nov 10, 2016 at 08:16:38PM +0800, zhun...@gmail.com wrote:
> From this point of view ,I think it make sense well, thank you very
much!
> but I have another question about notify mechanism between virtIO
driver an
On Thu, Nov 10, 2016 at 08:16:38PM +0800, zhun...@gmail.com wrote:
> From this point of view ,I think it make sense well, thank you very much!
> but I have another question about notify mechanism between virtIO driver and
> qemu.
> according the source code of Linux and qemu,
> when driver add a
I describe it clearly.or can you give me an example to prove
how it make sense!!
thanks a lot!
zhun...@gmail.com
From: Stefan Hajnoczi
Date: 2016-11-10 18:32
To: zhun...@gmail.com
CC: jkhasdev; qemu
Subject: Re: [Qemu-devel] virtIO question
On Wed, Nov 09, 2016 at 06:58:16PM +0800, zhun...@gmai
On Wed, Nov 09, 2016 at 06:58:16PM +0800, zhun...@gmail.com wrote:
> I want to ask a another question,why a virt_queue in virtio include in_sgs
> and out_sgs,for example,send_queue of virtIO net driver have in_sgs and
> out_sgs，when transmit data,It add buffer to out_sgs of send_queue,but how it
Date: 2016-11-05 23:41
To: Peter Maydell
CC: zhun...@gmail.com; qemu-devel
Subject: Re: [Qemu-devel] virtIO question
Have you looked at the virtio specification?
No.
This describes
the overall structure and communication mechanism, which
QEMU and Linux each only implement one half of:
http
thanks a lot!I will read the document carefully!
æ�¥è‡ª é…æ—� MX5
原始邮件
�件人：jitendra kumar khasdev
æ—¶é—´ï¼šå‘¨å… 11月5æ—¥ 23:11
收件人：Peter Maydell
抄�：zhun...@gmail.com,qemu-devel
主题：Re: [Qemu-devel] virtIO question
>
> Have you looked at the virtio specification?
No.
> This describes
> the overall structure and communication mechanism, which
> QEMU and Linux each only implement one half of:
> http://docs.oasis-open.org/virtio/virtio/v1.0/virtio-v1.0.html
Thanks Peter. This doc looks me interesting.
---
On 5 November 2016 at 14:46, jitendra kumar khasdev wrote:
> here is what I find difficulty in understanding the code,
>
> 1. Qemu virtio datastructures are not so clear.
> 2. I didn't find any sort high level design with respective qemu for virtIO.
> 3. How qemu virtIO and linux virtIO does share
Hi All,
I am also exploring virtio implementation in qemu, I try to understand
virtio in linux(guest) and qemu, but I am not able to understand I/O stack
between linux to qemu.
here is what I find difficulty in understanding the code,
1. Qemu virtio datastructures are not so clear.
2. I didn't f
who can explain the means of idx in VRingUsed and VRingAvail structure about
virtIO??
thanks!
zhun...@gmail.com
On Wed, May 13, 2015 at 07:16:13PM +, Subhashini Venkataraman wrote:
> I have a question on VRING_DESC_F_WRITE flag. As per the specifications, if
> this flag is set, then the corresponding buffer pointed by the descriptor is
> Write only, otherwise Read Only. I am trying to understand why
Hi,
I have a question on VRING_DESC_F_WRITE flag. As per the specifications, if
this flag is set, then the corresponding buffer pointed by the descriptor is
Write only, otherwise Read Only. I am trying to understand why there is no
READ_AND_WRITE option, i.e. a buffer could be Read by device
17 matches
Mail list logo
