From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH, RFC] Update qemu-tech.texi, needs verification
Date: Sun, 5 Oct 2008 11:44:47 +0300 [thread overview]
Message-ID: <f43fc5580810050144t7f1d6d15ie006558f63f10953@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 390 bytes --]
Hi,
Currently qemu-tech.texi is no longer in synch with QEMU development.
There are obsoleted references to code copying and dyngen versions,
TCG has changed a lot regarding code generation and target/host status
is no longer accurate.
In this patch I've tried to update the document based on my
understanding of how stuff works and what is the status of various
targets. Please comment.
[-- Attachment #2: update_qemu_tech.diff --]
[-- Type: plain/text, Size: 15174 bytes --]
next reply other threads:[~2008-10-05 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 8:44 Blue Swirl [this message]
2008-10-05 12:26 ` [Qemu-devel] [PATCH, RFC] Update qemu-tech.texi, needs verification Edgar E. Iglesias
2008-10-05 12:55 ` Thiemo Seufer
2008-10-05 17:28 ` malc
2008-10-06 13:26 ` Paul Brook
2008-10-06 17:53 ` Blue Swirl
2008-10-06 18:02 ` Paul Brook
2008-10-06 18:19 ` Laurent Desnogues
2008-10-06 19:09 ` andrzej zaborowski
2008-10-10 6:56 ` Kirill A. Shutemov
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=f43fc5580810050144t7f1d6d15ie006558f63f10953@mail.gmail.com \
--to=blauwirbel@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).