From: Steven Rostedt <rostedt@goodmis.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: virtualization@lists.osdl.org
Subject: Re: [RFC/PATCH PV_OPS X86_64 00/17] Paravirt_ops for x86_64
Date: Thu, 08 Mar 2007 08:05:07 -0500 [thread overview]
Message-ID: <1173359107.25848.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20070308064729.GZ10574@sequoia.sous-sol.org>
On Wed, 2007-03-07 at 22:47 -0800, Chris Wright wrote:
> * Steven Rostedt (rostedt@goodmis.org) wrote:
> > Well, it's still kind of crappy, but it's starting to work. So I spent
> > today, pulling out patches related only to paravirt ops from our git
> > repo, and separating them to be readable. Well, here they are.
>
> Cool. I had split these up slightly differently, with core changes
> coming first (like places where raw asm is still left behind), followed
> by adding in the paravirt bits. I think it would be useful to get those
> simple basic changes to the front of the queue, because they can
> largely be merged right away w/out issue. I'll look through the lot
> tomorrow.
The way I split it, and what took me so long to split it, was that I
wanted each patch to be able to compile. There was one two-way
dependency, I think that was between patches 7 and 8. But the most part,
each addition of a patch allowed for a successful compile. I didn't
test running those though ;)
I can work on splitting it better. After pushing out the lguest64
patches (coming soon).
-- Steve
next prev parent reply other threads:[~2007-03-08 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 6:01 [RFC/PATCH PV_OPS X86_64 00/17] Paravirt_ops for x86_64 Steven Rostedt
2007-03-08 6:47 ` Chris Wright
2007-03-08 13:05 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-08 5:53 Steven Rostedt
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=1173359107.25848.23.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.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).