From: Jarkko Sakkinen <jarkko@kernel.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>,
Matthew Garrett <mjg59@google.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH] tpm_tis: Disable interrupts on ThinkPad T490s
Date: Sun, 29 Nov 2020 05:21:45 +0200 [thread overview]
Message-ID: <20201129032145.GC39488@kernel.org> (raw)
In-Reply-To: <67628c88a9ddc85d9957c1847514afe24a6fcebf.camel@HansenPartnership.com>
On Tue, Nov 24, 2020 at 10:10:21AM -0800, James Bottomley wrote:
> On Tue, 2020-11-24 at 10:52 -0700, Jerry Snitselaar wrote:
> > Before diving further into that though, does anyone else have an
> > opinion on ripping out the irq code, and just using polling? We've
> > been only polling since 2015 anyways.
>
> Well only a biased one, obviously: polling causes large amounts of busy
> waiting, which is a waste of CPU resources and does increase the time
> it takes us to do TPM operations ... not a concern if you're doing long
> computation ones, like signatures, but it is a problem for short
> operations like bulk updates of PCRs. The other potential issue, as we
> saw with atmel is that if you prod the chip too often (which you have
> to do with polling) you risk upsetting it. We've spent ages trying to
> tune the polling parameters to balance reduction of busy wait with chip
> upset and still, apparently, not quite got it right. If the TPM has a
> functioning IRQ then it gets us out of the whole polling mess entirely.
> The big question is how many chips that report an IRQ actually have a
> malfunctioning one?
>
> James
Do we have a way to know is Windows TPM code using IRQ's?
/Jarkko
next prev parent reply other threads:[~2020-11-29 3:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 21:44 [PATCH] tpm_tis: Disable interrupts on ThinkPad T490s Jerry Snitselaar
2020-10-15 22:01 ` Jerry Snitselaar
2020-10-15 22:39 ` Matthew Garrett
2020-10-16 6:12 ` Hans de Goede
2020-11-19 6:36 ` Jerry Snitselaar
2020-11-19 14:42 ` Hans de Goede
2020-11-19 17:05 ` Jerry Snitselaar
2020-11-23 12:19 ` Hans de Goede
2020-11-24 3:27 ` Jarkko Sakkinen
2020-11-24 3:29 ` Jarkko Sakkinen
2020-11-24 3:26 ` Jarkko Sakkinen
2020-11-24 17:52 ` Jerry Snitselaar
2020-11-24 18:10 ` James Bottomley
2020-11-29 3:21 ` Jarkko Sakkinen [this message]
2020-11-24 21:45 ` Hans de Goede
2020-11-29 3:23 ` Jarkko Sakkinen
2020-11-29 11:34 ` Hans de Goede
2020-12-02 16:07 ` Jarkko Sakkinen
2020-11-29 3:18 ` Jarkko Sakkinen
2020-10-16 6:10 ` Hans de Goede
2020-10-18 21:11 ` Jarkko Sakkinen
2020-10-18 21:14 ` 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=20201129032145.GC39488@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=hdegoede@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@google.com \
--cc=peterhuewe@gmx.de \
/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).