All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Adeoluwa Ademoye <adeoluwaademoye@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Newcomer] Introduction and seeking guidance on TCG / memory architecture
Date: Mon, 06 Apr 2026 17:42:32 +0100	[thread overview]
Message-ID: <8734186nwn.fsf@draig.linaro.org> (raw)
In-Reply-To: <CAPxx-NymyR=iJ9CpdccOep=gO=L8gzjuTytXZ2DhGBhXpttSmg@mail.gmail.com> (Adeoluwa Ademoye's message of "Mon, 6 Apr 2026 00:04:25 +0100")

Adeoluwa Ademoye <adeoluwaademoye@gmail.com> writes:

> Hi everyone,
>
> I am an engineering student with a focus on systems programming and low-level execution. To build foundational knowledge, I
> recently wrote a stack-based virtual machine from scratch in C, implementing a dynamic type system with runtime type dispatch, raw
> bytecode execution, and manual memory ownership across the entire object graph.
>
> I am now looking to channel that into real open source contribution, and QEMU is where I want to start. The TCG subsystem and
> memory translation layer are the areas that interest me most.
>
> Before I dive into the codebase, could anyone point me toward the right documentation or entry-level issues in the TCG or memory
> subsystem? I want to make sure I am orientating myself correctly from
> the start.

What documentation we have is here:

  https://www.qemu.org/docs/master/devel/index-tcg.html

You can also see:

  https://www.qemu.org/docs/master/devel/codebase.html

for a quick tour of the code.

>
> Thank you for your time.
>
> Best regards,
> Daniel

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


      reply	other threads:[~2026-04-06 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-05 23:04 [Newcomer] Introduction and seeking guidance on TCG / memory architecture Adeoluwa Ademoye
2026-04-06 16:42 ` 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=8734186nwn.fsf@draig.linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=adeoluwaademoye@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.