From: Matthew Garrett <mjg59@google.com>
To: "Safford, David (GE Global Research, US)" <david.safford@ge.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>,
"jarkko.sakkinen@linux.intel.com"
<jarkko.sakkinen@linux.intel.com>,
"Wiseman, Monty (GE Global Research, US)" <monty.wiseman@ge.com>
Subject: Re: [PATCH] tpm_crb - workaround broken ACPI tables
Date: Mon, 15 Jul 2019 12:44:41 -0700 [thread overview]
Message-ID: <CACdnJusQncWiwrDfjNQpYs4_YoNevJ9+SzBrFzJ0CyLRxA8pQQ@mail.gmail.com> (raw)
In-Reply-To: <CACdnJuuE8GLnPdgcYqLzpY+8tY7JedYybb9S7QTYH8nccyLGgA@mail.gmail.com>
On Sun, Jul 14, 2019 at 4:48 PM Matthew Garrett <mjg59@google.com> wrote:
>
> Hmm that's weird - that's a surprisingly large region of reserved
> space. I've no idea why that would be covered, and it definitely makes
> things more complicated.
My gut feeling here is that we should figure out something with the
NVS code to handle the common case, and independently try to figure
out what's going on with this machine.
next prev parent reply other threads:[~2019-07-15 19:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 12:29 [PATCH] tpm_crb - workaround broken ACPI tables Safford, David (GE Global Research, US)
2019-07-11 14:10 ` Jarkko Sakkinen
2019-07-11 14:58 ` Jason Gunthorpe
2019-07-11 16:44 ` Safford, David (GE Global Research, US)
2019-07-11 18:50 ` Jason Gunthorpe
2019-07-11 19:31 ` Safford, David (GE Global Research, US)
2019-07-11 20:33 ` Matthew Garrett
2019-07-12 12:41 ` Safford, David (GE Global Research, US)
2019-07-12 15:06 ` Jason Gunthorpe
2019-07-12 15:48 ` Jarkko Sakkinen
2019-07-12 18:24 ` Matthew Garrett
2019-07-12 19:05 ` Safford, David (GE Global Research, US)
2019-07-12 20:36 ` Matthew Garrett
2019-07-14 19:28 ` Safford, David (GE Global Research, US)
2019-07-14 23:48 ` Matthew Garrett
2019-07-15 19:44 ` Matthew Garrett [this message]
2019-07-11 19:16 ` 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=CACdnJusQncWiwrDfjNQpYs4_YoNevJ9+SzBrFzJ0CyLRxA8pQQ@mail.gmail.com \
--to=mjg59@google.com \
--cc=david.safford@ge.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=monty.wiseman@ge.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;
as well as URLs for NNTP newsgroup(s).