From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56008) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNhBl-0000Zn-P9 for qemu-devel@nongnu.org; Mon, 25 Jan 2016 08:28:14 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aNhBh-0007Up-5H for qemu-devel@nongnu.org; Mon, 25 Jan 2016 08:28:13 -0500 Received: from mail-lb0-x22e.google.com ([2a00:1450:4010:c04::22e]:36462) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aNhBg-0007Ue-OB for qemu-devel@nongnu.org; Mon, 25 Jan 2016 08:28:09 -0500 Received: by mail-lb0-x22e.google.com with SMTP id oh2so73863047lbb.3 for ; Mon, 25 Jan 2016 05:28:08 -0800 (PST) MIME-Version: 1.0 From: Ata Fatahi baarzi Date: Mon, 25 Jan 2016 16:57:47 +0330 Message-ID: Content-Type: multipart/alternative; boundary=001a11c3bc4e193a58052a288a75 Subject: [Qemu-devel] qemu io path List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org --001a11c3bc4e193a58052a288a75 Content-Type: text/plain; charset=UTF-8 hi dear all. im searching for qemu io (storage) stack. i searched a lot but just found some slides which does not present so much. is there any text explanation or article or blog post which describes precisely qemu io stack? I would be grateful if you provide something for me. and have some question hope you answer them. before ask my question its worth noting that i have an excellent background about Linux io stack and read qemu source code for main io thread and know about qemu structure, guest os ,... i read [hw/block/virtio-blk.c] and started from virtio_blk_handle_output function and trace it until reached to io_submit! that great we reached host kernel libaio syscalls. but what made me confuesd, is what and where and when th stuffs for doing a typical io request from a typical guest os starts?! now here is my questions: 1- i wanna know codes which doing so.(start an io request until io_submit get called) 2- can you give me th exact path of an io request from app in guest os through qemu until get to real disk? 3- does it possible to determin bellow featers for an io request: a- which guest os sent this io request? b- address which io request points to? c- request type read/write? d- request size? e- if there is multiple disks in system, where it is define io request is corresponds to which disk? thank a lot -- Best Regrads Ata Fatahi Baarzi --001a11c3bc4e193a58052a288a75 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
hi dear all. im searching for qemu io (storage) stack. i searched a lot but just=20 found some slides which does not present so much. is there any text explanation or article or blog post which describes =20 precisely qemu io stack? I would be grateful if you provide something for me. and have some question hope you answer them. before ask my question its worth noting that i have an excellent=20 background about Linux io stack and read qemu source code for main io=20 thread and know about qemu structure, guest os ,... i read [hw/block/virtio-blk.c] and started from=20 virtio_blk_handle_output function and trace it until reached to=20 io_submit! that great we reached host kernel libaio syscalls. but what made me confuesd, is what and where and when th stuffs for=20 doing a typical io request from a typical guest os starts?! now here is my questions: 1- i wanna know codes which doing so.(start an io request until=20 io_submit get called) 2- can you give me th exact path of an io request from app in guest os=20 through qemu until get to real disk? 3- does it possible to determin bellow featers for an io request: a- which guest os sent this io request? b- address which io request points to? c- request type read/write? d- request size? e- if there is multiple disks in system, where it is define io=20 request is corresponds to which disk? thank a lot

--
--001a11c3bc4e193a58052a288a75--