From: Julian Seward <jseward@acm.org>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: This project needs a stable branch
Date: Thu, 22 Mar 2007 23:57:54 +0000 [thread overview]
Message-ID: <200703222357.55469.jseward@acm.org> (raw)
In-Reply-To: <200703222327.47558.paul@codesourcery.com>
On Thursday 22 March 2007 23:27, Paul Brook wrote:
> > Do you mean you're asking me to break up Paul Brook's QOPS tree at
> > https://nowt.dyndns.org and submit it to mainline? I can do this thing,
> > if you really think it would help.
>
> If you implement all the missing bits in the process it'll help ;-)
What bits would they be then?
FWIW, I snarfed the patch last Sunday and tested it on amd64 host /
x86 guest, and successfully booted a couple of linux distros. So it's
not obviously broken, at least for my mundane host/guest choice.
It also seemed marginally slower on a big compile in the guest -
395.4 host cpu seconds for mainline vs 422.9 with qops. Is this
expected?
J
next prev parent reply other threads:[~2007-03-23 0:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 11:11 [Qemu-devel] RFC: This project needs a stable branch Julian Seward
2007-03-15 13:48 ` Anthony Liguori
2007-03-15 14:11 ` Julian Seward
2007-03-15 14:53 ` Paul Brook
2007-03-15 15:34 ` Avi Kivity
2007-03-20 22:19 ` Julian Seward
2007-03-22 22:47 ` Rob Landley
2007-03-22 23:00 ` Johannes Schindelin
2007-03-22 23:23 ` Rob Landley
2007-03-22 23:27 ` Paul Brook
2007-03-22 23:57 ` Julian Seward [this message]
2007-03-23 0:35 ` Paul Brook
2007-03-23 0:37 ` Johannes Schindelin
2007-03-22 23:29 ` Thiemo Seufer
2007-03-22 23:45 ` Rob Landley
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=200703222357.55469.jseward@acm.org \
--to=jseward@acm.org \
--cc=paul@codesourcery.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).