From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
Xen-devel <xen-devel@lists.xen.org>
Cc: Wei Liu <wei.liu2@citrix.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH for-4.6 v2 2/6] docs/libxl: Re-specify XENSTORE_DATA as EMULATOR_XENSTORE_DATA
Date: Tue, 4 Aug 2015 11:16:08 +0100 [thread overview]
Message-ID: <55C090E8.7070808@citrix.com> (raw)
In-Reply-To: <1438682810.31129.86.camel@citrix.com>
On 04/08/15 11:06, Ian Campbell wrote:
>
>>>> +
>>>> + 0 1 2 3 4 5 6 7 octet
>>>> + +------------------------+------------------------+
>>>> + | emulator_id | index |
>>>> + +------------------------+------------------------+
>>>> + | record specific data |
>>>> + ...
>>>> + +-------------------------------------------------+
>>>> +
>>>> +--------------------------------------------------------------------
>>>> +Field Description
>>>> +------------ ---------------------------------------------------
>>>> +emulator_id 0x00000000: Unknown (In the case of a legacy
>>>> stream)
>>>> +
>>>> + 0x00000001: Qemu Traditional
>>>> +
>>>> + 0x00000002: Qemu Upstream
>>>> +
>>>> + 0x00000003 - 0xFFFFFFFF: Reserved for future
>>>> emulators.
>>>> +
>>>> +index Index of this emulator for the domain, if multiple
>>>> + emulators are in use.
>>> This is old wording, but what value does this take if no emulators are
>>> in
>>> use? If the answer is "undefined" then I suppose there is a field
>>> somewhere
>>> else which indicates the number of emulators?
>> If no emulators are in use, the record is not sent in the first place.
> Sorry, I meant no multiple emulators. Which is a complicated way of saying
> one...
>
> I saw in a later patch that this field appears to be zero then, which is
> reasonable and removes the need to treat multiple emulators specially. IOW
> I think you could just remove the second clause above.
Ah yes - I will make that adjustment.
~Andrew
next prev parent reply other threads:[~2015-08-04 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 15:56 [PATCH for-4.6 v2 0/6] Fix libxl TOOLSTACK records for migration v2 Andrew Cooper
2015-08-03 15:56 ` [PATCH for-4.6 v2 1/6] tools/libxl: Make libxl__conversion_helper_abort() safe to use Andrew Cooper
2015-08-04 9:30 ` Ian Campbell
2015-08-03 15:56 ` [PATCH for-4.6 v2 2/6] docs/libxl: Re-specify XENSTORE_DATA as EMULATOR_XENSTORE_DATA Andrew Cooper
2015-08-04 9:40 ` Ian Campbell
2015-08-04 9:42 ` Andrew Cooper
2015-08-04 10:06 ` Ian Campbell
2015-08-04 10:16 ` Andrew Cooper [this message]
2015-08-03 15:56 ` [PATCH for-4.6 v2 3/6] tools/libxl: Save and restore EMULATOR_XENSTORE_DATA content Andrew Cooper
2015-08-04 9:55 ` Ian Campbell
2015-08-03 15:56 ` [PATCH for-4.6 v2 4/6] tools/libxl: Prepare to write multiple records with EMULATOR headers Andrew Cooper
2015-08-04 9:59 ` Ian Campbell
2015-08-03 15:56 ` [PATCH for-4.6 v2 5/6] libxl/save&restore&convert: Switch to new EMULATOR_XENSTORE_DATA records Andrew Cooper
2015-08-03 15:56 ` [PATCH for-4.6 v2 6/6] tools/libxl: Drop all legacy "toolstack" record infrastructure Andrew Cooper
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=55C090E8.7070808@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.