All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Ady Wahyudi Paundu <awpaundu@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help for beginner
Date: Thu, 15 Jan 2015 15:53:19 +0000	[thread overview]
Message-ID: <87387c2g7k.fsf@linaro.org> (raw)
In-Reply-To: <CAOzyQ1F7qZiPSB0r=JD=KTpCHjxRepGa0H+g97-ypdEgKNLKpA@mail.gmail.com>


Ady Wahyudi Paundu <awpaundu@gmail.com> writes:

> Hi all, Happy New Year (not too late I hope)
> I also hope you guys don't' mind to be bothered by newbie questions
> related to Qemu, because I really don't know where else to ask.  I
> want to learn how several aspects of qemu works, and it really hard to
> find resources (physical or virtual) about it.  From qemu
> documentation "QEMU does not have a high level design description
> document - only the source code tells the full story"
> My question, if i want to learn CPU and/or Network related operation
> within Qemu, what file (or function) should i put my focus into?

If you are interested in the TCG emulation then you'll probably want to
start with:

target-${PROCESSOR}/translate.c

Where the instruction decode is carried out to translate guest
instructions into TCG ops which are then used to generate host code.


> for
> example, simple ping operation from within a guest VM will use what
> functions?
> Thank you in advance.
>
> regards,
> ady

-- 
Alex Bennée

      parent reply	other threads:[~2015-01-15 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13  1:40 [Qemu-devel] Help for beginner Ady Wahyudi Paundu
2015-01-15 15:32 ` Stefan Hajnoczi
2015-01-26  2:11   ` Ady Wahyudi Paundu
2015-01-26  4:10     ` Ady Wahyudi Paundu
2015-01-15 15:53 ` Alex Bennée [this message]

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=87387c2g7k.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=awpaundu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.