From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
To: Chris Paterson <Chris.Paterson2@renesas.com>,
"Kiszka, Jan (CT RDA IOT SES-DE)" <jan.kiszka@siemens.com>,
"Schilling,
Benjamin (MO MM R&D SYS SEC)" <schilling.benjamin@siemens.com>,
"dinesh.kumar@toshiba-tsip.com" <dinesh.kumar@toshiba-tsip.com>,
Nobuhiro Iwamatsu <iwamatsu@nigauri.org>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] Generic x86 kernel configration
Date: Mon, 13 May 2024 12:34:37 +0200 [thread overview]
Message-ID: <302fc487-5d23-480f-b79f-32d7dd140d5e@siemens.com> (raw)
In-Reply-To: <TYWPR01MB1186261BB1B3D572F59B287E5B7E52@TYWPR01MB11862.jpnprd01.prod.outlook.com>
On 5/8/24 6:00 PM, Chris Paterson wrote:
> Hello Quirin,
>
> Thank you for your work on this.
>
>> From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
>> Sent: Friday, May 3, 2024 4:58 PM
>>
>> Dear all,
>>
>> I have used a forked version of [1], which you can find here[2] to
>> merge the following x86 kernel configs together:
>>
>> cip-kernel-config/5.10.y-cip/x86/siemens_server_defconfig'
>> cip-kernel-config/5.10.y-cip/x86/toshiba_atom_baytrail_cip_defconfig'
>> cip-kernel-config/5.10.y-cip/x86/siemens_ipc127e_defconfig'
>> cip-kernel-config/5.10.y-cip/x86/plathome_obsvx2_defconfig'
>> cip-kernel-config/5.10.y-cip/x86/cip_qemu_defconfig'
>> cip-kernel-config/5.10.y-cip/x86/siemens_ipc227e_defconfig'
>> cip-kernel-config/5.10.y-cip/x86/siemens_iot2000_defconfig'
>> cip_core_merge_kernel_config/recipes-kernel/linux/files/mcom.cfg'
>>
>>
>> I have tested the v5.10.214-cip46 version of the config with qemu-amd64.
>> The next step would be to check it in the cip lab on the real hardware.
>>
>> The script takes the Kconfig entries of the specific kernel version into
>> account. It also adds all dependencies to the config. You can find to
>> log of the merge at [3] and the diffs to each configuration at [4].
>>
>> An first integration into cip-core can be found at [5].
>>
>> Any comments from your side?
>
> I had a go at building/boot testing the linux-cip 6.1 kernel in our GitLab CI setup using your merged config:
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1283476801
>
> It built and booted okay on the ipc227e.
> However, it didn't boot on the qemu setup in our LAVA lab:
> https://lava.ciplatform.org/scheduler/job/1129968
> "This kernel requires the following features not present on the CPU: movbe"
>
> I don't know if that's an issue with our qemu setup or with the kernel config.
This comes from CONFIG_MATOM which is set by the toshiba configuration.
Quirin
>
> Kind regards, Chris
prev parent reply other threads:[~2024-05-13 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 15:58 [cip-dev] Generic x86 kernel configration Gylstorff Quirin
2024-05-08 16:00 ` Chris Paterson
2024-05-08 16:03 ` Jan Kiszka
2024-05-08 16:16 ` quirin.gylstorff
2024-05-09 8:54 ` Shivanand.Kunijadar
2024-05-14 8:24 ` Gylstorff Quirin
2024-05-14 8:28 ` Gylstorff Quirin
2024-05-13 10:34 ` Gylstorff Quirin [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=302fc487-5d23-480f-b79f-32d7dd140d5e@siemens.com \
--to=quirin.gylstorff@siemens.com \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=iwamatsu@nigauri.org \
--cc=jan.kiszka@siemens.com \
--cc=schilling.benjamin@siemens.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 read-only IMAP folder(s) and NNTP newsgroup(s).