From: Kaiyang Wu <wukaiyang2003@gmail.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>, pve-devel@lists.proxmox.com
Cc: jeffbaichina@gmail.com
Subject: SPAM: Re: Upstream Support for LoongArch
Date: Tue, 26 May 2026 17:32:32 +0800 [thread overview]
Message-ID: <8c746061-b7b2-423c-8489-21c1a820b05c@gmail.com> (raw)
In-Reply-To: <3af17bf6-decc-4b29-9872-25bb3abcb88b@proxmox.com>
Hi Thomas,
We are glad to see your interest in the architecture.
While we currently do not have any European vendors, we are able to
supply Loongson hardware in reasonably efficient manner, see:
https://loongfans.cn/en/intro#i-m-sold-where-can-i-buy-one
But yes, we are indeed working on supporting more overseas vendors for
LoongArch hardware. In the mean time, We will continuously maintain the
unofficial port and align it to the upstream maintenance guidelines and
idioms. Thank you for the feedback!
Best,
Kaiyang Wu
Thomas Lamprecht 於 2026/5/26 17:12 寫道:
> Hello,
>
> Am 25.05.26 um 05:17 schrieb Kaiyang Wu:
>> LoongArch is a new RISC ISA developed by Loongson Technology. The Loongson 3 family supports virtualization via the LVZ extension, and while the Loongson 2 family of SoCs do not support virtualization, they are capable of running containerized applications via LXC. The performance of the latest mainstream server processor, Loongson 3C6000/S, is about equivalent to an AMD Ryzen 7 5700 and, the latest Loongson 2 SoC, 2K3000, is about equivalent to an Intel N95. This means that Loongson's mainstream processors are capable of hosting Proxmox VE instances.
>
> Interesting, I could only find these benchmarks [0] which are relatively recent.
> It doesn't shows that great performance, albeit it's probably not the best available HW the best/newest HW.
> FWIW, for us having recent and good server-class HW available globally is a key requirement before we can consider any official support.
> And here I don't just mean that you can send us some (test) system or the like, but that some - e.g. European - vendors provide this relatively hassle free, as then we and our end users here can buy it.
>
> [0]: https://www.phoronix.com/review/loongson-3b6000-loongarch
>
>> There is an existing unofficial port of Proxmox VE 9.0 to LoongArch maintained by Lierfang (https://github.com/jiangcuo/pxvirt). While we recognize their effort on maintaining the port, the repository has not been actively maintained for 8 months. We do not plan on using their patchset and will maintain our own in order to align them for upstreaming.
>>
>> We would like to seek chances to support LoongArch officially by Proxmox in the future. Loongson Hobbyists Community (https://loongfans.cn/en/) will provide long term support for the LoongArch port. If needed, we will be able to supply LoongArch devices for testing. To support the upstream work, we would like to know about the current workflow for managing patches, maintenance, and testing process. We are happy to answer any of your questions or comments.
>
> LoongArch does seem interesting and made great steps to become a powerful architecture.
> We will definitively keep an eye out and revisit it in the Future, that said, for now we do not plan to actively work on an official version from our side.
> I think the next best time to revisit this topic might be in about a year and a few months, then the next major release should be released, and with that also ideally the support status in upstream Debian better - which would help a lot - and maybe even some newer HW available.
>
> Thanks again for your interest, if there are contained patches for improving multi-arch support that helps your downstream port, we are happy to check them out and if non-invasive will also apply them already.
>
> best regards,
> Thomas
>
prev parent reply other threads:[~2026-05-26 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 3:16 Upstream Support for LoongArch Kaiyang Wu
2026-05-26 9:12 ` Thomas Lamprecht
2026-05-26 9:32 ` Kaiyang Wu [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=8c746061-b7b2-423c-8489-21c1a820b05c@gmail.com \
--to=wukaiyang2003@gmail.com \
--cc=jeffbaichina@gmail.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.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