[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090603024311.GZ31943@mit.edu>
Date: Tue, 2 Jun 2009 22:43:11 -0400
From: Theodore Tso <tytso@....edu>
To: Dan Magenheimer <dan.magenheimer@...cle.com>
Cc: Ingo Molnar <mingo@...e.hu>, Steven Rostedt <rostedt@...dmis.org>,
George Dunlap <george.dunlap@...citrix.com>,
David Miller <davem@...emloft.net>, jeremy@...p.org,
avi@...hat.com, xen-devel@...ts.xensource.com, x86@...nel.org,
linux-kernel@...r.kernel.org,
Keir Fraser <Keir.Fraser@...citrix.com>,
torvalds@...ux-foundation.org, gregkh@...e.de,
kurt.hackel@...cle.com, Ian Pratt <Ian.Pratt@...citrix.com>,
xen-users@...ts.xensource.com,
ksrinivasan <ksrinivasan@...ell.com>, EAnderson@...ell.com,
wimcoekaerts@...mekes.net,
Stephen Spector <stephen.spector@...rix.com>,
jens.axboe@...cle.com, npiggin@...e.de
Subject: Re: Merge Xen (the hypervisor) into Linux
On Tue, Jun 02, 2009 at 05:00:21PM -0700, Dan Magenheimer wrote:
> That sound you heard was 10000 xen-users@...ts.xensource.com
> all having heart attacks at once.
>
> Need I say more.
So maybe I'm stupid, but why would they be having heart attacks?
It seems like a decent solutoin to me. What's being proposed would
make the dom0/hypervisor interface an internal once, always subject to
change. What's wrong with that? Presumably the domU/hypervisor
interface would have to be remain stable, but why is the
dom0/hypervisor interface have to be sacred and unchanging? I don't
understand the concern.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists