From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [tpmdd-devel] [PATCH] tpm: improve tpm_tis send() performance by ignoring burstcount
Date: Mon, 14 Aug 2017 08:12:53 -0400 [thread overview]
Message-ID: <1502712773.6179.26.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170814105651.eo3e7tokt7mujeba@linux.intel.com>
On Mon, 2017-08-14 at 13:56 +0300, Jarkko Sakkinen wrote:
> > > Since the main concern about this change is breaking old systems that
> > > might potentially have other peripherals hanging off the LPC bus, can
> > > we define a new Kconfig option, with the default as 'N'?
> > >
> > > Mimi
> >
> > I guess that could make sense but I would like to hear feedback first.
> >
> > /Jarkko
>
> And I'm worried would that it'd be left for many years to come as an
> option. I do not have any metrics what portion of hardware in the field
> would break if this is turned on.
>
> It would slow down kernel testing as I would have to run tests for the
> driver with that option turned on and off because it is a major shift
> from how driver functions. And I have zero idea how long I would go on
> doing this.
>
> One maybe a little bit better option would be to have a sysfs attribute
> for this functionality (disable_burst_count). What do you think about
> that?
That works! So we'll define a module_param named disable_burst_count,
which can be specified on the boot command line.
Mimi
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Peter Huewe <PeterHuewe@gmx.de>,
Ken Goldman <kgold@linux.vnet.ibm.com>,
linux-ima-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Re: [tpmdd-devel] [PATCH] tpm: improve tpm_tis send() performance by ignoring burstcount
Date: Mon, 14 Aug 2017 08:12:53 -0400 [thread overview]
Message-ID: <1502712773.6179.26.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170814105651.eo3e7tokt7mujeba@linux.intel.com>
On Mon, 2017-08-14 at 13:56 +0300, Jarkko Sakkinen wrote:
> > > Since the main concern about this change is breaking old systems that
> > > might potentially have other peripherals hanging off the LPC bus, can
> > > we define a new Kconfig option, with the default as 'N'?
> > >
> > > Mimi
> >
> > I guess that could make sense but I would like to hear feedback first.
> >
> > /Jarkko
>
> And I'm worried would that it'd be left for many years to come as an
> option. I do not have any metrics what portion of hardware in the field
> would break if this is turned on.
>
> It would slow down kernel testing as I would have to run tests for the
> driver with that option turned on and off because it is a major shift
> from how driver functions. And I have zero idea how long I would go on
> doing this.
>
> One maybe a little bit better option would be to have a sysfs attribute
> for this functionality (disable_burst_count). What do you think about
> that?
That works! So we'll define a module_param named disable_burst_count,
which can be specified on the boot command line.
Mimi
next prev parent reply other threads:[~2017-08-14 12:12 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 11:46 [PATCH] tpm: improve tpm_tis send() performance by ignoring burstcount Nayna Jain
2017-08-07 11:46 ` Nayna Jain
2017-08-07 11:52 ` Peter Huewe
2017-08-07 11:52 ` Peter Huewe
2017-08-07 14:25 ` Nayna
2017-08-07 14:25 ` Nayna
2017-08-08 21:50 ` Jarkko Sakkinen
2017-08-08 21:50 ` Jarkko Sakkinen
2017-08-08 19:11 ` Jarkko Sakkinen
2017-08-08 19:11 ` Jarkko Sakkinen
2017-08-09 20:23 ` [tpmdd-devel] " Ken Goldman
2017-08-09 20:23 ` Ken Goldman
2017-08-09 20:23 ` Ken Goldman
2017-08-09 20:43 ` Aw: " Peter Huewe
2017-08-09 20:43 ` Peter Huewe
2017-08-11 21:54 ` Ken Goldman
2017-08-11 21:54 ` Ken Goldman
2017-08-11 21:54 ` Ken Goldman
[not found] ` <20170814101046.5hqrkaqmfvl7ugwj@linux.intel.com>
2017-08-16 19:51 ` Ken Goldman
2017-08-16 19:51 ` Ken Goldman
2017-08-16 19:51 ` Ken Goldman
2017-08-09 20:25 ` Ken Goldman
2017-08-09 20:25 ` Ken Goldman
2017-08-09 20:25 ` Ken Goldman
2017-08-09 21:00 ` Aw: " Peter Huewe
2017-08-09 21:00 ` Peter Huewe
2017-08-11 11:14 ` Jarkko Sakkinen
2017-08-11 11:14 ` Jarkko Sakkinen
2017-08-11 15:30 ` Mimi Zohar
2017-08-11 15:30 ` Mimi Zohar
2017-08-14 10:51 ` Jarkko Sakkinen
2017-08-14 10:51 ` Jarkko Sakkinen
2017-08-14 10:56 ` Jarkko Sakkinen
2017-08-14 10:56 ` Jarkko Sakkinen
2017-08-14 12:03 ` Mimi Zohar
2017-08-14 12:03 ` Mimi Zohar
2017-08-15 6:08 ` Jarkko Sakkinen
2017-08-15 6:08 ` Jarkko Sakkinen
2017-08-14 12:12 ` Mimi Zohar [this message]
2017-08-14 12:12 ` Mimi Zohar
2017-08-15 6:09 ` Jarkko Sakkinen
2017-08-15 6:09 ` Jarkko Sakkinen
2017-08-11 21:32 ` Aw: " Ken Goldman
2017-08-11 21:32 ` Ken Goldman
2017-08-11 21:32 ` Ken Goldman
2017-08-13 23:53 ` msuchanek
2017-08-13 23:53 ` msuchanek
2017-08-15 22:02 ` Ken Goldman
2017-08-15 22:02 ` Ken Goldman
2017-08-15 22:02 ` Ken Goldman
2017-08-16 10:24 ` Michal Suchánek
2017-08-16 10:24 ` Michal Suchánek
2017-08-11 21:42 ` [Linux-ima-devel] " Ken Goldman
2017-08-11 21:42 ` Ken Goldman
2017-08-11 21:42 ` Ken Goldman
2017-08-08 19:07 ` Jarkko Sakkinen
2017-08-08 19:07 ` 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=1502712773.6179.26.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=linux-security-module@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.