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/
Home Products Support Community News


[Xen-devel] Re: [PATCH]: kexec: framework and i386

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: [PATCH]: kexec: framework and i386
From: Horms <horms@xxxxxxxxxxxx>
Date: Mon, 17 Apr 2006 15:06:19 +0900
Cc: Magnus Damm <magnus@xxxxxxxxxxxxx>
Delivery-date: Tue, 18 Apr 2006 03:14:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060412091228.GA7409@xxxxxxxxxxxx>
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>
References: <20060407074234.GA19846@xxxxxxxxxxxx> <20060412091228.GA7409@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11+cvs20060403
On Wed, Apr 12, 2006 at 06:12:30PM +0900, Horms wrote:
> kexec: framework and i386


>   * This patch was prepared against xen-unstable.hg 9514
>     As of today (9574) two new hypercalls have been added.
>     I rediffed and moved the kexec hypercall to 33. However
>     this exceedes hypercall_NR, which is currently 32. 
>     I tried increasing this, but the dom0 now crashes 
>     in entry.S on init. Even after rebuilding both xen and the kernel
>     completely from scratch after a make distclean. Help!!


I am a bit concerned that this patch is going to start rotting if I
can't at least track the current xen-unstable.hg, or better still get it

I would really appreciate it if someone could take moments to comment on
the hypercall problem. Is adding a new hypercall, as the current patch
does, the best way? If so could someone point me to how to increase the
hypercall table size. If not, is it best to piggyback of the dom0_op
hypercall? Or is there some other prefered option?


Xen-devel mailing list

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