From: Seunghun Han <kkamagui@gmail.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Vanya Lazeev <ivan.lazeev@gmail.com>,
arnd@arndb.de, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
"open list:TPM DEVICE DRIVER" <linux-integrity@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Huewe <peterhuewe@gmx.de>
Subject: Re: [PATCH v2] Fix fTPM on AMD Zen+ CPUs
Date: Mon, 16 Sep 2019 18:43:36 +0900 [thread overview]
Message-ID: <CAHjaAcSixHporRbU0Y-h-NKRQR2pHqti2qnEtowc2oZkiPOORA@mail.gmail.com> (raw)
In-Reply-To: <20190916090741.GA31747@linux.intel.com>
> Eessentially what you want to do is to detach and backup the original
> NVS resources and put them back to the list with insert_resource() when
> tpm_crb is removed. At least I think this is what should be done but you
> should CC your patch also to the ACPI list for feedback.
>
> /Jarkko
Yes, you are right. But, what I really want to do is requesting
command/response buffer regions from NVS driver and releasing them. To
detach and backup the original NVS resources with insert_resource() or
remove_resource() are not needed maybe.
I have some idea about it, so I have sent an email to you. Would you
check the email and give comments? The link is here,
https://lkml.org/lkml/2019/9/16/112 .
Seunghun
next prev parent reply other threads:[~2019-09-16 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 5:17 [PATCH v2] Fix fTPM on AMD Zen+ CPUs Seunghun Han
2019-09-13 14:00 ` Jarkko Sakkinen
2019-09-13 14:02 ` Jarkko Sakkinen
2019-09-16 5:29 ` Seunghun Han
2019-09-16 9:07 ` Jarkko Sakkinen
2019-09-16 9:43 ` Seunghun Han [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-11 18:52 ivan.lazeev
2019-08-12 13:10 ` Jason Gunthorpe
2019-08-12 22:42 ` Vanya Lazeev
2019-08-15 20:47 ` 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=CAHjaAcSixHporRbU0Y-h-NKRQR2pHqti2qnEtowc2oZkiPOORA@mail.gmail.com \
--to=kkamagui@gmail.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=ivan.lazeev@gmail.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).