From: Jeremy Fitzhardinge <jeremy@goop.org>
To: M A Young <m.a.young@durham.ac.uk>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Dave McCracken <dcm@mccr.org>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Re: Balloon driver crash
Date: Tue, 08 Jun 2010 16:38:56 -0700 [thread overview]
Message-ID: <4C0ED490.1010004@goop.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1006090002510.2619@vega4.dur.ac.uk>
On 06/08/2010 04:08 PM, M A Young wrote:
> On Tue, 8 Jun 2010, Jeremy Fitzhardinge wrote:
>
>> Actually it looks like this was fixed on the xen/hugepage-balloon a long
>> time ago, but I guess that branch wasn't merged across to xen/next
>> because it was based on xen/master and so awkward to merge into the
>> .32-based and later branches.
>>
>> I need to check how the current hugepage support has made it into the
>> .32 based tree, assuming it has. It will take a bit of git archeology.
>
> There is an "Add hugepage support to balloon driver" in xen/balloon
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=refs/heads/xen/balloon
> and xen/balloon was later merged into xen/next
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=53fbeec80db2d7c5677da8d47096d156332731c4
>
> xen/next has been merged into xen/stable-2.6.32.x a few times since then.
Thanks. I just cherry-picked the subsequent fixes over and merged them
in. Please check it out.
J
prev parent reply other threads:[~2010-06-08 23:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 13:37 Balloon driver crash M A Young
2010-06-03 19:37 ` M A Young
2010-06-03 20:36 ` Ian Campbell
2010-06-03 22:38 ` Dave McCracken
2010-06-07 19:29 ` M A Young
2010-06-08 7:56 ` Ian Campbell
2010-06-08 8:28 ` M A Young
2010-06-08 8:42 ` Ian Campbell
2010-06-08 9:25 ` [PATCH] " M A Young
2010-06-08 10:59 ` Pasi Kärkkäinen
2010-06-08 11:07 ` M A Young
2010-06-08 16:43 ` Jeremy Fitzhardinge
2010-06-08 18:08 ` M A Young
2010-06-08 18:34 ` Jeremy Fitzhardinge
2010-06-08 22:48 ` Jeremy Fitzhardinge
2010-06-08 23:08 ` M A Young
2010-06-08 23:38 ` Jeremy Fitzhardinge [this message]
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=4C0ED490.1010004@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@citrix.com \
--cc=dcm@mccr.org \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xensource.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 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).