From: Yunfeng Ye <yeyunfeng@huawei.com>
To: <catalin.marinas@arm.com>, <will@kernel.org>,
<wangkefeng.wang@huawei.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <yeyunfeng@huawei.com>
Cc: <linfeilong@huawei.com>
Subject: [PATCH 0/5] Support ASID Isolation mechanism
Date: Mon, 17 Oct 2022 16:31:58 +0800 [thread overview]
Message-ID: <20221017083203.3690346-1-yeyunfeng@huawei.com> (raw)
From: y00318929 <yeyunfeng@huawei.com>
This series patches introduce an ASID Isolation mechanism to improve
isolation.
Patch 1-3: Prepare for supporting ASID Isolation mechanism.
Patch 4: Detailed Description and Implementation of ASID Isolation
mechanism.
Patch 5: This patch is used to observe the TLB flush information.
Yunfeng Ye (5):
arm64: mm: Define asid_bitmap structure for pinned_asid
arm64: mm: Extract the processing of asid_generation
arm64: mm: Use cpumask in flush_context()
arm64: mm: Support ASID isolation feature
arm64: mm: Add TLB flush trace on context switch
arch/arm64/mm/context.c | 286 ++++++++++++++++++++++++++++++++++------
1 file changed, 247 insertions(+), 39 deletions(-)
--
2.27.0
next reply other threads:[~2022-10-17 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 8:31 Yunfeng Ye [this message]
2022-10-17 8:31 ` [PATCH 1/5] arm64: mm: Define asid_bitmap structure for pinned_asid Yunfeng Ye
2022-10-17 8:32 ` [PATCH 2/5] arm64: mm: Extract the processing of asid_generation Yunfeng Ye
2022-10-17 8:32 ` [PATCH 3/5] arm64: mm: Use cpumask in flush_context() Yunfeng Ye
2022-10-17 8:32 ` [PATCH 4/5] arm64: mm: Support ASID isolation feature Yunfeng Ye
2022-11-09 12:43 ` Catalin Marinas
2022-11-10 7:07 ` Yunfeng Ye
2022-11-28 17:00 ` Catalin Marinas
2022-11-29 12:26 ` Yunfeng Ye
2022-10-17 8:32 ` [PATCH 5/5] arm64: mm: Add TLB flush trace on context switch Yunfeng Ye
-- strict thread matches above, loose matches on Subject: below --
2022-10-17 8:12 [PATCH 0/5] Support ASID Isolation mechanism y00318929
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=20221017083203.3690346-1-yeyunfeng@huawei.com \
--to=yeyunfeng@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=linfeilong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).