From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Christian Zoffoli <czoffoli@xmerlin.org>
Subject: Re: Performance numbers on PV-on-HVM
Date: Mon, 04 Oct 2010 12:23:14 -0700 [thread overview]
Message-ID: <4CAA29A2.7000802@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1010041807260.2440@kaball-desktop>
On 10/04/2010 10:08 AM, Stefano Stabellini wrote:
> On Mon, 4 Oct 2010, Stefano Stabellini wrote:
>> On Fri, 1 Oct 2010, Jeremy Fitzhardinge wrote:
>>>>> Hopefully Jeremy merges 2.6.32-pvhvm to xen/stable-2.6.32.x branch..
>>>>
>>>> The problem is that Jeremy's stable branch is sufficiently different
>>>> from stable 2.6.32 that the port in non-trivial.
>>>> It would probably easier for him to cherry-pick the last 6 patches in
>>>> the series.
>>> I tried this, but it is a bit awkward:
>>>
>>> Two of them have already been applied verbatim.
>>>
>>> The blkfront name patch clashes with something similar that's already in
>>> xen/next (the version I currently have does xlbd_reserve_minors(), but
>>> this branch's patch doesn't). I don't know which version to take.
>>>
>> just take the latest version
>>
>>> The hvc console patches clash fairly badly with the dom0 ones; nothing
>>> fundamental, but fiddly.
>> skip them for now: they are not critical and at some point I'll rebase
>> them on top of the "xen initial domain" series that has dom0 hvc_xen
>> support and you'll be able to pull them without conflicts.
>>
>>> The balloon.c changes clash with the largepage ballooning stuff.
>>>
>>
>> I have reworked the balloon patch on top of stable 2.6.32, I am attaching
>> the patch to this email.
>
> of course if you would like me to prepare a branch on top of
> stable-2.6.32.x I can do that as well
A resolved merge would be better than rebasing onto stable-2.6.32.x.
J
next prev parent reply other threads:[~2010-10-04 19:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 6:24 Performance numbers on PV-on-HVM Jagadish Nadimpalli
2010-09-27 10:22 ` Stefano Stabellini
2010-09-27 11:27 ` Jagadish Nadimpalli
2010-09-27 11:49 ` Stefano Stabellini
2010-09-27 12:42 ` Jagadish Nadimpalli
2010-09-27 13:11 ` Stefano Stabellini
2010-09-27 15:48 ` Jagadish Nadimpalli
2010-09-28 10:28 ` Jagadish Nadimpalli
2010-09-28 11:01 ` Pasi Kärkkäinen
2010-09-28 11:28 ` Jagadish Nadimpalli
2010-09-28 22:17 ` Christian Zoffoli
2010-09-29 9:10 ` Stefano Stabellini
2010-09-30 18:56 ` Christian Zoffoli
2010-10-01 6:00 ` Pasi Kärkkäinen
2010-10-01 13:19 ` Christian Zoffoli
2010-10-01 13:42 ` Pasi Kärkkäinen
2010-10-01 14:06 ` Stefano Stabellini
2010-10-01 14:13 ` Pasi Kärkkäinen
2010-10-01 14:16 ` Stefano Stabellini
2010-10-01 22:19 ` Jeremy Fitzhardinge
2010-10-04 17:06 ` Stefano Stabellini
2010-10-04 17:08 ` Stefano Stabellini
2010-10-04 19:23 ` Jeremy Fitzhardinge [this message]
2010-10-01 15:10 ` Christian Zoffoli
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=4CAA29A2.7000802@goop.org \
--to=jeremy@goop.org \
--cc=czoffoli@xmerlin.org \
--cc=stefano.stabellini@eu.citrix.com \
--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 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.