From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: HVMlite ABI specification DRAFT A
Date: Thu, 4 Feb 2016 20:37:56 +0000
Message-ID: <56B3B6A4.9090101@citrix.com>
References: <56B38EDE.5090700@citrix.com> <56B39A8A.6090001@oracle.com>
	<20160204185125.GA3377@var.home> <56B3A4B4.20607@citrix.com>
	<56B3B1D1.7070705@oracle.com>
	<20160204202907.GA17624@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <prvs=83511c2b9=Andrew.Cooper3@citrix.com>)
	id 1aRQfB-0004OH-3x
	for xen-devel@lists.xenproject.org; Thu, 04 Feb 2016 20:38:01 +0000
In-Reply-To: <20160204202907.GA17624@localhost.localdomain>
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: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Tim Deegan <tim@xen.org>, Paul Durrant <paul.durrant@citrix.com>, David Vrabel <david.vrabel@citrix.com>, Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xenproject.org>, Samuel Thibault <samuel.thibault@ens-lyon.org>, =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= <roger.pau@citrix.com>
List-Id: xen-devel@lists.xenproject.org

On 04/02/16 20:29, Konrad Rzeszutek Wilk wrote:
>>>>> If there is more than one module, how is the guest expected to sort out
>>>>> which module is what?
>>> In general I was expecting this would be done by position, or if that's
>>> not enough an additional module (at either position 0 or n) should be
>>> passed to contain that information.
>> Then we should specify it somehow --- e.g. that first module is always the
>> ramdisk.
> Keep in mind that with Linux you can actually append the initrd in the
> vmlinuz file - so you only have "one" file. Hence the first module
> could be optional.

The PV ABI suffers from false assumptions and expectations like this. 
Lets not repeat the same mistakes for HVMLite.

~Andrew