xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.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 Monné" <roger.pau@citrix.com>
Subject: Re: HVMlite ABI specification DRAFT A
Date: Thu, 4 Feb 2016 19:51:25 +0100	[thread overview]
Message-ID: <20160204185125.GA3377@var.home> (raw)
In-Reply-To: <56B39A8A.6090001@oracle.com>

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

  reply	other threads:[~2016-02-04 18:51 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 17:48 HVMlite ABI specification DRAFT A Roger Pau Monné
2016-02-04 18:22 ` Andrew Cooper
2016-02-04 19:33   ` Roger Pau Monné
2016-02-04 20:24     ` Boris Ostrovsky
2016-02-05 14:44     ` Ian Campbell
2016-02-05 14:46       ` Roger Pau Monné
2016-02-05  9:12   ` Jan Beulich
2016-02-05  9:50     ` Roger Pau Monné
2016-02-05 10:40       ` Jan Beulich
2016-02-05 11:04         ` Andrew Cooper
2016-02-05 11:07           ` Jan Beulich
2016-02-05 11:30         ` Roger Pau Monné
2016-02-05 11:45           ` Jan Beulich
2016-02-05 11:50             ` Roger Pau Monné
2016-02-05 13:22               ` Jan Beulich
2016-02-05 14:27                 ` Roger Pau Monné
2016-02-05 14:31                   ` Jan Beulich
2016-02-05 15:00                     ` Roger Pau Monné
2016-02-05 15:29                       ` Jan Beulich
2016-02-05 15:35                         ` Roger Pau Monné
2016-02-04 18:38 ` Boris Ostrovsky
2016-02-04 18:51   ` Samuel Thibault [this message]
2016-02-04 19:21     ` Roger Pau Monné
2016-02-04 20:17       ` Boris Ostrovsky
2016-02-04 20:29         ` Konrad Rzeszutek Wilk
2016-02-04 20:37           ` Andrew Cooper
2016-02-05  8:23         ` Roger Pau Monné
2016-02-04 22:23       ` Samuel Thibault
2016-02-04 19:09 ` Samuel Thibault
2016-02-04 19:18   ` Boris Ostrovsky
2016-02-04 22:21     ` Samuel Thibault
2016-02-04 22:25       ` Andrew Cooper
2016-02-04 22:41         ` Samuel Thibault
2016-02-05 10:20 ` Ian Campbell
2016-02-05 16:01 ` Tim Deegan
2016-02-05 16:13   ` Roger Pau Monné
2016-02-05 17:14   ` Andrew Cooper
2016-02-05 18:05     ` Tim Deegan
2016-02-05 18:44       ` Andrew Cooper
2016-02-08 12:10     ` Stefano Stabellini
2016-02-08 13:21       ` David Vrabel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160204185125.GA3377@var.home \
    --to=samuel.thibault@ens-lyon.org \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=paul.durrant@citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).