From mboxrd@z Thu Jan  1 00:00:00 1970
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: HVMlite ABI specification DRAFT A
Date: Thu, 4 Feb 2016 19:51:25 +0100
Message-ID: <20160204185125.GA3377@var.home>
References: <56B38EDE.5090700@citrix.com>
 <56B39A8A.6090001@oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta5.messagelabs.com ([195.245.231.135])
	by lists.xen.org with esmtp (Exim 4.72) (envelope-from
	<SRS0=ihCT=OD=ens-lyon.org=samuel.thibault@bounce.ens-lyon.org>)
	id 1aRP06-0000Rz-PE
	for xen-devel@lists.xenproject.org; Thu, 04 Feb 2016 18:51:30 +0000
Content-Disposition: inline
In-Reply-To: <56B39A8A.6090001@oracle.com>
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: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, Andrew Cooper <andrew.cooper3@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>, Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.com>
List-Id: xen-devel@lists.xenproject.org

Boris Ostrovsky, on Thu 04 Feb 2016 13:38:02 -0500, wrote:
> On 02/04/2016 12:48 PM, Roger Pau Monn=E9 wrote:
> >The format of the boot start info structure is the following (pointed to
> >be %ebx):
> >
> >     struct hvm_start_info {
> >     #define HVM_START_MAGIC_VALUE 0x336ec578
> >         uint32_t magic;             /* Contains the magic value 0x336ec=
578       */
> >                                     /* ("xEn3" with the 0x80 bit of the=
 "E" set).*/
> >         uint32_t flags;             /* SIF_xxx flags.                  =
          */
> >         uint32_t cmdline_paddr;     /* Physical address of the command =
line.     */
> >         uint32_t nr_modules;        /* Number of modules passed to the =
kernel.   */
> >         uint32_t modlist_paddr;     /* Physical address of an array of =
          */
> >                                     /* hvm_modlist_entry.              =
          */
> >     };
> >
> >     struct hvm_modlist_entry {
> >         uint32_t paddr;             /* Physical address of the module. =
          */
> >         uint32_t size;              /* Size of the module in bytes.    =
          */
> >     };
> =

> If there is more than one module, how is the guest expected to sort out
> which module is what?

+1
We need that to pass parameters to gnumach modules.

Samuel