qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: 陳韋任 <chenwj@iis.sinica.edu.tw>
Cc: Alexander Graf <agraf@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Improve QEMU performance with LLVM codegen and other techniques
Date: Thu, 1 Dec 2011 10:59:53 +0000	[thread overview]
Message-ID: <CAFEAcA_iTWuxatkyQ-dSCaFw5ngDxAzWPuAONdi2QaYy9N0xBQ@mail.gmail.com> (raw)
In-Reply-To: <20111201035024.GA88545@cs.nctu.edu.tw>

On 1 December 2011 03:50, 陳韋任 <chenwj@iis.sinica.edu.tw> wrote:
> We use QEMU 0.13

Oops, I missed this. 0.13 is over a year old now. There is zero point
in doing any kind of engineering work of this scale on such an old
codebase. You need to be tracking the head of git master, generally,
if you want (a) any hope of getting your changes back into qemu or
(b) any kind of useful support for problems you encounter during
development.

-- PMM

  parent reply	other threads:[~2011-12-01 11:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29  7:03 [Qemu-devel] Improve QEMU performance with LLVM codegen and other techniques 陳韋任
2011-11-30 12:37 ` Alexander Graf
2011-12-01  3:50   ` 陳韋任
2011-12-01  7:46     ` Stefan Hajnoczi
2011-12-01  9:16       ` Alex Bradbury
2011-12-01  9:30       ` 陳韋任
2011-12-01 10:23     ` Alexander Graf
2011-12-04  6:14       ` 陳韋任
2011-12-04 11:29         ` Alexander Graf
2011-12-05  6:05           ` 陳韋任
2011-12-01 10:59     ` Peter Maydell [this message]
2011-12-06  7:39   ` 陳韋任
2011-12-19 17:44     ` Alexander Graf
2011-11-30 12:51 ` Peter Maydell
2011-12-01  9:03   ` 陳韋任
2011-12-01  9:13     ` 陳韋任
2011-12-01  9:15     ` Max Filippov
2011-12-01  9:25       ` 陳韋任
2011-12-01  9:41         ` Max Filippov
2011-12-06  6:37           ` 陳韋任
2011-12-01 10:12     ` Peter Maydell
2011-12-01 10:40       ` 陳韋任

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=CAFEAcA_iTWuxatkyQ-dSCaFw5ngDxAzWPuAONdi2QaYy9N0xBQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=agraf@suse.de \
    --cc=chenwj@iis.sinica.edu.tw \
    --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).