From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Kinzler <ml-xen-devel@hfp.de>
Subject: design questions: blktap & dom0-kernel/Xen binary
	compatibility
Date: Mon, 04 Feb 2013 18:45:39 +0100
Message-ID: <510FF3C3.9070601@hfp.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

I have two design questions:

a) is there some doc on binary compatibility between dom0-kernels and 
Xen/xen-tools? For example Xen 4.2.1 on my system does not work with 
xenified OpenSuse 12.2 kernel, while it seems to work with vanilla 3.7. 
I am interested in some kind of compatibility matrix having various 
kernels (pvops0, xenified, with versions) on one axis and Xen releases 
on the other axis. Also having some info about reasons for 
breakage-by-design would be helpful.

b) is there some doc/info on what is going on with blktap[1,2,3]? I am 
specifically interested in underlying (design) questions, for example 
why blktap was not migrated to vanilla kernel 3.x?

Regards Andreas