From: Palmer Dabbelt <palmer@dabbelt.com>
To: leyfoon.tan@starfivetech.com
Cc: alexandre.ghiti@canonical.com, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: arch/riscv: SV48 patch series questions
Date: Wed, 01 Jun 2022 20:44:00 -0700 (PDT) [thread overview]
Message-ID: <mhng-055df44c-3feb-41ae-b8c0-ae3a6489dee1@palmer-ri-x1c9> (raw)
In-Reply-To: <83813d991f96428c95c6d681c16ae852@EXMBX161.cuchost.com>
On Fri, 27 May 2022 02:37:34 PDT (-0700), leyfoon.tan@starfivetech.com wrote:
> Hi Palmer
>
> Alex's "Introduce sv48 support without relocatable kernel" patch series in [1] was partially merged to Linux v5.17. But there are 4 patches are not merged (Patch-10 to 13).
>
> May I know what is the plan for these patches? Will them merged to next v5.19 merging window? Or do you expect any changes for these patches or Alex needs resend with rebase to latest kernel version?
I just saw this as I was digging up Alex's old email to reply to, all
but #13 are now on for-next.
> Note, we would like to use the Patch-13 in this series.
Is your use case a CPU errata? If so I think we should just go ahead
and add that errata via the existing errata mechanism. If you've got
some other use case, do you mind elaborating? From that other thread it
sounds like a command-line argument is the way to go for folks who want
to turn this off more dynamically, but happy to hear if you've got
something different in mind.
> Patches not merged:
> [v3,10/13] riscv: Improve virtual kernel memory layout dump
> [v3,11/13] Documentation: riscv: Add sv48 description to VM layout
> [v3,12/13] riscv: Initialize thread pointer before calling C functions
> [v3,13/13] riscv: Allow user to downgrade to sv39 when hw supports sv48 if !KASAN
>
> [1]: https://patchwork.kernel.org/project/linux-riscv/cover/20211206104657.433304-1-alexandre.ghiti@canonical.com/
>
> Thanks.
>
> Regards
> Ley Foon
next prev parent reply other threads:[~2022-06-02 3:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 9:37 arch/riscv: SV48 patch series questions Leyfoon Tan
2022-06-02 3:44 ` Palmer Dabbelt [this message]
2022-06-02 5:43 ` Leyfoon Tan
2022-07-01 2:34 ` Leyfoon Tan
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=mhng-055df44c-3feb-41ae-b8c0-ae3a6489dee1@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=alexandre.ghiti@canonical.com \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.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).