From: Blue Swirl <blauwirbel@gmail.com>
To: malc <av1474@comtv.ru>
Cc: Andreas Niederl <andreas.niederl@iaik.tugraz.at>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] Add TPM 1.2 host device passthrough interface
Date: Thu, 26 Aug 2010 17:22:04 +0000 [thread overview]
Message-ID: <AANLkTi=LCYcca2QzUDA631gGHSH3FOreHDRmU6C3mrRL@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1008260041320.1964@linmac>
On Wed, Aug 25, 2010 at 8:46 PM, malc <av1474@comtv.ru> wrote:
> On Wed, 25 Aug 2010, Blue Swirl wrote:
>
>> On Wed, Aug 25, 2010 at 4:33 PM, Andreas Niederl
>> <andreas.niederl@iaik.tugraz.at> wrote:
>> > This implementation is based on the TPM 1.2 interface for virtualized TPM
>> > devices from the Xen-4.0.0 ioemu-qemu-xen fork.
>> >
>> > A separate thread is used for I/O to the host TPM device because the Linux TPM
>> > driver does not allow for non-blocking I/O.
>> >
>> > Signed-off-by: Andreas Niederl <andreas.niederl@iaik.tugraz.at>
>>
>> In general, please read CODING_STYLE.
>>
>> Ideally, the host and guest devices should be decoupled so that the
>> guest visible device should still be functional without host TPM
>> support.
>>
>> > ---
>
> [..snip..]
>
>> > +static inline uint32_t tpm_get_size_from_buffer(const uint8_t *buffer)
>> > +{
>> > + uint32_t len = (buffer[4] << 8) + buffer[5];
>> > + return len;
>> > +}
>> > +
>> > +static inline uint8_t locality_from_addr(target_phys_addr_t addr)
>> > +{
>> > + return (uint8_t)((addr >> 12) & 0x7);
>> > +}
>> > +
>> > +
>> > +static void die2(int err, const char *what)
>> > +{
>> > + fprintf(stderr, "%s failed: %s\n", what, strerror(err));
>> > + abort();
>> > +}
>> > +
>> > +static void die(const char *what)
>> > +{
>> > + die2(errno, what);
>> > +}
>>
>> There's hw_error() and errx(), no need to reinvent the wheel.
>
> Since it looks as if this code was based on mine, i take issues with
> your analysis.
>
> Firstly hw_error is for hardware errors and does not print message
> corresponding to errno code
Right, the correct function should be error_report().
> and lastly there is no errx[1]
>
> [..snip..]
>
> [1] err(3):
> CONFORMING TO
> These functions are non-standard BSD extensions.
err() and errx() are already used somewhere. But these should be
converted to error_report etc., like other printf based local
functions.
next prev parent reply other threads:[~2010-08-26 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 16:33 [Qemu-devel] [PATCH 1/3] Add TPM 1.2 host device passthrough interface Andreas Niederl
2010-08-25 16:33 ` [Qemu-devel] [PATCH 2/3] Add command line options for TPM interface Andreas Niederl
2010-08-25 19:15 ` Blue Swirl
2010-08-25 16:33 ` [Qemu-devel] [PATCH 3/3] seabios: Add DSDT entry for an emulated TPM 1.2 device Andreas Niederl
2010-08-25 16:46 ` [Qemu-devel] [PATCH 1/3] Add TPM 1.2 host device passthrough interface Anthony Liguori
2010-08-25 19:46 ` Blue Swirl
2010-08-25 20:46 ` malc
2010-08-26 17:22 ` Blue Swirl [this message]
2010-08-26 21:44 ` malc
2010-08-26 21:57 ` Anthony Liguori
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='AANLkTi=LCYcca2QzUDA631gGHSH3FOreHDRmU6C3mrRL@mail.gmail.com' \
--to=blauwirbel@gmail.com \
--cc=andreas.niederl@iaik.tugraz.at \
--cc=av1474@comtv.ru \
--cc=qemu-devel@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).