[MODERATED] Re: [PATCH v5 08/11] TAAv5 8

On 21/10/2019 21:33, speck for Pawan Gupta wrote:
> On Mon, Oct 21, 2019 at 03:34:40PM -0500, speck for Josh Poimboeuf wrote:
>> On Mon, Oct 21, 2019 at 03:33:38PM -0500, Josh Poimboeuf wrote:
>>> On Mon, Oct 21, 2019 at 01:01:39PM -0700, speck for Pawan Gupta wrote:
>>>> On Mon, Oct 21, 2019 at 02:54:29PM +0200, speck for Michal Hocko wrote:
>>>>> On Thu 17-10-19 17:14:07, speck for Pawan Gupta wrote:
>>>>> [...]
>>>>>> Let me know if there are any questions.
>>>>> is there any list of CPUs that would benefit from tsx=auto compared to
>>>>> tsx=on? In other words do we really need both?
>>>> Below is the list of TAA affected CPUs that will get TSX_CTRL MSR.
>>>>
>>>> +----------------------------+------------------+------------+
>>>> |            Name            |  Family / model  |  Stepping  |
>>>> +============================+==================+============+
>>>> | Whiskey Lake (ULT refresh) |      06_8E       |    0xC     |
>>>> +----------------------------+------------------+------------+
>>>> |    2nd gen Cascade Lake    |      06_55       |    6, 7    |
>>>> +----------------------------+------------------+------------+
>>>> |       Coffee Lake R        |      06_9E       |    0xD     |
>>>> +----------------------------+------------------+------------+
>>>>
>>>> tsx=auto on these CPUs will disable TSX.
>>>> tsx=on will keep TSX enabled.
>> [ Please ignore my previous email, it had a glaring typo ]
>>
>> Just to clarify, is this list identical to the list of CPUs which are
>> vulnerable to TAA and have MDS_NO=1?
> That is correct.

What about Commit Lake parts, because that is explicitly called out in
the list of MDS_NO=1, TAA-vulnerable parts in initial whitepaper about TAA.

~Andrew