From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Xen-devel@lists.xensource.com, Chu Rui <ruichu@gmail.com>
Subject: Re: Balloon driver for Linux/HVM
Date: Wed, 24 Nov 2010 10:53:58 -0800 [thread overview]
Message-ID: <4CED5F46.5050004@goop.org> (raw)
In-Reply-To: <20101122095146.GA2455@router-fw-old.local.net-space.pl>
On 11/22/2010 01:51 AM, Daniel Kiper wrote:
> Hi,
>
> On Thu, Nov 18, 2010 at 12:32:35PM -0800, Dan Magenheimer wrote:
>> What is the difference between 2.6.36 balloon driver and Jeremy's
>> xen/balloon tree head? I think ideally the kernel version for
>> development should be the latest (2.6.36).
> I know that the best practice is to base new work on the
> latest stable kernel version, however I am not sure that it is
> the case there. xen/balloon head contains most of neweset fixes
> and improvments which are not merged into current stable till
> now. That is why I think we should start from this and later
> merge it with current stable. However, maybe Jeremy may have
> better view of which version would be better for the start
> of development.
>
The big difference between xen/balloon and current mainline is hugepage
support, which is not yet in an upstreamable state. Aside from that,
current upstream balloon driver (in current git, post 2.6.37-rc3) is
equivalent, and would make a good base for development.
The main difference between .37-rc and .36 is support for boot-time
ballooning, but the changes to the balloon driver to support that are
small, so .36 would probably make a reasonable base as well.
J
next prev parent reply other threads:[~2010-11-24 18:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 10:49 Balloon driver for Linux/HVM Chu Rui
2010-11-16 11:35 ` Stefano Stabellini
2010-11-16 11:44 ` 牛立新
2010-11-16 12:56 ` George Dunlap
2010-11-16 15:37 ` Chu Rui
2010-11-16 17:10 ` Dan Magenheimer
2010-11-17 2:28 ` Chu Rui
2010-11-17 17:40 ` Dan Magenheimer
2010-11-17 9:46 ` George Dunlap
2010-11-17 9:53 ` George Dunlap
2010-11-17 11:50 ` Chu Rui
2010-11-17 13:04 ` Daniel Kiper
2010-11-17 14:05 ` Chu Rui
2010-11-17 15:29 ` Daniel Kiper
2010-11-17 17:48 ` Dan Magenheimer
2010-11-18 3:50 ` Chu Rui
2010-11-18 17:52 ` Daniel Kiper
2010-11-18 20:32 ` Dan Magenheimer
2010-11-22 9:51 ` Daniel Kiper
2010-11-24 10:14 ` Daniel Kiper
2010-11-24 18:53 ` Jeremy Fitzhardinge [this message]
2010-12-02 11:06 ` Daniel Kiper
2010-11-19 16:53 ` Chu Rui
2010-11-22 10:02 ` Daniel Kiper
[not found] ` <AANLkTikUSQ3e-U3jKmnWit2jP=nk5858p9ou2PBXVmCA@mail.gmail.com>
2010-11-24 7:38 ` Fwd: " Chu Rui
2010-11-24 9:49 ` Daniel Kiper
-- strict thread matches above, loose matches on Subject: below --
2010-11-16 10:46 Rui Chu
2010-11-16 10:46 ` Rui Chu
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=4CED5F46.5050004@goop.org \
--to=jeremy@goop.org \
--cc=Xen-devel@lists.xensource.com \
--cc=dan.magenheimer@oracle.com \
--cc=dkiper@net-space.pl \
--cc=ruichu@gmail.com \
/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.