From: Leyfoon Tan <leyfoon.tan@starfivetech.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: "alexandre.ghiti@canonical.com" <alexandre.ghiti@canonical.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: arch/riscv: SV48 patch series questions
Date: Fri, 1 Jul 2022 02:34:08 +0000 [thread overview]
Message-ID: <d1d448faad0e421e9a0b4412d46681c5@EXMBX061.cuchost.com> (raw)
In-Reply-To: <e99af0ab0a264aadb77d949c4b73fd57@EXMBX161.cuchost.com>
> -----Original Message-----
> From: Leyfoon Tan
> Sent: Thursday, 2 June, 2022 1:44 PM
> To: 'Palmer Dabbelt' <palmer@dabbelt.com>
> Cc: alexandre.ghiti@canonical.com; linux-riscv@lists.infradead.org; linux-
> kernel@vger.kernel.org
> Subject: RE: arch/riscv: SV48 patch series questions
>
>
>
> > -----Original Message-----
> > From: Palmer Dabbelt <palmer@dabbelt.com>
> > Sent: Thursday, 2 June, 2022 11:44 AM
> > To: Leyfoon Tan <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
> >
> > 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.
> It is not CPU errata.
> RISC-V cpu can have sv39, sv48 or even sv57. If it is a heterogenous system,
> cpu cores in the system might have different sv. Eg: one cpu can be sv39 and
> another core is sv48.
> In this case, auto detection is not work. So, Patch-13 can help in this use case.
>
> >
Hi Palmer
Any further comment for this?
Any chance merging Patch-13 in [1]?
[1] https://patchwork.kernel.org/project/linux-riscv/patch/20211206104657.433304-14-alexandre.ghiti@canonical.com/
Regards
Ley Foon
prev parent reply other threads:[~2022-07-01 2:34 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
2022-06-02 5:43 ` Leyfoon Tan
2022-07-01 2:34 ` Leyfoon Tan [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=d1d448faad0e421e9a0b4412d46681c5@EXMBX061.cuchost.com \
--to=leyfoon.tan@starfivetech.com \
--cc=alexandre.ghiti@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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;
as well as URLs for NNTP newsgroup(s).