From: Conor Dooley <conor.dooley@microchip.com>
To: Yangyu Chen <cyy@cyyself.name>
Cc: Palmer Dabbelt <palmer@dabbelt.com>, <alexghiti@rivosinc.com>,
<andy.chiu@sifive.com>, Charlie Jenkins <charlie@rivosinc.com>,
<guoren@kernel.org>, <jszhang@kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-riscv@lists.infradead.org>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH v2 0/3] RISC-V: mm: do not treat hint addr on mmap as the upper bound to search
Date: Fri, 1 Mar 2024 13:02:41 +0000 [thread overview]
Message-ID: <20240301-patient-backpedal-f0e9333d3b8b@wendy> (raw)
In-Reply-To: <tencent_BA062F64BB719A8F42F0435BCD3117B73F05@qq.com>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
On Fri, Mar 01, 2024 at 04:54:05AM +0800, Yangyu Chen wrote:
> Another concern is that if we can't make this decision in time to catch up
> with v6.9 we don't want some bad things to happen as a large number of sv48
> machines might appear this year and they may run on the next v6.9 LTS
> kernel, Shall we change the code in the kernel to use sv48 by default right
> now?
Just pointing out that v6.9 is highly unlikely to be the next lts
kernel, depending on whether or not Linus delays some releases, it'll
most likely be either v6.11 or v6.12.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2024-03-01 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 21:48 Yangyu Chen
2024-01-20 21:49 ` [PATCH v2 1/3] " Yangyu Chen
2024-01-20 21:49 ` [PATCH v2 2/3] RISC-V: mm: only test mmap without hint Yangyu Chen
2024-01-20 21:50 ` [PATCH v2 3/3] Documentation: riscv: correct sv57 kernel behavior Yangyu Chen
2024-02-29 12:10 ` [PATCH v2 0/3] RISC-V: mm: do not treat hint addr on mmap as the upper bound to search Yangyu Chen
2024-02-29 19:21 ` Palmer Dabbelt
2024-02-29 20:54 ` Yangyu Chen
2024-03-01 13:02 ` Conor Dooley [this message]
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=20240301-patient-backpedal-f0e9333d3b8b@wendy \
--to=conor.dooley@microchip.com \
--cc=alexghiti@rivosinc.com \
--cc=andy.chiu@sifive.com \
--cc=charlie@rivosinc.com \
--cc=cyy@cyyself.name \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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