From: Ata Fatahi baarzi <afbcesh91@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] qemu io stack code approach
Date: Fri, 8 Jan 2016 17:10:00 +0330 [thread overview]
Message-ID: <CAFRi3MTPRM5DPFmKX9QngUtc4j8Y9PhJBwNA12Fo8DnV_sD60w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
hi all
I recently pursued Linux IO stack and dove into kernel source code. that is
when a user programm calls read or write syscall some functions will be
called to finally make a io request and send it to device drivers and
compelete io request.
in this path which is known as Life of IO request i placed some printks in
linux kernel and compile and install it then i can see IO requests
information in /var/log/syslog.
i totally used This good Post
<https://scaryreasoner.wordpress.com/2013/09/14/the-life-of-io-in-the-linux-kernel/>
which done for linux kernel.
know i wanna do some thing like that in qemu to answer these too important
questions:
1- what is path of a IO request from a guest os to host os and finally
disk? (both siurce code approach and io stack approach)
2- how qemu determines an IO request is corresponds to which guest os?(if
its feasible)
--
Best Rega
r
ds
Ata Fatahi Baarzi <http://ce.sharif.edu/~fatahibarzi>
[-- Attachment #2: Type: text/html, Size: 2021 bytes --]
reply other threads:[~2016-01-08 13:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFRi3MTPRM5DPFmKX9QngUtc4j8Y9PhJBwNA12Fo8DnV_sD60w@mail.gmail.com \
--to=afbcesh91@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).