[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-devel] linux-2.6.27-xen.hg
- To: Jan Beulich <jbeulich@xxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
- From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
- Date: Mon, 5 Jan 2009 13:13:54 -0800 (PST)
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Mon, 05 Jan 2009 13:14:23 -0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=R/OlM5z8EeJiZODuZU4PQR7mv6dB9r5aVFYZPccCoL5uEMxebzEkgzJzR5Vkkm+alBpPyMQXCzQa3G6M1Fo0K6jeI4eeZyXE6CDiLIRC3rXt2HdtouaMtv1NJ1PoPGUhjp0rFfYVXEaYXE5DS23v/ES0FDyDDC/BRn17j0P1f5Q=;
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
As far as i understand it's Novell's patched tree.
Suse performed Xen forward porting to 2.6.27.
Canonical gave up on this task and picked up KVM, obviously
unable to compete with Xen Hypervisor on Server's platform.
If i am wrong about that , please advise.
--- On Mon, 1/5/09, Dan Magenheimer <dan.magenheimer@xxxxxxxxxx> wrote:
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: RE: [Xen-devel] linux-2.6.27-xen.hg
To: "Jan Beulich" <jbeulich@xxxxxxxxxx>, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Monday, January 5, 2009, 3:25 PM
Hmmm... I had thought that the linux-2.6.27-xen.hg tree was
essentially an hg equivalent of upstream
kernel.org 2.6.27,
but it appears there are more differences (and not just bug
fixes).
Can someone explain the difference and the purpose of
the linux-2.6.27-xen.hg tree (if other than to have a private
non-kernel.org copy for xen-related development that
hasn't yet made it upstream)? Why, for example, are
the hypercall source files in a different place?
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
