From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Marc - A. Dahlhaus" <mad@wol.de>
Subject: Re: Announcing xen/master: pvops git trees rearranged
Date: Sat, 19 Sep 2009 12:36:41 +0200
Message-ID: <4AB4B439.7020001@wol.de>
References: <4AB431AD.1030205@goop.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4AB431AD.1030205@goop.org>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>, =?UTF-8?B?UGFzaSBLw6Rya2vDpA==?=
List-Id: xen-devel@lists.xenproject.org

Hello Jeremy,

Jeremy Fitzhardinge schrieb:
> Well, my current pvops/dom0 tree is finally (reasonably) stable.  There
> was a fairly nasty bug which ended up corrupting dom0 memory when doing
> IO on behalf of domains, but that is finally fixed.
> 
> In honour of this, I've renamed the rebase/* branches to xen/* (moving
> the old remaining xen/* branches to xen-old/*); xen/master is now the
> preferred branch for fetching current dom0 work.
> 
> The kernel tree is fairly featureful:
> 
>     * basic dom0 support
>     * blkback
>     * netback
>     * ACPI power management
>     * S3 suspend/resume (at least for some people)
>     * microcode update
>     * MSI support
> 
> In other words, it has as much as it ever has.

waited for MSI, will give it a try :o)

> There are a few notable missing features:
> 
>     * blktap2
>     * netchannel2
>     * pci front/back
>     * upstream Linux support
>     * your pet feature
> 
> 
> Full coordinates are:
> 
>     git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git xen/master

Is HEAD already pointing to xen/master or do i have to change branches?

> See http://wiki.xensource.com/xenwiki/XenParavirtOps for general
> directions on configuration, compilation and use.

I think it would be a good idea to add some backtrace and debug related 
options to the CONFIG_ options listed on the wiki page so that one gets 
all the details needed from the testers when some bug shows up (CCd 
Pasi). The NETXEN_NIC option looks unrelated to xen...

> This is definitely a work-in-progress kernel.  I'd appreciate all bug
> *and* success reports so I can get some idea of how many people are
> using this thing, and how often there are problems.  Patches gratefully
> accepted.

Will report something back soon,


Marc