Hi Song,
On 9/22/21 14:22, Song Gao wrote:
Hi, Richard.
On 09/21/2021 05:17 AM, Richard Henderson wrote:
On 9/17/21 1:12 AM, Song Gao wrote:
The 'o32' code has been deleted at the latest kernel [1]. This series only
support
linux-user emulation.
I have now reviewed all but the linux-user/ portion.
Thank you!
I see that kernel upstreaming is in progress,
https://lore.kernel.org/linux-kernel/20210917035736.3934017-1-chenhua...@loongson.cn/
so hopefully this will be resolved soon.
Have you started working on system mode support for LoongArch, so that one may
run that kernel?
Yes. We already support running the old kernel, but we don't support running
the latest kernel yet.
(the reply was at the wrong quotation level, never mind though)
First of all, thanks for your contribution and continued engagement with
the wider development community! That's what it takes to unlock the
3A5000 and future products' so many possibilities.
As for the system emulation part, I have some questions though:
- How would you provide the necessary firmware bits? Ideally that would
be some open-source reference implementation so people would be able to
collaborate on that front, and to maybe customize for specialized needs
(e.g. ultra-dense cloud use cases like with Firecracker).
- How is old/new kernel ABI affecting your system-level emulation
compatibility? IIUC the underlying ISA and chip behavior should be the
same, only difference would be the firmware-kernel ABI, but again it
should be just a matter of substituting the right image.
- Would the resulting work support emulating both old-world and
new-world systems? AFAIK those commercial distros who're VERY early
adopters of LoongArch are given similarly early toolchains/kernels. They
belong to the old-world as a result, and are very likely to be stuck on
the old-world ABI for whole major versions before migrating, if at all
possible. Closed-source/commercial software also risk being available
only for the old-world, and it would be extremely important to provide
some degree of interoperability so that we don't split the ecosystem.
Questions aside, you did a nice work so far; looking forward to your
system emulation work!
