public inbox for linux-coco@lists.linux.dev
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@amd.com>
To: dan.j.williams@intel.com, linux-crypto@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Ashish Kalra <ashish.kalra@amd.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	John Allen <john.allen@amd.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	x86@kernel.org, linux-coco@lists.linux.dev,
	"Pratik R . Sampat" <prsampat@amd.com>
Subject: Re: [PATCH kernel 2/2] crypto/ccp: Allow multiple streams on the same root bridge
Date: Mon, 26 Jan 2026 11:44:45 +1100	[thread overview]
Message-ID: <196ef0d2-93ac-4872-831b-e803e02b5d95@amd.com> (raw)
In-Reply-To: <6973fd402a74a_309510049@dwillia2-mobl4.notmuch>



On 24/1/26 09:59, dan.j.williams@intel.com wrote:
> Alexey Kardashevskiy wrote:
>> IDE stream IDs are responsibility of a platform and in some cases TSM
>> allocates the numbers. AMD SEV TIO though leaves it to the host OS.
>> Mistakenly stream ID is hard coded to be the same as a traffic class.
> 
> I scratched my head at this comment, but now realize that you are saying
> the existing code used the local @tc, not that the hardware stream ID is
> in any way related to traffic class, right?

When I did that in the first place, I also wanted to try different traffic classes so I just took a shortcut here.

> It would help to detail what the end user visible effects of this bug
> are. The TSM framework does not allow for multiple streams per PF, so I
> wonder what scenario is being fixed?

There is no way in the current upstream code to specify this TC so the only visible effect is that 2 devices under the same bridge can work now, previously the second device would fail to allocate a stream.

> Lastly, are you expecting tsm.git#fixes to pick this up? I am assuming
> that this goes through crypto.git and tsm.git can just stay focused on
> core fixes.

I was kinda hoping that Tom acks these (as he did) and you could take them. Thanks,

-- 
Alexey


  reply	other threads:[~2026-01-26  0:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-23  5:30 [PATCH kernel 0/2] crypto/ccp: Fixes for PCI IDE Alexey Kardashevskiy
2026-01-23  5:30 ` [PATCH kernel 1/2] crypto/ccp: Use PCI bridge defaults for IDE Alexey Kardashevskiy
2026-01-23 22:48   ` dan.j.williams
2026-01-23  5:30 ` [PATCH kernel 2/2] crypto/ccp: Allow multiple streams on the same root bridge Alexey Kardashevskiy
2026-01-23 22:59   ` dan.j.williams
2026-01-26  0:44     ` Alexey Kardashevskiy [this message]
2026-01-27  6:59       ` dan.j.williams
2026-01-29 22:29         ` Alexey Kardashevskiy
2026-01-23 16:01 ` [PATCH kernel 0/2] crypto/ccp: Fixes for PCI IDE Tom Lendacky

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=196ef0d2-93ac-4872-831b-e803e02b5d95@amd.com \
    --to=aik@amd.com \
    --cc=ashish.kalra@amd.com \
    --cc=dan.j.williams@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=john.allen@amd.com \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prsampat@amd.com \
    --cc=thomas.lendacky@amd.com \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox