From: Christopher Covington <cov@codeaurora.org>
To: Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Mark Langsdorf <mlangsdo@redhat.com>,
kvm@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Marc Zyngier <marc.zyngier@arm.com>, Jon Masters <jcm@redhat.com>,
timur@codeaurora.org, linux-doc@vger.kernel.org,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/5] arm64: Work around Falkor erratum 1003
Date: Tue, 24 Jan 2017 09:27:44 -0500 [thread overview]
Message-ID: <ab7d621e-0ba2-f113-22fc-2866f9cba5f5@codeaurora.org> (raw)
In-Reply-To: <20170112161214.GB12583@leverpostej>
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.
next prev parent reply other threads:[~2017-01-24 14:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 14:41 [PATCH v3 1/5] arm64: Define Falkor v1 CPU Christopher Covington
2017-01-11 14:41 ` [PATCH v3 2/5] arm64: Work around Falkor erratum 1003 Christopher Covington
2017-01-11 18:06 ` Catalin Marinas
2017-01-11 18:22 ` Marc Zyngier
2017-01-11 18:40 ` Mark Rutland
2017-01-12 15:45 ` Catalin Marinas
2017-01-12 16:12 ` Mark Rutland
2017-01-24 14:27 ` Christopher Covington [this message]
2017-01-12 15:55 ` Catalin Marinas
2017-01-12 16:07 ` Will Deacon
2017-01-11 18:33 ` Mark Rutland
2017-01-11 18:35 ` Timur Tabi
2017-01-11 18:37 ` Mark Rutland
2017-01-11 18:40 ` Timur Tabi
2017-01-11 18:45 ` Mark Rutland
2017-01-16 14:26 ` Christopher Covington
2017-01-11 18:50 ` Marc Zyngier
2017-01-12 9:59 ` Catalin Marinas
2017-01-24 14:54 ` Christopher Covington
2017-01-11 14:41 ` [PATCH v3 3/5] arm64: Create and use __tlbi_dsb() macros Christopher Covington
2017-01-12 16:58 ` Will Deacon
2017-01-13 15:12 ` Christopher Covington
2017-01-13 16:12 ` Will Deacon
2017-01-24 22:03 ` Christopher Covington
2017-01-11 14:41 ` [PATCH v3 4/5] arm64: Use __tlbi_dsb() macros in KVM code Christopher Covington
2017-01-11 14:41 ` [PATCH v3 5/5] arm64: Work around Falkor erratum 1009 Christopher Covington
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=ab7d621e-0ba2-f113-22fc-2866f9cba5f5@codeaurora.org \
--to=cov@codeaurora.org \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=jcm@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mlangsdo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=timur@codeaurora.org \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®