public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Zhenyu Ye <yezhenyu2@huawei.com>
To: Will Deacon <will@kernel.org>, Hanjun Guo <guohanjun@huawei.com>
Cc: mark.rutland@arm.com, Rob Herring <robh@kernel.org>,
	wanghuiqiang <wanghuiqiang@huawei.com>,
	Anna.Chen@arm.com, suzuki.poulose@arm.com,
	catalin.marinas@arm.com,
	'Matteo Carlini' <Matteo.Carlini@arm.com>,
	xiexiangyou@huawei.com, Linuxarm <linuxarm@huawei.com>,
	Shaokun Zhang <zhangshaokun@hisilicon.com>,
	tangnianyao@huawei.com, Marc Zyngier <maz@kernel.org>,
	linux-arm-kernel@lists.infradead.org, qiuzhenfa@hisilicon.com
Subject: Re: [RFC PATCH v2] arm64: cpufeatures: add support for tlbi range instructions
Date: Tue, 14 Apr 2020 19:45:07 +0800	[thread overview]
Message-ID: <5e56599f-c10a-9bd2-1e37-bcec564272c9@huawei.com> (raw)
In-Reply-To: <20200414070809.GA24197@willie-the-truck>

Hi Will,

On 2020/4/14 15:08, Will Deacon wrote:
> 
> I'm worried about the TTL series without being able to test it.
> Please post a v3 of the TLBI by range patch again when you get a chance.
> 

I have sent the v3 of the TLBI RANGE patch based on Linux 5.7-rc1:

https://lore.kernel.org/linux-arm-kernel/20200414112835.1121-1-yezhenyu2@huawei.com/


As for the TTL series, it's based on commit "a6d60245d6", which has tracked
the levels of the page tables have been cleared, so I think there is no
problem at the software level. (The stride parameter of __flush_tlb_range in
ARM64 also depends on the values of cleared_*, and behaves well)

If we want to test whether the hardware deals with TTL correctly, I have a
vague idea:

1. mmap a piece of memory;
2. write our own change_protection_range(), in which calls the tlbi
   interface with TTL value;
3. if the hardware deals with TTL correctly, the permissions of memory
   should have changed, otherwise not.


Thanks,
Zhenyu



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-04-14 11:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5DC960EB.9050503@huawei.com>
     [not found] ` <20191111132716.GA9394@willie-the-truck>
     [not found]   ` <5DC96660.8040505@huawei.com>
     [not found]     ` <d4542758f83b3df3ab391341499fecfb@www.loen.fr>
2019-11-19  1:13       ` [RFC PATCH v2] arm64: cpufeatures: add support for tlbi range instructions Hanjun Guo
2019-11-19 10:03         ` Marc Zyngier
2019-11-20  1:29           ` Hanjun Guo
2020-04-10  1:43             ` Hanjun Guo
2020-04-10 11:54               ` Will Deacon
2020-04-10 12:02                 ` Will Deacon
2020-04-11  6:39                   ` Hanjun Guo
2020-04-14  7:08                     ` Will Deacon
2020-04-14  7:27                       ` Hanjun Guo
2020-04-14 11:45                       ` Zhenyu Ye [this message]
2020-04-11  6:24                 ` Hanjun Guo
2019-11-20  8:47           ` Will Deacon

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=5e56599f-c10a-9bd2-1e37-bcec564272c9@huawei.com \
    --to=yezhenyu2@huawei.com \
    --cc=Anna.Chen@arm.com \
    --cc=Matteo.Carlini@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxarm@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=qiuzhenfa@hisilicon.com \
    --cc=robh@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=tangnianyao@huawei.com \
    --cc=wanghuiqiang@huawei.com \
    --cc=will@kernel.org \
    --cc=xiexiangyou@huawei.com \
    --cc=zhangshaokun@hisilicon.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