From: Auger Eric <eric.auger@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Laszlo Ersek" <lersek@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Eric Auger" <eric.auger.pro@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
ardb@kernel.org, "Stefan Berger" <stefanb@linux.ibm.com>
Subject: Re: [RFC 1/2] tpm: Let the TPM TIS device be usable on ARM
Date: Tue, 11 Feb 2020 14:21:53 +0100 [thread overview]
Message-ID: <33a8885f-8367-b37a-a18b-564fa73f0504@redhat.com> (raw)
In-Reply-To: <CAFEAcA_TJ5gDMRNK=O-iaqksYL_aQFu7repo7wKi7pGb-A9cYQ@mail.gmail.com>
Hi Peter,
On 2/11/20 11:56 AM, Peter Maydell wrote:
> On Tue, 11 Feb 2020 at 08:35, Auger Eric <eric.auger@redhat.com> wrote:
>>
>> Hi Philippe,
>>
>> On 2/11/20 9:25 AM, Philippe Mathieu-Daudé wrote:
>>> You don't need much to remove the RFC tag:
>>>
>>> - rename TYPE_TPM_TIS as TYPE_TPM_TIS_ISA
>>> - rename TPMState as TPMCommonState, add an abstract TYPE_TPM_TIS
>>> parent, let TYPE_TPM_TIS_ISA be a child
>>> - add TYPE_TPM_TIS_SYSBUS also child.
>> Yes I tried my luck without too much hopes ;-)
>
> There should be a few existing examples in the tree
> of devices that we provide in a sysbus and also
> an isa or pci flavour, that you can use as templates
> for how to structure the device.
Yes I found some. Thank you.
Eric
>
> -- PMM
>
next prev parent reply other threads:[~2020-02-11 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 13:15 [RFC 0/2] vTPM for aarch64 Eric Auger
2020-02-10 13:15 ` [RFC 1/2] tpm: Let the TPM TIS device be usable on ARM Eric Auger
2020-02-11 8:25 ` Philippe Mathieu-Daudé
2020-02-11 8:34 ` Auger Eric
2020-02-11 10:56 ` Peter Maydell
2020-02-11 13:21 ` Auger Eric [this message]
2020-02-11 14:30 ` Stefan Berger
2020-02-10 13:15 ` [RFC 2/2] hw/arm/virt: vTPM support Eric Auger
2020-02-10 13:21 ` Philippe Mathieu-Daudé
2020-02-10 13:44 ` [RFC 0/2] vTPM for aarch64 no-reply
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=33a8885f-8367-b37a-a18b-564fa73f0504@redhat.com \
--to=eric.auger@redhat.com \
--cc=ardb@kernel.org \
--cc=eric.auger.pro@gmail.com \
--cc=lersek@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.ibm.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).