From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Stefan Berger <stefanb@linux.ibm.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Thomas Huth <thuth@redhat.com>
Cc: peter.maydell@linaro.org, Eric Auger <eric.auger@redhat.com>,
Joelle van Dyne <j@getutm.app>
Subject: Re: [PULL v1 1/1] hw/tpm: TIS on sysbus: Remove unsupport ppi command line option
Date: Fri, 14 Jul 2023 19:58:51 +0200 [thread overview]
Message-ID: <6697efa4-c76c-deaa-178f-1d7fccf08b04@linaro.org> (raw)
In-Reply-To: <20230714154101.184057-2-stefanb@linux.ibm.com>
Hi Stefan,
On 14/7/23 17:41, Stefan Berger 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>
> Reviewed-by: Eric Auger <eric.auger@redhat.com>
> Message-id: 20230713171955.149236-1-stefanb@linux.ibm.com
> ---
> hw/tpm/tpm_tis_sysbus.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/hw/tpm/tpm_tis_sysbus.c b/hw/tpm/tpm_tis_sysbus.c
> index 45e63efd63..6724b3d4f6 100644
> --- a/hw/tpm/tpm_tis_sysbus.c
> +++ b/hw/tpm/tpm_tis_sysbus.c
> @@ -93,7 +93,6 @@ static void tpm_tis_sysbus_reset(DeviceState *dev)
> static Property tpm_tis_sysbus_properties[] = {
> DEFINE_PROP_UINT32("irq", TPMStateSysBus, state.irq_num, TPM_TIS_IRQ),
> DEFINE_PROP_TPMBE("tpmdev", TPMStateSysBus, state.be_driver),
> - DEFINE_PROP_BOOL("ppi", TPMStateSysBus, state.ppi_enabled, false),
Since properties are user-facing, shouldn't we deprecate their
removal? I'm not sure so I ask :) Otherwise we could register
the property with object_class_property_add_bool() and have
the setter display a warning. Anyhow I suppose now setting
"ppi" triggers some error, which is better than a abort.
> DEFINE_PROP_END_OF_LIST(),
> };
>
next prev parent reply other threads:[~2023-07-14 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 15:40 [PULL v1 0/1] Merge tpm 2023/07/14 v1 Stefan Berger
2023-07-14 15:41 ` [PULL v1 1/1] hw/tpm: TIS on sysbus: Remove unsupport ppi command line option Stefan Berger
2023-07-14 17:58 ` Philippe Mathieu-Daudé [this message]
2023-07-14 18:04 ` Stefan Berger
2023-07-16 16:48 ` [PULL v1 0/1] Merge tpm 2023/07/14 v1 Richard Henderson
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=6697efa4-c76c-deaa-178f-1d7fccf08b04@linaro.org \
--to=philmd@linaro.org \
--cc=armbru@redhat.com \
--cc=eric.auger@redhat.com \
--cc=j@getutm.app \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.ibm.com \
--cc=thuth@redhat.com \
/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).