From: Marc Zyngier <maz@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will@kernel.org, akpm@linux-foundation.org,
oliver.upton@linux.dev, mark.rutland@arm.com,
ryan.roberts@arm.com, apopple@nvidia.com, rananta@google.com,
yangyicong@hisilicon.com, v-songbaohua@oppo.com,
yezhenyu2@huawei.com, yihyu@redhat.com, shan.gavin@gmail.com
Subject: Re: [PATCH v2] arm64: tlb: Fix TLBI RANGE operand
Date: Thu, 04 Apr 2024 18:33:16 +0100 [thread overview]
Message-ID: <87frw1rq1v.wl-maz@kernel.org> (raw)
In-Reply-To: <d0b2f9d0-228f-488d-94b8-79f01f17e4e8@redhat.com>
On Thu, 04 Apr 2024 11:26:20 +0100,
Gavin Shan <gshan@redhat.com> wrote:
>
> In summary, we need 3 patches but the one fixing __TLBI_RANGE_NUM needs to be
> PATCH[1/3] so that it can be easily picked by stable kernel. PATCH[2/3] would
> be to improve __TLBI_VADDR_RANGE with masks. PATCH[3/3] will allow __flush_tlb_range_nosync()
> to do range-based TLB flush for MAX_TLBI_RANGE_PAGES.
That's about it indeed.
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Gavin Shan <gshan@redhat.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will@kernel.org, akpm@linux-foundation.org,
oliver.upton@linux.dev, mark.rutland@arm.com,
ryan.roberts@arm.com, apopple@nvidia.com, rananta@google.com,
yangyicong@hisilicon.com, v-songbaohua@oppo.com,
yezhenyu2@huawei.com, yihyu@redhat.com, shan.gavin@gmail.com
Subject: Re: [PATCH v2] arm64: tlb: Fix TLBI RANGE operand
Date: Thu, 04 Apr 2024 18:33:16 +0100 [thread overview]
Message-ID: <87frw1rq1v.wl-maz@kernel.org> (raw)
In-Reply-To: <d0b2f9d0-228f-488d-94b8-79f01f17e4e8@redhat.com>
On Thu, 04 Apr 2024 11:26:20 +0100,
Gavin Shan <gshan@redhat.com> wrote:
>
> In summary, we need 3 patches but the one fixing __TLBI_RANGE_NUM needs to be
> PATCH[1/3] so that it can be easily picked by stable kernel. PATCH[2/3] would
> be to improve __TLBI_VADDR_RANGE with masks. PATCH[3/3] will allow __flush_tlb_range_nosync()
> to do range-based TLB flush for MAX_TLBI_RANGE_PAGES.
That's about it indeed.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-04-04 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 5:36 [PATCH v2] arm64: tlb: Fix TLBI RANGE operand Gavin Shan
2024-04-04 5:36 ` Gavin Shan
2024-04-04 9:10 ` Marc Zyngier
2024-04-04 9:10 ` Marc Zyngier
2024-04-04 10:26 ` Gavin Shan
2024-04-04 10:26 ` Gavin Shan
2024-04-04 17:33 ` Marc Zyngier [this message]
2024-04-04 17:33 ` Marc Zyngier
2024-04-05 4:05 ` Gavin Shan
2024-04-05 4:05 ` Gavin Shan
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=87frw1rq1v.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=oliver.upton@linux.dev \
--cc=rananta@google.com \
--cc=ryan.roberts@arm.com \
--cc=shan.gavin@gmail.com \
--cc=v-songbaohua@oppo.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=yezhenyu2@huawei.com \
--cc=yihyu@redhat.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.