> On Mar 14, 2016, at 10:09 PM, Huaicheng Li wrote:
>
>
>> On Mar 13, 2016, at 8:42 PM, Fam Zheng wrote:
>>
>> On Sun, 03/13 14:37, Huaicheng Li (coperd) wrote:
>>> Hi all,
>>>
>>> What I’m confused about is that:
>>>
>>
Hi all,
I meet some trouble in understanding IDE emulation:
(1) IDE I/O Down Path (In VCPU thread):
upon KVM_EXIT_IO, corresponding disk ioport write function will write IO info
to IDEState, then ide read callback function will eventually split it into
**several DMA transfers** and eventually
> On Mar 5, 2016, at 8:42 PM, Huaicheng Li (coperd) wrote:
>
>
>> On Mar 1, 2016, at 3:01 PM, Paolo Bonzini > <mailto:pbonz...@redhat.com>> wrote:
>>
>> This is done
>> because the worker threads only care about the queued request list, not
>&
> On Mar 1, 2016, at 3:01 PM, Paolo Bonzini wrote:
>
> This is done
> because the worker threads only care about the queued request list, not
> about active or completed requests.
Do you think it would be useful to add an API for inserting one request back
to the queued list? For example, In c
> On Mar 1, 2016, at 3:34 PM, Stefan Hajnoczi wrote:
>
> Have you seen Linux Documentation/device-mapper/delay.txt?
>
> You could set up a loopback block device and put the device-mapper delay
> target on top to simulate latency.
I’m working on one idea to emulate the latency of SSD read/wri
