All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Zhenyu Ye <yezhenyu2@huawei.com>
Cc: mark.rutland@arm.com, linux-arch@vger.kernel.org, arm@kernel.org,
	catalin.marinas@arm.com, guohanjun@huawei.com,
	linux-kernel@vger.kernel.org, xiexiangyou@huawei.com,
	steven.price@arm.com, linux-mm@kvack.org, broonie@kernel.org,
	prime.zeng@hisilicon.com, aneesh.kumar@linux.ibm.com,
	will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v1 0/3] arm64: tlb: add support for TTL field
Date: Wed, 11 Mar 2020 09:12:54 +0000	[thread overview]
Message-ID: <247ad619edf17eb266f856d937dac826@kernel.org> (raw)
In-Reply-To: <20200311025309.1743-1-yezhenyu2@huawei.com>

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/
-- 
Jazz is not dead. It just smells funny...

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Zhenyu Ye <yezhenyu2@huawei.com>
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
Subject: Re: [RFC PATCH v1 0/3] arm64: tlb: add support for TTL field
Date: Wed, 11 Mar 2020 09:12:54 +0000	[thread overview]
Message-ID: <247ad619edf17eb266f856d937dac826@kernel.org> (raw)
Message-ID: <20200311091254.o5o9Xs1YOVDEI4COfUQ9ErAx4YzRQmtKY_V6xCI21OE@z> (raw)
In-Reply-To: <20200311025309.1743-1-yezhenyu2@huawei.com>

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/
-- 
Jazz is not dead. It just smells funny...

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Zhenyu Ye <yezhenyu2@huawei.com>
Cc: mark.rutland@arm.com, linux-arch@vger.kernel.org, arm@kernel.org,
	catalin.marinas@arm.com, guohanjun@huawei.com,
	linux-kernel@vger.kernel.org, xiexiangyou@huawei.com,
	steven.price@arm.com, linux-mm@kvack.org, broonie@kernel.org,
	prime.zeng@hisilicon.com, aneesh.kumar@linux.ibm.com,
	will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH v1 0/3] arm64: tlb: add support for TTL field
Date: Wed, 11 Mar 2020 09:12:54 +0000	[thread overview]
Message-ID: <247ad619edf17eb266f856d937dac826@kernel.org> (raw)
In-Reply-To: <20200311025309.1743-1-yezhenyu2@huawei.com>

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/
-- 
Jazz is not dead. It just smells funny...

_______________________________________________
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-03-11  9:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11  2:53 [RFC PATCH v1 0/3] arm64: tlb: add support for TTL field Zhenyu Ye
2020-03-11  2:53 ` Zhenyu Ye
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   ` Zhenyu Ye
2020-03-11  2:53   ` 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   ` Zhenyu Ye
2020-03-11  2:53   ` 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  2:53   ` Zhenyu Ye
2020-03-11  2:53   ` Zhenyu Ye
2020-03-11  9:12 ` Marc Zyngier [this message]
2020-03-11  9:12   ` [RFC PATCH v1 0/3] arm64: tlb: add support for TTL field Marc Zyngier
2020-03-11  9:12   ` Marc Zyngier
2020-03-11 11:29   ` yezhenyu (A)
2020-03-11 11:29     ` yezhenyu (A)
2020-03-11 11:29     ` yezhenyu (A)
2020-03-17 10:59   ` yezhenyu (A)
2020-03-17 10:59     ` yezhenyu (A)
2020-03-17 10:59     ` yezhenyu (A)

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=247ad619edf17eb266f856d937dac826@kernel.org \
    --to=maz@kernel.org \
    --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=prime.zeng@hisilicon.com \
    --cc=steven.price@arm.com \
    --cc=will@kernel.org \
    --cc=xiexiangyou@huawei.com \
    --cc=yezhenyu2@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.