All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 01 Oct 2010 15:19:36 -0700	[thread overview]
Message-ID: <4CA65E78.1000400@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1010011514240.2864@kaball-desktop>

 On 10/01/2010 07:16 AM, Stefano Stabellini wrote:
> On Fri, 1 Oct 2010, Pasi K??rkk??inen wrote:
>> On Fri, Oct 01, 2010 at 03:06:12PM +0100, Stefano Stabellini wrote:
>>> On Thu, 30 Sep 2010, Christian Zoffoli wrote:
>>>> Il 29/09/2010 11:10, Stefano Stabellini ha scritto:
>>>> [cut]
>>>>> Yes, you are right.
>>>>> A little while back I backported the whole series to 2.6.32 and the
>>>>> result was included the Jeremy's pvops main branch, but I haven't kept
>>>>> it completely up to date.
>>>>> The new changes that are only in the 2.6.35-rc5-pvhvm-v7 branch regards
>>>>> PV spinlocks, the balloon driver and the PV console.
>>>> that's a good news but in my experience the pv_ops kernel is not as
>>>> stable as the suse xenified kernel
>>>> ...imho the best would be to have clean patches for a 3.6.32.x vanilla
>>>> kernel ...so we can do packages close to the official ones ...with only
>>>> this great addition.
>>>>
>>>  
>>> I have just done a backport to 2.6.32 of the whole series, branch name
>>> 2.6.32-pvhvm; I'll try to keep it up to date.
>>> It should be easy to rebase the series on the latest 2.6.32 stable
>>> kernel or to apply CVE fixes on top of this branch.
>>>
>> 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.

The hvc console patches clash fairly badly with the dom0 ones; nothing
fundamental, but fiddly.

The balloon.c changes clash with the largepage ballooning stuff.

    J

  reply	other threads:[~2010-10-01 22:19 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 [this message]
2010-10-04 17:06                 ` Stefano Stabellini
2010-10-04 17:08                   ` Stefano Stabellini
2010-10-04 19:23                     ` Jeremy Fitzhardinge
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=4CA65E78.1000400@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.