Re: [Xen-devel] HVMlite ABI specification DRAFT A

[Samuel Thibault <samuel.thibault@xxxxxxxxxxxx>]

Boris Ostrovsky, on Thu 04 Feb 2016 13:38:02 -0500, wrote:
> On 02/04/2016 12:48 PM, Roger Pau Monné 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 0x336ec578  
> >      */
> >                                     /* ("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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel