All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: maz@kernel.org, steven.price@arm.com, guohanjun@huawei.com,
	Zhenyu Ye <yezhenyu2@huawei.com>,
	will@kernel.org, olof@lixom.net, suzuki.poulose@arm.com
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, zhangshaokun@hisilicon.com,
	prime.zeng@hisilicon.com, linux-arch@vger.kernel.org,
	kuhn.chenqun@huawei.com, xiexiangyou@huawei.com,
	linux-mm@kvack.org, arm@kernel.org
Subject: Re: [PATCH v2 0/2] arm64: tlb: add support for TLBI RANGE instructions
Date: Fri, 10 Jul 2020 20:11:19 +0100	[thread overview]
Message-ID: <159440712962.27784.4664678472466095995.b4-ty@arm.com> (raw)
In-Reply-To: <20200710094420.517-1-yezhenyu2@huawei.com>

On Fri, 10 Jul 2020 17:44:18 +0800, Zhenyu Ye wrote:
> NOTICE: this series are based on the arm64 for-next/tlbi branch:
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/tlbi
> 
> --
> ARMv8.4-TLBI provides TLBI invalidation instruction that apply to a
> range of input addresses. This series add support for this feature.
> 
> [...]

Applied to arm64 (for-next/tlbi), thanks!

[1/2] arm64: tlb: Detect the ARMv8.4 TLBI RANGE feature
      https://git.kernel.org/arm64/c/a2fd755f77ff
[2/2] arm64: tlb: Use the TLBI RANGE feature in arm64
      https://git.kernel.org/arm64/c/db34a081d273

-- 
Catalin


  parent reply	other threads:[~2020-07-10 19:11 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  9:44 [PATCH v2 0/2] arm64: tlb: add support for TLBI RANGE instructions Zhenyu Ye
2020-07-10  9:44 ` Zhenyu Ye
2020-07-10  9:44 ` Zhenyu Ye
2020-07-10  9:44 ` Zhenyu Ye
2020-07-10  9:44 ` [PATCH v2 1/2] arm64: tlb: Detect the ARMv8.4 TLBI RANGE feature Zhenyu Ye
2020-07-10  9:44   ` Zhenyu Ye
2020-07-10  9:44   ` Zhenyu Ye
2020-07-10  9:44 ` [PATCH v2 2/2] arm64: tlb: Use the TLBI RANGE feature in arm64 Zhenyu Ye
2020-07-10  9:44   ` Zhenyu Ye
2020-07-10  9:44   ` Zhenyu Ye
2020-07-10 18:31   ` Catalin Marinas
2020-07-10 18:31     ` Catalin Marinas
2020-07-11  6:50     ` Zhenyu Ye
2020-07-11  6:50       ` Zhenyu Ye
2020-07-11  6:50       ` Zhenyu Ye
2020-07-12 12:03       ` Catalin Marinas
2020-07-12 12:03         ` Catalin Marinas
     [not found]   ` <20200710094420.517-3-yezhenyu2-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2020-07-13 14:27     ` Jon Hunter
2020-07-13 14:27       ` Jon Hunter
2020-07-13 14:27       ` Jon Hunter
2020-07-13 14:27       ` Jon Hunter
     [not found]       ` <4040f429-21c8-0825-2ad4-97786c3fe7c1-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2020-07-13 14:39         ` Zhenyu Ye
2020-07-13 14:39           ` Zhenyu Ye
2020-07-13 14:39           ` Zhenyu Ye
2020-07-13 14:39           ` Zhenyu Ye
     [not found]           ` <cee60718-ced2-069f-8dad-48941c6fc09b-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2020-07-13 14:44             ` Jon Hunter
2020-07-13 14:44               ` Jon Hunter
2020-07-13 14:44               ` Jon Hunter
2020-07-13 14:44               ` Jon Hunter
     [not found]               ` <7237888d-2168-cd8b-c83d-c8e54871793d-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2020-07-13 17:21                 ` Catalin Marinas
2020-07-13 17:21                   ` Catalin Marinas
2020-07-13 17:21                   ` Catalin Marinas
2020-07-14 10:36   ` Catalin Marinas
2020-07-14 10:36     ` Catalin Marinas
2020-07-14 13:51     ` Zhenyu Ye
2020-07-14 13:51       ` Zhenyu Ye
2020-07-14 13:51       ` Zhenyu Ye
2020-07-10 19:11 ` Catalin Marinas [this message]
2020-07-13 12:21   ` [PATCH v2 0/2] arm64: tlb: add support for TLBI RANGE instructions Catalin Marinas
2020-07-13 12:21     ` Catalin Marinas
2020-07-13 12:41     ` Zhenyu Ye
2020-07-13 12:41       ` Zhenyu Ye
2020-07-13 12:41       ` Zhenyu Ye
2020-07-13 16:59       ` Catalin Marinas
2020-07-13 16:59         ` Catalin Marinas
2020-07-14 15:17         ` Zhenyu Ye
2020-07-14 15:17           ` Zhenyu Ye
2020-07-14 15:17           ` Zhenyu Ye
2020-07-14 15:58           ` Catalin Marinas
2020-07-14 15:58             ` Catalin Marinas

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=159440712962.27784.4664678472466095995.b4-ty@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=arm@kernel.org \
    --cc=guohanjun@huawei.com \
    --cc=kuhn.chenqun@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=maz@kernel.org \
    --cc=olof@lixom.net \
    --cc=prime.zeng@hisilicon.com \
    --cc=steven.price@arm.com \
    --cc=suzuki.poulose@arm.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 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.