On Mon, Mar 12, 2012 at 11:49 AM, Kevin Wolf wrote:
> Am 12.03.2012 12:39, schrieb Stefan Hajnoczi:
>> On Wed, Dec 21, 2011 at 3:35 PM, Stefan Hajnoczi
>> wrote:
>>> @@ -1776,6 +1779,9 @@ int main(int argc, char **argv)
>>> case 'k':
>>> flags |= BDRV_O_NATIVE_AIO;
>>>
Am 12.03.2012 12:39, schrieb Stefan Hajnoczi:
> On Wed, Dec 21, 2011 at 3:35 PM, Stefan Hajnoczi
> wrote:
>
> Ping? Do you want to take this through the block tree?
Sorry, I completely missed this one.
>> It can be useful to enable QEMU tracing when trying out block layer
>> interfaces via qem
On Wed, Dec 21, 2011 at 3:35 PM, Stefan Hajnoczi
wrote:
Ping? Do you want to take this through the block tree?
> It can be useful to enable QEMU tracing when trying out block layer
> interfaces via qemu-io. Tracing can be enabled using the new -t FILE
> option where the given file contains a l
It can be useful to enable QEMU tracing when trying out block layer
interfaces via qemu-io. Tracing can be enabled using the new -t FILE
option where the given file contains a list of trace events to enable
(just like the qemu --trace events=FILE option).
$ echo qemu_vfree >my-events
$ ./qemu
