Re: [Xen-devel] kexec design issues

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Mon, 2009-03-16 at 09:54 -0400, Jan Beulich wrote:
> 
> But I view the issue as broader: Any other OS wanting to make use of
> the kexec hypercall interface would be required to match the Linux
> implementation in  various respects. This is what I consider a design
> flaw, which makes me think that the current kexec sub-hypercalls
> should be urgently deprecated in favor of a clean interface.

I agree with this, the existing interface has always irked me a little
due it its very close ties to the specifics of the Linux 2.6.18 kexec
interface. I've never been entirely sure what a better interface would
look like, but something like you suggest later seems to make sense:

On Tue, 2009-03-17 at 04:09 -0400, Jan Beulich wrote:
> Something like changing page_list to a pointer (and add a count), and
> having an extra attribute (or operation code if you will) field for
> each page that tells what to do with it (i.e. as a replacement for the
> pa/va pairs: indicating that a certain entry is to represent the
> virtual address for a machine address specified by another entry).

Ian.


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