From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: peterhuewe@gmx.de, safford@us.ibm.com,
Marcel Selhorst <tpmdd@selhorst.net>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>,
open list <linux-kernel@vger.kernel.org>,
richard.l.maliszewski@intel.com
Subject: Re: [PATCH] tpm: introduce struct tpm_buf
Date: Wed, 3 Jun 2015 10:11:28 -0600 [thread overview]
Message-ID: <20150603161128.GB12073@obsidianresearch.com> (raw)
In-Reply-To: <20150603122331.GA3542@jsakkine-mobl1>
On Wed, Jun 03, 2015 at 03:23:31PM +0300, Jarkko Sakkinen wrote:
> On Tue, Jun 02, 2015 at 12:13:15PM -0600, Jason Gunthorpe wrote:
> > On Tue, Jun 02, 2015 at 04:04:22PM +0300, Jarkko Sakkinen wrote:
> > > +/* A string buffer type for constructing TPM commands. This is based on the
> > > + * code in security/keys/trusted.h.
> > > + */
> > > +
> > > +#define TPM_BUF_SIZE 512
> > > +
> > > +struct tpm_buf {
> > > + u8 data[TPM_BUF_SIZE];
> > This should be u32 or u64 to guarentee correct alignment for the
> > casting.
>
> Good catch. The functions where this might cause trouble are *_length()
> and *_tag().
>
> In other places misalignment should not cause any regressions since data
> is not directly assigned to the buffer with pointer casting.
>
> I would prefer to fix by changing *_length() and *_tag() to copy the
> value to a local variable and return that. It's a fail safe way and here
> the performance is not an issue.
I would change the type, that is very simple and will improve
performance of the memcpy as well.
It actually isn't a problem for the casts to tpm_input_header - any
structure marked __packed will cause the compiler to assume that the
entire structure is unaligned and code gen accordingly, so the cast
will always work, but on x86 it will be more efficient if the array
is aligned.
Ideally we could change to something like:
__attribute__((packed,aligned(4)))
Instead of __packed which will help the compiler minimize unaligned
load instructions..
Jason
next prev parent reply other threads:[~2015-06-03 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 13:04 Jarkko Sakkinen
2015-06-02 13:18 ` Aw: " Peter Huewe
2015-06-02 14:36 ` Jarkko Sakkinen
2015-06-02 18:13 ` Jason Gunthorpe
2015-06-03 12:23 ` Jarkko Sakkinen
2015-06-03 16:11 ` Jason Gunthorpe [this message]
2015-06-03 16:43 ` Jarkko Sakkinen
2015-06-03 16:48 ` Jason Gunthorpe
2015-06-03 17:06 ` Jarkko Sakkinen
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=20150603161128.GB12073@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=richard.l.maliszewski@intel.com \
--cc=safford@us.ibm.com \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.net \
/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
all inboxes | Powered by JetHome®