From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4 2/2] tpm: extend TPM TIS with state migration support
Date: Wed, 28 Mar 2018 19:56:22 -0400 [thread overview]
Message-ID: <944288fa-05f1-7ed1-b35d-f7010d28d4c9@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAMxuvaxDVJxH0BwdtdqgvCUpOzaFf_0NsjvjQnceVjeO5dDhbQ@mail.gmail.com>
On 03/28/2018 11:41 AM, Marc-André Lureau wrote:
> Hi
>
> On Thu, Mar 1, 2018 at 8:59 PM, Stefan Berger
> <stefanb@linux.vnet.ibm.com> wrote:
>> +
>> +static const VMStateDescription vmstate_locty = {
>> + .name = "loc",
>> + .version_id = 1,
>> + .minimum_version_id = 0,
>> + .minimum_version_id_old = 0,
> I don't understand the problem there is leaving all the version fields
> to 0, just like CRB.
>
>> + .fields = (VMStateField[]) {
>> + VMSTATE_UINT32(state, TPMLocality),
>> + VMSTATE_UINT32(inte, TPMLocality),
>> + VMSTATE_UINT32(ints, TPMLocality),
>> + VMSTATE_UINT8(access, TPMLocality),
>> + VMSTATE_UINT32(sts, TPMLocality),
>> + VMSTATE_UINT32(iface_id, TPMLocality),
>> + VMSTATE_END_OF_LIST(),
>> + }
>> +};
>> +
>> static const VMStateDescription vmstate_tpm_tis = {
>> .name = "tpm",
>> - .unmigratable = 1,
>> + .version_id = 1,
>> + .minimum_version_id = 0,
>> + .minimum_version_id_old = 0,
> same
>
> If you remove the version fields: Reviewed-by: Marc-André Lureau
> <marcandre.lureau@redhat.com>
This is the error I got when setting .version_id = 0 (on both) and doing
a localhost migration
qemu-system-x86_64: Missing section footer for tpm-tis
qemu-system-x86_64: load of migration failed: Invalid argument
It must have something to do with the nesting invoked by
VMSTATE_STRUCT_ARRAY(loc,...) below.
>
>
>
>> + .pre_save = tpm_tis_pre_save,
>> + .fields = (VMStateField[]) {
>> + VMSTATE_BUFFER(buffer, TPMState),
>> + VMSTATE_UINT16(rw_offset, TPMState),
>> + VMSTATE_UINT8(active_locty, TPMState),
>> + VMSTATE_UINT8(aborting_locty, TPMState),
>> + VMSTATE_UINT8(next_locty, TPMState),
>> +
>> + VMSTATE_STRUCT_ARRAY(loc, TPMState, TPM_TIS_NUM_LOCALITIES, 1,
>> + vmstate_locty, TPMLocality),
>> +
>> + VMSTATE_END_OF_LIST()
>> + }
>> };
>>
>> static Property tpm_tis_properties[] = {
>> --
>> 2.5.5
>>
next prev parent reply other threads:[~2018-03-28 23:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 19:59 [Qemu-devel] [PATCH v4 0/2] tpm: Extend TPM with state migration support Stefan Berger
2018-03-01 19:59 ` [Qemu-devel] [PATCH v4 1/2] tpm: extend TPM emulator " Stefan Berger
2018-03-02 9:26 ` Marc-André Lureau
2018-03-02 10:14 ` Dr. David Alan Gilbert
2018-03-03 2:52 ` Stefan Berger
2018-03-05 12:43 ` Dr. David Alan Gilbert
2018-03-05 13:52 ` Stefan Berger
2018-03-02 13:19 ` Stefan Berger
2018-03-02 15:00 ` Stefan Berger
2018-03-05 20:33 ` Stefan Berger
2018-03-28 15:23 ` Marc-André Lureau
2018-03-01 19:59 ` [Qemu-devel] [PATCH v4 2/2] tpm: extend TPM TIS " Stefan Berger
2018-03-02 9:40 ` Marc-André Lureau
2018-03-28 15:41 ` Marc-André Lureau
2018-03-28 23:56 ` Stefan Berger [this message]
2018-03-29 17:07 ` Marc-André Lureau
2018-04-02 12:15 ` Stefan Berger
2018-03-01 20:23 ` [Qemu-devel] [PATCH v4 0/2] tpm: Extend TPM " Stefan Berger
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=944288fa-05f1-7ed1-b35d-f7010d28d4c9@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.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).