LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "yezhenyu (A)" <yezhenyu2@huawei.com>
To: Marc Zyngier <maz@kernel.org>
Cc: <mark.rutland@arm.com>, <catalin.marinas@arm.com>,
<will@kernel.org>, <aneesh.kumar@linux.ibm.com>,
<steven.price@arm.com>, <broonie@kernel.org>,
<guohanjun@huawei.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-arch@vger.kernel.org>,
<linux-mm@kvack.org>, <arm@kernel.org>, <xiexiangyou@huawei.com>,
<prime.zeng@hisilicon.com>, <zhangshaokun@hisilicon.com>
Subject: Re: [RFC PATCH v1 0/3] arm64: tlb: add support for TTL field
Date: Tue, 17 Mar 2020 18:59:40 +0800 [thread overview]
Message-ID: <e155d744-4433-b9a6-109f-f665316dd928@huawei.com> (raw)
In-Reply-To: <247ad619edf17eb266f856d937dac826@kernel.org>
Hi Marc,
On 2020/3/11 17:12, Marc Zyngier wrote:
> Zhenyu,
>
> On 2020-03-11 02:53, Zhenyu Ye wrote:
>> ARMv8.4-TTL provides the TTL field in tlbi instruction to indicate
>> the level of translation table walk holding the leaf entry for the
>> address that is being invalidated. Hardware can use this information
>> to determine if there was a risk of splintering.
>>
>> This set of patches adds TTL field to __TLBI_ADDR, and uses
>> Architecture-specific MM context to pass the TTL value to tlb interface.
>>
>> The default value of TTL is 0, which will not have any impact on the
>> TLB maintenance instructions. The last patch trys to use TTL field in
>> some obviously tlb-flush interface.
>
> I have already posted some support for ARMv8.4-TTL as part of my NV series [1],
> patches 62, 67, 68 and 69. This only deals with Stage-2 translation so far.
> If you intend to add Stage-1, please build on top of what I have already posted
> (I can extract the patches on a separate branch if you want).
>
> Thanks,
>
> M.
>
> [1] https://lore.kernel.org/linux-arm-kernel/20200211174938.27809-1-maz@kernel.org/
I have sent the PATCH v2 on 2020-03-12 [1]. Do you have any suggestion
for my code? Is it appropriate to post my code based on your branch?
Looking forward to your suggestions.
Thanks,
zhenyu
[1] https://lkml.org/lkml/2020/3/12/2
prev parent reply other threads:[~2020-03-17 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 2:53 Zhenyu Ye
2020-03-11 2:53 ` [RFC PATCH v1 1/3] arm64: tlb: add TTL field to __TLBI_ADDR Zhenyu Ye
2020-03-11 2:53 ` [RFC PATCH v1 2/3] arm64: tlb: use mm_struct.context.flags to indicate TTL Zhenyu Ye
2020-03-11 2:53 ` [RFC PATCH v1 3/3] arm64: tlb: add support for TTL in some functions Zhenyu Ye
2020-03-11 9:12 ` [RFC PATCH v1 0/3] arm64: tlb: add support for TTL field Marc Zyngier
2020-03-11 11:29 ` yezhenyu (A)
2020-03-17 10:59 ` yezhenyu (A) [this message]
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=e155d744-4433-b9a6-109f-f665316dd928@huawei.com \
--to=yezhenyu2@huawei.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=arm@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=guohanjun@huawei.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=prime.zeng@hisilicon.com \
--cc=steven.price@arm.com \
--cc=will@kernel.org \
--cc=xiexiangyou@huawei.com \
--cc=zhangshaokun@hisilicon.com \
--subject='Re: [RFC PATCH v1 0/3] arm64: tlb: add support for TTL field' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).