From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>, qemu-devel@nongnu.org
Cc: marcandre.lureau@redhat.com, qemu-ppc@nongnu.org, lo1@us.ibm.com,
James.Bottomley@HansenPartnership.com,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH 1/2] tpm_spapr: Support TPM for ppc64 using CRQ based interface
Date: Fri, 8 Dec 2017 16:17:39 -0500 [thread overview]
Message-ID: <242276bf-f147-f848-a2b7-777f646df367@linux.vnet.ibm.com> (raw)
In-Reply-To: <157332b2-bfc2-a99d-0bf1-577a1dda775e@kaod.org>
On 12/08/2017 01:17 PM, Cédric Le Goater wrote:
> On 12/06/2017 12:53 PM, Stefan Berger wrote:
>> On 12/06/2017 02:26 AM, Cédric Le Goater wrote:
>>> Hello Stefan,
>>>
>>> Some comments below. How do we populate the device tree ?
>> Patched SLOF.
>
> Ah. Isn't that a problem ? I thought QEMU was in charge of populating
> the device tree.
I haven't seen this for ppc64 but it's true for ACPI on x86.
> You should send the full patchset rebased on QEMU's head or
> on David's 2.12 branch else this patch won't apply or compile.
I am maintaining a tpm-next branch for 2.12 that includes the patches
that this builds on top of.
Stefan
next prev parent reply other threads:[~2017-12-08 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 20:35 [Qemu-devel] [PATCH 0/2] Add vTPM emulator supportfor ppc64 platform Stefan Berger
2017-12-05 20:35 ` [Qemu-devel] [PATCH 1/2] tpm_spapr: Support TPM for ppc64 using CRQ based interface Stefan Berger
2017-12-06 7:26 ` Cédric Le Goater
2017-12-06 11:53 ` Stefan Berger
2017-12-08 18:17 ` Cédric Le Goater
2017-12-08 21:17 ` Stefan Berger [this message]
2017-12-05 20:35 ` [Qemu-devel] [PATCH 2/2] tpm_spapr: Support suspend and resume Stefan Berger
2017-12-05 20:45 ` [Qemu-devel] [PATCH 0/2] Add vTPM emulator supportfor ppc64 platform 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=242276bf-f147-f848-a2b7-777f646df367@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=lo1@us.ibm.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).