WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] unmodified drivers question

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] unmodified drivers question
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Tue, 23 Oct 2007 07:33:33 +0100
Delivery-date: Mon, 22 Oct 2007 23:32:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
In platform-compat.h I find

#if defined(_LINUX_SYSRQ_H) && LINUX_VERSION_CODE > KERNEL_VERSION(2,6,18)
#define handle_sysrq(x,y,z) handle_sysrq(x,y)
#endif

which apparently assumes that non-ported Linux code (in this case
drivers/xen/core/reboot.c) is being compiled for newer kernel versions. If
that is the intended model (which I doubt is a generally workable one), a
second more natural model would need to be implemented by some means
so that building the drivers from an already forward ported tree is possible
(in the given case I'm talking about mentioned file already having the
handle_sysrq() converted to the two argument form).

Thanks for clarification,
Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>