From: Gerd Hoffmann <kraxel@redhat.com>
To: Andrew Lyon <andrew.lyon@gmail.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Xen dom0 Kernel Patches
Date: Wed, 03 Jun 2009 23:24:43 +0200 [thread overview]
Message-ID: <4A26EA1B.1090805@redhat.com> (raw)
In-Reply-To: <f4527be0906031149gebed073l519799116540eb7c@mail.gmail.com>
Hi,
> My question is this, given that the openSUSE patches seem to work
> quite well would it really be so much work to at least update the
> Xensource kernel to 2.6.29 or .30? I believe openSUSE use a semi
> automated process for forward porting but however they do it the
> results are quite good,
Jan Beulich does it. I doubt it is automated process. There are tools
like quilt though which help maintaining and rebasing patch queues. Now
with the x86 merge being mostly done rebasing the patches to a newer
kernel is probably easier again.
> It seems to me that a huge amount of effort is being duplicated in the
> forward porting when a combined effort is bound to produce better
> results, if multiple distro's can find the resources to do it surely
> working together with Xensource would be less effort for everybody.
There is no duplicated effort. Everybody with xen patches against
recent kernels just uses the opensuse patches.
> I understand that the kernel is a moving target and 2.6.29 will soon
> be out of date, but I don't think that justifies simply not providing
> a newer one because pv_ops will be in mainline "any time soon", it
> really feel that it is going to take a long time before that happens,
> if at all.
Even with the bits not being merged into mainline you can still pull
jeremies git tree to get a pv_ops based kernel with dom0 support.
cheers,
Gerd
next prev parent reply other threads:[~2009-06-03 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 18:49 Xen dom0 Kernel Patches Andrew Lyon
2009-06-03 19:35 ` Pasi Kärkkäinen
2009-06-03 20:36 ` Andrew Lyon
2009-06-04 15:08 ` Ian Pratt
2009-06-03 21:24 ` Gerd Hoffmann [this message]
2009-06-03 21:31 ` Keir Fraser
2009-06-04 3:43 ` Tim Post
2009-06-04 6:59 ` Gerd Hoffmann
2009-06-04 14:36 ` Tim Post
-- strict thread matches above, loose matches on Subject: below --
2009-06-04 17:55 Boris Derzhavets
2009-06-04 18:18 ` Pasi Kärkkäinen
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=4A26EA1B.1090805@redhat.com \
--to=kraxel@redhat.com \
--cc=andrew.lyon@gmail.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.