public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Hanjun Guo <guohanjun@huawei.com>
To: Will Deacon <will@kernel.org>
Cc: mark.rutland@arm.com, Rob Herring <robh@kernel.org>,
	wanghuiqiang <wanghuiqiang@huawei.com>,
	Anna.Chen@arm.com, Zhenyu Ye <yezhenyu2@huawei.com>,
	catalin.marinas@arm.com, suzuki.poulose@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: Sat, 11 Apr 2020 14:39:13 +0800	[thread overview]
Message-ID: <5af3a54c-c058-78a8-eba2-9e2ef666beee@huawei.com> (raw)
In-Reply-To: <20200410120235.GC24814@willie-the-truck>

On 2020/4/10 20:02, Will Deacon wrote:
> On Fri, Apr 10, 2020 at 12:54:46PM +0100, Will Deacon wrote:
>> On Fri, Apr 10, 2020 at 09:43:49AM +0800, Hanjun Guo wrote:
>>> On 2019/11/20 9:29, Hanjun Guo wrote:
>>>>>
>>>>> I also wonder if the ARMv8.4-TTL extension (which I have patches for in
>>>>> the nested virt series) requires the same kind of treatment (after all,
>>>>> it has an implicit range based on the base granule size and level).
>>>>>
>>>>> In any way, this requires careful specification, and I don't think
>>>>> we can improvise this on the ML... ;-)
>>>>
>>>> Sure :), the good news is that ARM officially announced will be
>>>> working with Huawei again.
>>>>
>>>> So if I understand your point correctly, we need steps to take:
>>>>    - ARM spec needs to make TIBi by range crystal clear and being
>>>>      written down in the spec;
>>>>    - Firmware description of supporting TLBi by range in system level
>>>>      for both FDT and ACPI;
>>>>    - Then upstream the code.
>>>
>>> Do we have update here? I noticed that the TLBI by rang for SMMU is
>>> merged for upstream from Rob, any plan or progress for the CPU side?
>>>
>>> Sorry to ping you on the mailling list, our upcoming new chip has
>>> this feature and it's good to enable it, so it's a bit urgent for us.
>>
>> Have you tried look at the latest version of the patches rather than
>> "pinging" old history? We're also in the merge window at the moment, so
>> please cut us some slack.
>>
>> I also fail to see the urgency. This thing is a pure performance play, and a
>> fairly niche one at that. I'm not especially comfortable ripping up our TLBI
>> code without being able to test it.
> 
> Argh, so while it *is* the middle of the merge window and I do fail to see
> the urgency of this, I also mixed it up with the TTL series, which is the one
> I'm really worried about.
> 
> Please post a v3 at -rc1.

A bit lost here, do you mean the TLBi by range patch or the TTL series?

Thanks
Hanjun


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

  reply	other threads:[~2020-04-11  6:39 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 [this message]
2020-04-14  7:08                     ` Will Deacon
2020-04-14  7:27                       ` Hanjun Guo
2020-04-14 11:45                       ` Zhenyu Ye
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=5af3a54c-c058-78a8-eba2-9e2ef666beee@huawei.com \
    --to=guohanjun@huawei.com \
    --cc=Anna.Chen@arm.com \
    --cc=Matteo.Carlini@arm.com \
    --cc=catalin.marinas@arm.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=yezhenyu2@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