From: "Yao Yongxian" <yxianyao@126.com>
To: "Jan Kiszka" <jan.kiszka@siemens.com>
Cc: greg@embeddedgreg.com, xenomai@lists.linux.dev
Subject: Re:Re: MSI NOT pipeline-safe & Internal error
Date: Wed, 24 Apr 2024 19:56:43 +0800 (CST) [thread overview]
Message-ID: <6c251ca.986e.18f0ff71ba2.Coremail.yxianyao@126.com> (raw)
In-Reply-To: <6644bcdb-5867-452a-9c11-c82014e50b7d@siemens.com>
Hi,
>At 2024-04-24 04:55:46, "Jan Kiszka" <jan.kiszka@siemens.com> wrote:
>On 18.04.24 12:10, Yao Yongxian wrote:
>> Hi,
>>
>>> On Mon, Jan 16, 2023 at 9:44 AM Jan Kiszka <jan.kiszka@siemens.com> wrote:
>>>>
>>>> On 16.01.23 09:40, Yao,Yongxian wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> The following exception occurred when running the kernel(Linux-5.4.180, xenomai-3.2.2) on aarch64 computer.
>>>>> Attachment is startup information and kernel configuration.
>>>>>
>>>>> What caused the exception? Please give me some hints!
>>>>
>>>> Maybe just something like we have in Dovetail already:
>>>>
>>>> https://source.denx.de/Xenomai/linux-dovetail/-/commit/42f44cf859e3525eb26dc090fffa97bfc35e870c
>>>>
>>>> Jan
>>>>
>>>> --
>>>> Siemens AG, Technology
>>>> Competence Center Embedded Linux
>>>>
>>
>>> Have you run the ipipe on this platform before? It looks like you
>>> have an IRQ source that isn't ipipe safe, it may be causing issues
>>> when the IRQ is trying to be handled. I'm not familiar with this
>>> platform. Did you port it to ipipe?
>>
>> It runs on Huawei Taishan Server(CPU: armv8 Kunpeng920).
>> Does xenomai/ipipe/dovetail not support this CPU/server？
>> Does the community have any plans to support it?
>>
>
>I'm not aware of anyone having tried Xenomai on such a server. For some
>in this community, it may even be... tricky to get one even if they
>wanted to.
>
>But I'm sure that any patch written to enable this support will be
>welcome to the dovetail tree - provided that general support is already
>in the upstream kernel.
The upstream kernel should already support this hardware platform.
Using the upstream kernel on this hardware platform is ok,
but applying ipipe/dovetail and xenomai patches to the upstream kernel is problematic.
>Jan
>
>--
>Siemens AG, Technology
>Linux Expert Center
--
Yao Yongxian
next prev parent reply other threads:[~2024-04-24 11:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 10:10 MSI NOT pipeline-safe & Internal error Yao Yongxian
2024-04-23 20:55 ` Jan Kiszka
2024-04-24 11:56 ` Yao Yongxian [this message]
2024-04-24 20:55 ` Jan Kiszka
-- strict thread matches above, loose matches on Subject: below --
2023-01-16 8:40 Yao,Yongxian
2023-01-16 14:44 ` Jan Kiszka
2023-01-16 15:10 ` Greg Gallagher
2023-01-17 5:42 ` Yao,Yongxian
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=6c251ca.986e.18f0ff71ba2.Coremail.yxianyao@126.com \
--to=yxianyao@126.com \
--cc=greg@embeddedgreg.com \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).