Linux-Integrity Archive on
 help / color / Atom feed
From: Jarkko Sakkinen <>
To: Vanya Lazeev <>
Cc: Jason Gunthorpe <>, Peter Huewe <>,
	Arnd Bergmann <>,
	Greg Kroah-Hartman <>,,
Subject: Re: [PATCH v2] Fix fTPM on AMD Zen+ CPUs
Date: Thu, 15 Aug 2019 23:47:42 +0300
Message-ID: <> (raw)
In-Reply-To: <20190812224242.GA3865@tazik.netherland>

On Tue, Aug 13, 2019 at 01:42:42AM +0300, Vanya Lazeev wrote:
> fTPM on Zen+ not only needs multiple mappings, it can also return
> inconsistent with ACPI values for range sizes (as for me and
> mikajhe from the bug thread), so results of crb_containing_resource
> are also used to fix the inconsistencies with crb_fixup_cmd_size.

How do you think that just by your code change, without any explanation
in the commit message, we could backtrack all this information?


      reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Integrity Archive on

Archives are clonable:
	git clone --mirror linux-integrity/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-integrity linux-integrity/ \
	public-inbox-index linux-integrity

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox