From: "Hon Ching (Vicky) Lo" <honclo@linux.vnet.ibm.com>
To: Ashley Lai <ashley@ashleylai.com>
Cc: tpmdd-devel@lists.sourceforge.net,
Peter Huewe <PeterHuewe@gmx.de>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Vicky Lo <honclo2014@gmail.com>,
linux-kernel@vger.kernel.org,
Joy Latten <jmlatten@linux.vnet.ibm.com>
Subject: Re: [PATCH 3/3] vTPM: support little endian guests
Date: Fri, 08 May 2015 19:10:24 -0400 [thread overview]
Message-ID: <1431126624.25419.11.camel@vtpm2014.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1505081331540.8786@ant>
Thanks Ashley!
> > The event log in ppc64 arch is always in big endian format. PowerPC
> > supports both little endian and big endian guests. This patch converts
> > the event log entries to guest format.
>
> I'm a little confused here. If this patch is to convert the event log
> entries why are we convert in the conditional statements? One example
> below:
>
> + if (((convert_to_host_format(event->event_type) == 0) &&
> + (convert_to_host_format(event->event_size) == 0))
> + ||
> + ((v + sizeof(struct tcpa_event) +
> + convert_to_host_format(event->event_size)) > limit))
>
> >
> > We defined a macro to convert to guest format. In addition,
> > tpm_binary_bios_measurements_show() is modified to parse the event
> > and print each field individually.
>
We do not convert the whole event entry. Instead, we're converting only
what's necessary such as pcr_index, event_type and event_size. pcr_value
and event_data are of type u8. They do not need LE conversion.
> It's nice to have human readable format but it may break existing tools
> that parse or understand the machine readable format. Any comments on
> this anyone?
I got comments on the format, so I tried to make that conditional
statement all in one line, but the 'Lindent' tool puts the lines back to
the above format..
Regards,
Vicky
next prev parent reply other threads:[~2015-05-08 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 0:51 [PATCH 0/3] additional little endian support Hon Ching(Vicky) Lo
2015-05-06 0:51 ` [PATCH 1/3] vTPM: fixed the limit checking Hon Ching(Vicky) Lo
2015-05-11 13:02 ` [tpmdd-devel] " Stefan Berger
2015-05-12 21:19 ` Joy M. Latten
2015-05-06 0:51 ` [PATCH 2/3] TPM: remove unnecessary little endian conversion Hon Ching(Vicky) Lo
2015-05-06 0:51 ` [PATCH 3/3] vTPM: support little endian guests Hon Ching(Vicky) Lo
2015-05-08 22:31 ` Ashley Lai
2015-05-08 23:10 ` Hon Ching (Vicky) Lo [this message]
2015-05-11 22:07 ` Joy M. Latten
2015-05-19 21:08 ` Ashley Lai
2015-05-19 21:18 ` Ashley Lai
2015-05-20 21:23 ` Hon Ching (Vicky) Lo
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=1431126624.25419.11.camel@vtpm2014.ibm.com \
--to=honclo@linux.vnet.ibm.com \
--cc=PeterHuewe@gmx.de \
--cc=ashley@ashleylai.com \
--cc=honclo2014@gmail.com \
--cc=jmlatten@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=zohar@linux.vnet.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
Powered by JetHome