[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ab7d621e-0ba2-f113-22fc-2866f9cba5f5@codeaurora.org>
Date: Tue, 24 Jan 2017 09:27:44 -0500
From: Christopher Covington <cov@...eaurora.org>
To: Mark Rutland <mark.rutland@....com>,
Catalin Marinas <catalin.marinas@....com>
Cc: Mark Langsdorf <mlangsdo@...hat.com>, kvm@...r.kernel.org,
Jonathan Corbet <corbet@....net>,
Marc Zyngier <marc.zyngier@....com>,
Jon Masters <jcm@...hat.com>, timur@...eaurora.org,
linux-doc@...r.kernel.org, Will Deacon <will.deacon@....com>,
linux-kernel@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
kvmarm@...ts.cs.columbia.edu, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003
On 01/12/2017 11:12 AM, Mark Rutland wrote:
> On Thu, Jan 12, 2017 at 03:45:48PM +0000, Catalin Marinas wrote:
>> On Wed, Jan 11, 2017 at 06:40:52PM +0000, Mark Rutland wrote:
>
>>> Likewise, I beleive we may need to modify cpu_set_reserved_ttbr0().
>>
>> This may be fine if my assumptions about this erratum are correct. In
>> the cpu_set_reserved_ttbr0() case we set TTBR0_EL1 to a table without
>> any entries, so no new entries could be tagged with the old ASID.
>
> For some reason, I was under the impression that the issue was old table
> entries being allocated to the new ASID. Looking over the series again,
> it's not clear to me precisely which cases can occur.
>
> It would be good to see that clarified.
I'll add more general background the commit message in the next revision
and I've also asked directly about this. The answer is that page table
entries using the new translation table base address will be allocated
into the TLB using the old ASID. If employing the workaround, it's
possible for page table entries using the new translation table base
to be allocated into the TLB using the reserved ASID.
Cov
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code
Aurora Forum, a Linux Foundation Collaborative Project.
Powered by blists - more mailing lists