[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6973fd402a74a_309510049@dwillia2-mobl4.notmuch>
Date: Fri, 23 Jan 2026 14:59:12 -0800
From: <dan.j.williams@...el.com>
To: Alexey Kardashevskiy <aik@....com>, <linux-crypto@...r.kernel.org>
CC: <linux-kernel@...r.kernel.org>, Ashish Kalra <ashish.kalra@....com>, "Tom
Lendacky" <thomas.lendacky@....com>, John Allen <john.allen@....com>,
"Herbert Xu" <herbert@...dor.apana.org.au>, "David S. Miller"
<davem@...emloft.net>, Dan Williams <dan.j.williams@...el.com>, Alexey
Kardashevskiy <aik@....com>, <x86@...nel.org>, <linux-coco@...ts.linux.dev>,
"Pratik R . Sampat" <prsampat@....com>
Subject: Re: [PATCH kernel 2/2] crypto/ccp: Allow multiple streams on the same
root bridge
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?
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?
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.
Powered by blists - more mailing lists