From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: "Xu, Quan" <quan.xu@intel.com>, Ian Campbell <ian.campbell@citrix.com>
Cc: "kevin@koconnor.net" <kevin@koconnor.net>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH] SeaBios/vTPM: Enable Xen stubdom vTPM for HVM virtual machine
Date: Fri, 20 Mar 2015 08:00:47 -0400 [thread overview]
Message-ID: <550C0BEF.3000409@linux.vnet.ibm.com> (raw)
In-Reply-To: <945CA011AD5F084CBEA3E851C0AB28890E8C5EE4@SHSMSX101.ccr.corp.intel.com>
On 03/19/2015 09:35 PM, Xu, Quan wrote:
>
>> -----Original Message-----
>> From: Ian Campbell [mailto:ian.campbell@citrix.com]
>> Sent: Thursday, March 19, 2015 8:57 PM
>> To: Xu, Quan
>> Cc: kevin@koconnor.net; stefanb@linux.vnet.ibm.com; xen-devel@lists.xen.org;
>> qemu-devel@nongnu.org; stefano.stabellini@eu.citrix.com
>> Subject: Re: [Xen-devel] [PATCH] SeaBios/vTPM: Enable Xen stubdom vTPM for
>> HVM virtual machine
>>
>> On Tue, 2015-03-10 at 08:16 -0400, Quan Xu wrote:
>>> @@ -151,6 +152,8 @@ device_hardware_setup(void)
>>> esp_scsi_setup();
>>> megasas_setup();
>>> pvscsi_setup();
>>> + if (runningOnXen())
>>> + vtpm4hvm_setup();
>> Is there anything which is actually Xen specific about the driver in tpm.[ch]?
>> Would it be better to just probe for it, perhaps gates by a Kconfig option which
>> enables TPM support.
>>
>> And following that train of thought I think you could reasonable drop "4hvm"
>> from the name. And possibly even the leading "v", since I suppose seabios
>> shouldn't really care if the tpm is emulated or real so long as it looks like a real
>> tpm.
>>
>> Ian.
> Thanks for your review. Make sense.
>
> Quan
From previously posted patches you should be able to take 1/8 with the
driver:
http://www.seabios.org/pipermail/seabios/2014-July/008179.html
2/8 added ACPI support, but this is not necessary; it contained the
probing parts, which could be merged into 1.
3/8 was doing TPM initialization, so that should be recyclable as well:
http://www.seabios.org/pipermail/seabios/2014-July/008180.html
I have a set of patches that removes the ACPI part in 2/8, though didn't
post it.
Stefan
next prev parent reply other threads:[~2015-03-20 12:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 12:16 [Qemu-devel] [PATCH] SeaBios/vTPM: Enable Xen stubdom vTPM for HVM virtual machine Quan Xu
2015-03-10 12:16 ` Quan Xu
2015-03-19 12:56 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2015-03-20 1:35 ` Xu, Quan
2015-03-20 12:00 ` Stefan Berger [this message]
2015-03-20 11:43 ` Stefan Berger
2015-03-23 1:47 ` Xu, Quan
2015-03-23 10:57 ` Stefan Berger
2015-03-23 12:03 ` Xu, Quan
2015-03-23 20:00 ` Stefan Berger
2015-03-24 2:20 ` Xu, Quan
2015-03-24 15:21 ` Stefan Berger
2015-03-25 1:51 ` Xu, Quan
2015-03-11 19:49 ` [Qemu-devel] " Kevin O'Connor
2015-03-12 2:54 ` Xu, Quan
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=550C0BEF.3000409@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=ian.campbell@citrix.com \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=quan.xu@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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).