xen-devel
[Xen-devel] Re: Xen is a feature
To: |
David Miller <davem@xxxxxxxxxxxxx> |
Subject: |
[Xen-devel] Re: Xen is a feature |
From: |
George Dunlap <george.dunlap@xxxxxxxxxxxxx> |
Date: |
Fri, 29 May 2009 13:01:18 +0100 |
Cc: |
"npiggin@xxxxxxx" <npiggin@xxxxxxx>, "jeremy@xxxxxxxx" <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "wimcoekaerts@xxxxxxxxxxxx" <wimcoekaerts@xxxxxxxxxxxx>, Stephen Spector <stephen.spector@xxxxxxxxxx>, ksrinivasan <ksrinivasan@xxxxxxxxxx>, "kurt.hackel@xxxxxxxxxx" <kurt.hackel@xxxxxxxxxx>, "x86@xxxxxxxxxx" <x86@xxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>, Ian Pratt <Ian.Pratt@xxxxxxxxxxxxx>, "avi@xxxxxxxxxx" <avi@xxxxxxxxxx>, "EAnderson@xxxxxxxxxx" <EAnderson@xxxxxxxxxx>, "jens.axboe@xxxxxxxxxx" <jens.axboe@xxxxxxxxxx>, "mingo@xxxxxxx" <mingo@xxxxxxx>, "torvalds@xxxxxxxxxxxxxxxxxxxx" <torvalds@xxxxxxxxxxxxxxxxxxxx>, "gregkh@xxxxxxx" <gregkh@xxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxxx> |
Delivery-date: |
Fri, 29 May 2009 08:53:23 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<20090528.210559.137121893.davem@xxxxxxxxxxxxx> |
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
List-post: |
<mailto:xen-devel@lists.xensource.com> |
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
References: |
<162f4c90-6431-4a2a-b337-6d7451d7b11e@default> <20090528001350.GD26820@xxxxxxx> <4A1F302E.8030501@xxxxxxxx> <20090528.210559.137121893.davem@xxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Thunderbird 2.0.0.21 (X11/20090409) |
David Miller wrote:
I don't see Ingo's comments, whether I agree with them or not, as
an implication of Xen being niche. Rather I see his comments as
an opposition to how Xen is implemented.
It's in his definition of "improving Linux". Jeremy is saying that
allowing Linux to run as dom0 *is* improving Linux. The lack of dom0
support is at this moment making life more difficult for a huge number
of Linux users who use Xen, including Mozilla, Debian, and Amazon.
Adding dom0 support would make Linux even more useful to a wide variety
of people not using Xen at the moment.
Saying that dom0 support is "not about improving Linux" completely
ignores the cost people are paying right now, and the benefits people
could have. That (if I understand him) what Jeremy meant by saying it
was treating it as if it was some kind of "niche usage, with barely more
users than Voyager", and "being a pure drain".
I don't see any animosity at all in what Ingo has said.
The last few paragraphs of the e-mail weren't about that particular
argument, but about the sum of the interaction with Ingo over dom0
support for the last 6 months. If you read the various threads, it's
pretty clear that Ingo is resistant to accepting dom0 changes, for
whatever reason, and has been looking for reasons not to include it.
If we take him at his word, that the root issue is that he fundamentally
dislikes the design choice of running Linux-as-hypervisor-component,
then we have a difference of opinion and we're just going to have to
agree to disagree. But there are reasons to include it anyway,
including benefits to existing Xen users and potential Xen users (who
have decided not to use KVM for whatever reason), and the idea of
survival-of-the-fittest: Xen and KVM have made different design choices,
let's let them both grow and see which one thrives. If KVM's design is
unilaterally superior, eventually Xen will die off. But I suspect that
there's significant demand in the OSS virtualization ecology for both
approaches, and the world will be the worse for dom0 support being
out-of-tree.
In any case, making unreasonable or inconsistent technical objections,
when the root issue is is actually something else, is a waste of time
and energy for everyone involved.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: Distro kernel and 'virtualization server' vs. 'server that sometimes runs virtual instances' rant (was: Re: [Xen-devel] Re: [GIT PULL] Xen APIC hooks (with io_apic_ops)), (continued)
- [Xen-devel] Re: Distro kernel and 'virtualization server' vs. 'server that sometimes runs virtual instances' rant, Michael David Crawford
- Re: [Xen-devel] Re: [GIT PULL] Xen APIC hooks (with io_apic_ops), George Dunlap
- [Xen-devel] Xen is a feature, Jeremy Fitzhardinge
- [Xen-devel] Re: Xen is a feature, Greg KH
- [Xen-devel] Re: Xen is a feature, David Miller
- [Xen-devel] Re: Xen is a feature, Jaswinder Singh Rajput
- [Xen-users] Re: Xen is a feature, David Miller
- [Xen-devel] Re: Xen is a feature,
George Dunlap <=
- [Xen-devel] Re: Xen is a feature, Pasi Kärkkäinen
- [Xen-devel] Re: Xen is a feature, Andi Kleen
- Re: [Xen-devel] Re: Xen is a feature, Jeremy Fitzhardinge
- RE: [Xen-devel] Re: Xen is a feature, Nakajima, Jun
- Re: [Xen-devel] Re: Xen is a feature, Jeremy Fitzhardinge
- Re: [Xen-devel] Re: [GIT PULL] Xen APIC hooks (with io_apic_ops), Gerd Hoffmann
- Re: [Xen-devel] Re: [GIT PULL] Xen APIC hooks (with io_apic_ops), George Dunlap
[Xen-devel] Re: [GIT PULL] Xen APIC hooks (with io_apic_ops), Avi Kivity
|
|
|