From: Stefan Berger <stefanb@linux.ibm.com>
To: eric.auger@redhat.com, Joelle van Dyne <j@getutm.app>
Cc: qemu-devel@nongnu.org, marcandre.lureau@redhat.com,
ard.biesheuvel@linaro.org
Subject: Re: [PATCH] hw/tpm: TIS on sysbus: Remove unsupport ppi command line option
Date: Fri, 14 Jul 2023 10:19:12 -0400 [thread overview]
Message-ID: <6db33e13-523f-8b03-f668-40fbc7f03729@linux.ibm.com> (raw)
In-Reply-To: <d1a121d2-b0ec-7928-ff21-ce5389cf7749@redhat.com>
On 7/14/23 09:51, Eric Auger wrote:
> Hi Stefan,
> On 7/14/23 13:51, Stefan Berger wrote:
>>
>>
>> On 7/14/23 02:07, Joelle van Dyne wrote:
>>> On Thu, Jul 13, 2023 at 10:20 AM Stefan Berger
>>> <stefanb@linux.ibm.com> wrote:
>>>>
>>>> The ppi command line option for the TIS device on sysbus never worked
>>>> and caused an immediate segfault. Remove support for it since it also
>>>> needs support in the firmware and needs testing inside the VM.
>>>>
>>>> Reproducer with the ppi=on option passed:
>>>>
>>>> qemu-system-aarch64 \
>>>> -machine virt,gic-version=3 \
>>>> -m 4G \
>>>> -nographic -no-acpi \
>>>> -chardev socket,id=chrtpm,path=/tmp/mytpm1/swtpm-sock \
>>>> -tpmdev emulator,id=tpm0,chardev=chrtpm \
>>>> -device tpm-tis-device,tpmdev=tpm0,ppi=on
>>>> [...]
>>>> Segmentation fault (core dumped)
>>>>
>>>> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
>>>
>>> Do you need to add a VMSTATE_UNUSED_TEST in case a future QEMU version
>>> introduces a new field in the same position which will cause an issue
>>> when restoring from an older version?
>>
>> Hm, you got a point there. We will have to error-out in case someone
>> sets ppi=on instead since the expectation that PPI would work is
>> simply not there. v2 coming soon.
> as Joelle pointed it out ppi_enabled is not part of
> vmstate_tpm_tis_sysbus fields. And since it has never worked I suspect
> we cannot have any existing VM enabling it. So I don't get the issue
> with this 1st version?
You are right. I repeated my test with restoring state of a VM taken before the removal of this field and it restored it. So that other patch is good and I am withdrawing this patch here.
Stefan
>
> Thanks
>
> Eric
>>
>> Stefan
>>
>
next prev parent reply other threads:[~2023-07-14 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 17:19 [PATCH] hw/tpm: TIS on sysbus: Remove unsupport ppi command line option Stefan Berger
2023-07-13 17:38 ` Eric Auger
2023-07-14 6:07 ` Joelle van Dyne
2023-07-14 6:12 ` Joelle van Dyne
2023-07-14 11:51 ` Stefan Berger
2023-07-14 13:51 ` Eric Auger
2023-07-14 14:19 ` Stefan Berger [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 11:53 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=6db33e13-523f-8b03-f668-40fbc7f03729@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=eric.auger@redhat.com \
--cc=j@getutm.app \
--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).