All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org, hongzha1 <hongzhan.chen@intel.com>
Subject: Re: [Dovetail] x86 test version available (kernel v5.10)
Date: Sat, 06 Feb 2021 18:23:20 +0100	[thread overview]
Message-ID: <875z35qfef.fsf@xenomai.org> (raw)
In-Reply-To: <46e13cc0-6f1c-65f3-34cc-4a6ea44d00d8@siemens.com>


Jan Kiszka <jan.kiszka@siemens.com> writes:

> On 03.02.21 18:35, Philippe Gerum wrote:
>> 
>> Jan Kiszka <jan.kiszka@siemens.com> writes:
>> 
>>> On 31.01.21 17:06, Philippe Gerum wrote:
>>>>
>>>> The initial port of the Cobalt core to Dovetail/x86 is available from
>>>> [1]. Ports to Dovetail/ARM and Dovetail/arm64 should follow within a
>>>> couple of weeks.
>>>>
>>>> So far, latency and switchtest run flawlessly. Most of the smokey test
>>>> suite passes successfully, except the GDB test at the moment.
>>>>
>>>> How to test this:
>>>>
>>>> - clone Xenomai from [1], switch to branch for-upstream/dovetail
>>>> - clone the Dovetail tree (v5.10) from [2], switch to branch dovetail/master
>>>> - run scripts/prepare-kernel.sh available from [1] into [2] (usual procedure)
>>>>   for x86, that would be: .../scripts/prepare-kernel.sh --arch=x86
>>>> - build your kernel using the sources from [2]
>>>>
>>>> There is no user-visible Kconfig change compared to an I-pipe based
>>>> version.
>>>>
>>>> Alternatively, the Xenomai code base in [1] can also run on top of the
>>>> I-pipe. prepare-kernel.sh detects which pipeline flavour is there, and
>>>> prepares the source tree accordingly.
>>>>
>>>> This code is being gradually merged into Xenomai's -next branch, and
>>>> will be at the core of Xenomai 3.2. Testing and feedback appreciated.
>>>>
>>>> Thanks,
>>>>
>>>> [1] https://lab.xenomai.org/xenomai-rpm.git, "for-upstream/dovetail" branch
>>>> [2] https://git.evlproject.org/linux-evl.git, "dovetail/master" branch
>>>>
>>>
>>> First try on my end looked good as well - great news, well done!
>>>
>>> Would it help to stick the wip branch into our CI/CT?
>>>
>> 
>> Yep, it would. TIA,
>> 
>
> CI build is passing now, see
>
> https://gitlab.denx.de/Xenomai/xenomai/-/pipelines/6258
>
> I'm carrying two fixes and a could of tweaks:
>
> https://gitlab.denx.de/Xenomai/xenomai/-/commits/wip/dovetail
>

I'll pick the trace-related fixes in my queue.

> Specifically
> https://gitlab.denx.de/Xenomai/xenomai/-/commit/4196216e821abea3107284a8e31e13bdf05141d5
> would a second look as the timer ipi abstraction became obsolete with
> the code moving to pipeline-specific code.
>

Yes, moving this to the pipeline-specific section, so that we reduce the
level of visual clutter in the generic code.

> I've just started also target runs, see
> https://gitlab.denx.de/Xenomai/xenomai-images/-/pipelines/6263. There
> will be several known breakages, though, namely the gdb test but also
> the unrelated arm[64]-5.4 regressions.
>

I'm fixing the RTnet build issues ATM.

-- 
Philippe.


  reply	other threads:[~2021-02-06 17:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 16:06 [Dovetail] x86 test version available (kernel v5.10) Philippe Gerum
2021-02-01 17:32 ` Jan Kiszka
2021-02-03 17:35   ` Philippe Gerum
2021-02-06 12:29     ` Jan Kiszka
2021-02-06 17:23       ` Philippe Gerum [this message]
2021-02-15 13:28       ` Jan Kiszka
2021-02-15 15:11         ` Jan Kiszka
2021-02-15 16:53           ` Jan Kiszka
2021-02-15 17:19             ` Jan Kiszka
2021-02-15 17:07           ` Philippe Gerum
2021-02-15 17:21             ` Philippe Gerum
2021-02-22 15:35 ` Henning Schild
2021-02-22 17:59   ` Henning Schild
2021-03-11 16:35   ` Henning Schild
2021-03-12  7:22     ` Jan Kiszka
2021-03-12 11:32       ` Jan Kiszka
2021-03-12 18:18         ` Henning Schild
2021-03-12 19:46           ` Henning Schild
2021-03-12 19:53             ` Henning Schild
2021-03-15  7:57               ` Jan Kiszka

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=875z35qfef.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=hongzhan.chen@intel.com \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.