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 23:23:22 +0100
Message-ID: <20160204222322.GD3377@var.home>
References: <56B38EDE.5090700@citrix.com> <56B39A8A.6090001@oracle.com>
	<20160204185125.GA3377@var.home> <56B3A4B4.20607@citrix.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.bemta3.messagelabs.com ([195.245.230.39])
	by lists.xen.org with esmtp (Exim 4.72) (envelope-from
	<SRS0=ihCT=OD=ens-lyon.org=samuel.thibault@bounce.ens-lyon.org>)
	id 1aRSJC-0007Rh-CV
	for xen-devel@lists.xenproject.org; Thu, 04 Feb 2016 22:23:26 +0000
Content-Disposition: inline
In-Reply-To: <56B3A4B4.20607@citrix.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: Roger Pau =?iso-8859-1?Q?Monn=E9?= <roger.pau@citrix.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>, Boris Ostrovsky <boris.ostrovsky@oracle.com>
List-Id: xen-devel@lists.xenproject.org

Roger Pau Monn=E9, on Thu 04 Feb 2016 20:21:24 +0100, wrote:
> > +1
> > We need that to pass parameters to gnumach modules.
> =

> Hm, parameters as in a string that's paired with a module,

That, yes. Just like the kernel command line. One per module.

> I see that multiboot provides a string associated with each module, we
> could do the same IMHO.

That's it.

> Just to be clear that we are on the same page, then the _entry struct
> becomes:
> =

> struct hvm_modlist_entry {
> 	uint32_t paddr;
> 	uint32_t size;
> 	uint32_t cmdline_paddr;
> };
> =

> cmdline_paddr would work the same way as it does in the hvm_start_info
> struct (ie: physical address of a zero-terminated ASCII string).

That looks alright for me.

Samuel