[cip-dev] Kernel feature support

[cip-dev] Kernel feature support

[Ben Hutchings]

We've previously agreed that not all kernel features (drivers,
filesystems, network protocols, etc.) can be supported in an SLTS
branch.  I'd like to start working out what the supported features
should be for the 4.4 branch.

Are members able to share their kernel .config files, showing which
features are enabled?  Or would you prefer to specify your needs at a
slightly higher level?

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

[cip-dev] Kernel feature support

[Angelo Compagnucci]

Dear Ben Hutchings,

2017-03-09 15:33 GMT+01:00 Ben Hutchings <ben.hutchings@codethink.co.uk>:
> We've previously agreed that not all kernel features (drivers,
> filesystems, network protocols, etc.) can be supported in an SLTS
> branch.  I'd like to start working out what the supported features
> should be for the 4.4 branch.
>
> Are members able to share their kernel .config files, showing which
> features are enabled?  Or would you prefer to specify your needs at a
> slightly higher level?

I would really like to have IIO drivers, they are generally easy to
backport and extremely useful in industrial contexts.

Sincerely, Angelo

>
> Ben.
>
> --
> Ben Hutchings
> Software Developer, Codethink Ltd.
>
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev



-- 
Profile: http://it.linkedin.com/in/compagnucciangelo

[cip-dev] Kernel feature support

[Ben Hutchings]

On Thu, 2017-03-09 at 16:25 +0100, Angelo Compagnucci wrote:
> Dear Ben Hutchings,
> 
> 2017-03-09 15:33 GMT+01:00 Ben Hutchings <ben.hutchings@codethink.co.uk>:
> > We've previously agreed that not all kernel features (drivers,
> > filesystems, network protocols, etc.) can be supported in an SLTS
> > branch.  I'd like to start working out what the supported features
> > should be for the 4.4 branch.
> >
> > Are members able to share their kernel .config files, showing which
> > features are enabled?  Or would you prefer to specify your needs at a
> > slightly higher level?
> 
> I would really like to have IIO drivers, they are generally easy to
> backport and extremely useful in industrial contexts.

But you don't use *all* the IIO drivers, do you?

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

[cip-dev] Kernel feature support

[Ben Hutchings]

On Thu, 2017-03-09 at 18:55 +0000, Ben Hutchings wrote:
> On Thu, 2017-03-09 at 16:25 +0100, Angelo Compagnucci wrote:
> > Dear Ben Hutchings,
> > 
> > 2017-03-09 15:33 GMT+01:00 Ben Hutchings <ben.hutchings@codethink.co.uk>:
> > > We've previously agreed that not all kernel features (drivers,
> > > filesystems, network protocols, etc.) can be supported in an SLTS
> > > branch.  I'd like to start working out what the supported features
> > > should be for the 4.4 branch.
> > >
> > > Are members able to share their kernel .config files, showing which
> > > features are enabled?  Or would you prefer to specify your needs at a
> > > slightly higher level?
> > 
> > I would really like to have IIO drivers, they are generally easy to
> > backport and extremely useful in industrial contexts.
> 
> But you don't use *all* the IIO drivers, do you?

Also, I'm not talking about backports here - only about which of the
existing features in 4.4 will need SLTS.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

[cip-dev] Kernel feature support

[Agustin Benito Bethencourt]

Hi,

On 09/03/17 15:33, Ben Hutchings wrote:
> We've previously agreed that not all kernel features (drivers,
> filesystems, network protocols, etc.) can be supported in an SLTS
> branch.  I'd like to start working out what the supported features
> should be for the 4.4 branch.
>
> Are members able to share their kernel .config files, showing which
> features are enabled?  Or would you prefer to specify your needs at a
> slightly higher level?

Answering this question is important to discard features in 4.4 that are 
not of CIP interest so we can severely reduce the amount of effort that 
we will need to do in terms of fixes analysis, security etc. in the future.

Please take some time to provide feedback.

Best Regards

-- 
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk

[cip-dev] Kernel feature support

[Chris Paterson]

Hello Agustin, Ben,

Sorry for the slow response to your query.

> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-
> bounces at lists.cip-project.org] On Behalf Of Agustin Benito Bethencourt
> Sent: 15 March 2017 16:19
> Hi,
> 
> On 09/03/17 15:33, Ben Hutchings wrote:
> > We've previously agreed that not all kernel features (drivers,
> > filesystems, network protocols, etc.) can be supported in an SLTS
> > branch.  I'd like to start working out what the supported features
> > should be for the 4.4 branch.
> >
> > Are members able to share their kernel .config files, showing which
> > features are enabled?  Or would you prefer to specify your needs at a
> > slightly higher level?

>From an SoC vendor point of view, ideally we'd like the interfaces provided by the reference platform to be included. As support for our CIP reference platform is not yet mainlined, I can't provide the exact .config yet. However it will likely be very similar to shmobile_defconfig [1].

Of course, narrowing down configurations supported by the CIP Kernel should probably be lead more by the end use-cases, but hopefully this is a start.


[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/configs/shmobile_defconfig

Kind regards, Chris

> 
> Answering this question is important to discard features in 4.4 that are not of
> CIP interest so we can severely reduce the amount of effort that we will
> need to do in terms of fixes analysis, security etc. in the future.
> 
> Please take some time to provide feedback.
> 
> Best Regards
> 
> --
> Agustin Benito Bethencourt
> Principal Consultant - FOSS at Codethink agustin.benito at codethink.co.uk
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev

[cip-dev] Kernel feature support

[Ben Hutchings]

On Thu, 2017-03-23 at 16:32 +0000, Chris Paterson wrote:
[...]
> From an SoC vendor point of view, ideally we'd like the interfaces
> provided by the reference platform to be included. As support for our
> CIP reference platform is not yet mainlined, I can't provide the
> exact .config yet. However it will likely be very similar to
> shmobile_defconfig [1].
[...]

Thanks, I'll look through this config.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

[cip-dev] Kernel feature support

[河合英宏 / KAWAI，HIDEHIRO]

Hello Agustin and Ben,

> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Agustin Benito
> On 09/03/17 15:33, Ben Hutchings wrote:
> > We've previously agreed that not all kernel features (drivers,
> > filesystems, network protocols, etc.) can be supported in an SLTS
> > branch.  I'd like to start working out what the supported features
> > should be for the 4.4 branch.
> >
> > Are members able to share their kernel .config files, showing which
> > features are enabled?  Or would you prefer to specify your needs at a
> > slightly higher level?
> 
> Answering this question is important to discard features in 4.4 that are
> not of CIP interest so we can severely reduce the amount of effort that
> we will need to do in terms of fixes analysis, security etc. in the future.
> 
> Please take some time to provide feedback.

I attached a defconfig for one of our products running on 4.4.12.
This config is based on omap2plus_defconfig, and a diff from
omap2plus_defconfig is also attached.

Currently, each config item has not been prioritized yet, and it
may contain non-important items.  Please treat our defconfig
as a reference at this point.

Best regards,

Hidehiro Kawai
Hitachi, Ltd. Research & Development Group

-------------- next part --------------
A non-text attachment was scrubbed...
Name: defconfig
Type: application/octet-stream
Size: 12849 bytes
Desc: defconfig
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20170324/94ee26b4/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: defconfig.diff
Type: application/octet-stream
Size: 20958 bytes
Desc: defconfig.diff
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20170324/94ee26b4/attachment-0003.obj>

[cip-dev] Kernel feature support

[Ben Hutchings]

On Fri, 2017-03-24 at 03:39 +0000, ???? / KAWAI?HIDEHIRO wrote:
[...]
> I attached a defconfig for one of our products running on 4.4.12.
> This config is based on omap2plus_defconfig, and a diff from
> omap2plus_defconfig is also attached.
>
> Currently, each config item has not been prioritized yet, and it
> may contain non-important items.  Please treat our defconfig
> as a reference at this point.

Thanks, this is useful.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

[cip-dev] Kernel feature support

[Gernot Hillier]

On 15.03.2017 17:18, Agustin Benito Bethencourt wrote:
> Hi,
> 
> On 09/03/17 15:33, Ben Hutchings wrote:
>> We've previously agreed that not all kernel features (drivers,
>> filesystems, network protocols, etc.) can be supported in an SLTS
>> branch.  I'd like to start working out what the supported features
>> should be for the 4.4 branch.
>>
>> Are members able to share their kernel .config files, showing which
>> features are enabled?  Or would you prefer to specify your needs at a
>> slightly higher level?
> 
> Answering this question is important to discard features in 4.4 that are
> not of CIP interest so we can severely reduce the amount of effort that
> we will need to do in terms of fixes analysis, security etc. in the future.
> 
> Please take some time to provide feedback.

Sorry for the late reply!

Please find attached an x86 kernel configuration from early product
development using kernel 4.4.

This product uses nearly-COTS server hardware due to needed computation
power, but also comes with nice embedded requirements like longterm
maintenance - and as a special need, real-time support, so we use
Linux-Ipipe/Xenomai here.

This means two things:
* many included drivers (especially in net and storage) are only
  activated "to be prepared" for future hw replacements
* Feel free to either include Xenomai on your list as a used "kernel
  feature" or to ignore the related options.

So same as with the config from Hidehiro Kawai: please let me know if
you need prioritized list of drivers or other features!

-- 
Kind regards,
Gernot Hillier

Siemens AG, Corporate Competence Center Embedded Linux

-------------- next part --------------
A non-text attachment was scrubbed...
Name: defconfig.gz
Type: application/gzip
Size: 5167 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20170327/8a5d0701/attachment.bin>

[cip-dev] Kernel feature support

[Jan Kiszka]

On 2017-03-27 12:31, Gernot Hillier wrote:
> On 15.03.2017 17:18, Agustin Benito Bethencourt wrote:
>> Hi,
>>
>> On 09/03/17 15:33, Ben Hutchings wrote:
>>> We've previously agreed that not all kernel features (drivers,
>>> filesystems, network protocols, etc.) can be supported in an SLTS
>>> branch.  I'd like to start working out what the supported features
>>> should be for the 4.4 branch.
>>>
>>> Are members able to share their kernel .config files, showing which
>>> features are enabled?  Or would you prefer to specify your needs at a
>>> slightly higher level?
>>
>> Answering this question is important to discard features in 4.4 that are
>> not of CIP interest so we can severely reduce the amount of effort that
>> we will need to do in terms of fixes analysis, security etc. in the future.
>>
>> Please take some time to provide feedback.
> 
> Sorry for the late reply!

Fell through my cracks as well, just sending out another internal call
for more product configs. One is attached already, derived from
github.com/siemens/meta-iot2000.

> 
> Please find attached an x86 kernel configuration from early product
> development using kernel 4.4.
> 
> This product uses nearly-COTS server hardware due to needed computation
> power, but also comes with nice embedded requirements like longterm
> maintenance - and as a special need, real-time support, so we use
> Linux-Ipipe/Xenomai here.
> 
> This means two things:
> * many included drivers (especially in net and storage) are only
>   activated "to be prepared" for future hw replacements
> * Feel free to either include Xenomai on your list as a used "kernel
>   feature" or to ignore the related options.

Xenomai is not in CIP scope right now (though Siemens would welcome
anyone interested in collaborating on it).

In general, anything in a config not part of upstream is filtered out
"automatically", I would say. There are switches for out-of-tree
features in the iot2000 config as well (we are still in the process of
upstreaming).

> 
> So same as with the config from Hidehiro Kawai: please let me know if
> you need prioritized list of drivers or other features!
> 

Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.bz2
Type: application/x-bzip
Size: 21169 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20170327/64a8370d/attachment-0001.bin>

[cip-dev] Kernel feature support

[Daniel Sangorrin]

Hi Ben,

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Ben Hutchings
> Sent: Thursday, March 09, 2017 11:34 PM
> To: cip-dev at lists.cip-project.org
> Subject: [cip-dev] Kernel feature support
> 
> We've previously agreed that not all kernel features (drivers,
> filesystems, network protocols, etc.) can be supported in an SLTS
> branch.  I'd like to start working out what the supported features
> should be for the 4.4 branch.
> 
> Are members able to share their kernel .config files, showing which
> features are enabled? 

Please find attached to this e-mail four kernel v4.4 configurations for different architectures and platforms. Some of these kernels contain vendor patches and the PREEMPT RT patch. Also, please note that they were created with 'make ARCH=xxx savedefconfig'.

> Or would you prefer to specify your needs at a
> slightly higher level?

I prepared a list of kernel config options that I consider the most important among the configs we are using. You can find them in the file config-cip (included in the attached zip file) which is reproduced below:

General setup
  CONFIG_POSIX_MQUEUE
  CONFIG_HZ_PERIODIC
  CONFIG_HIGH_RES_TIMERS
  CONFIG_IKCONFIG
  CONFIG_IKCONFIG_PROC
  CONFIG_CGROUPS
  CONFIG_CPUSETS
  CONFIG_NAMESPACES
  CONFIG_SCHED_AUTOGROUP
  CONFIG_BLK_DEV_INITRD
  CONFIG_RD_GZIP
  CONFIG_SHMEM
  CONFIG_SYSCTL_SYSCALL
  CONFIG_KPROBES

Processor type and features
  CONFIG_SMP
  CONFIG_EFI
  CONFIG_HOTPLUG_CPU
  CONFIG_CRASH_DUMP

System type
  CONFIG_ARCH_TEGRA
  CONFIG_ARCH_ZYNQ

Filesystems
  CONFIG_EXT4_FS
  CONFIG_INOTIFY_USER
  CONFIG_OVERLAY_FS
  CONFIG_VFAT_FS
  CONFIG_PROC_FS
  CONFIG_SYSFS
  CONFIG_TMPFS
  CONFIG_SQUASHFS
  CONFIG_JFFS2_FS

Networking support
  CONFIG_INET
  CONFIG_VLAN_8021Q
  CONFIG_IPV6

Device drivers
  CONFIG_UIO
  CONFIG_UIO_PDRV_GENIRQ
  CONFIG_USB_EHCI_HCD
  CONFIG_USB_XHCI_HCD
  CONFIG_USB_STORAGE
  CONFIG_USB_HID
  CONFIG_USB_NET_DRIVERS
  CONFIG_FB
  CONFIG_TUN
  CONFIG_DEVTMPFS
  CONFIG_DEVTMPFS_MOUNT
  CONFIG_GPIOLIB
  CONFIG_GPIO_SYSFS
  CONFIG_GPIOLIB_IRQCHIP
  CONFIG_BLK_DEV_RAM
  CONFIG_MTD
  CONFIG_MTD_BLOCK
  CONFIG_MTD_NAND
  CONFIG_I2C
  CONFIG_SPI
  CONFIG_MMC
  CONFIG_MMC_SDHCI
  CONFIG_INPUT_EVDEV
  CONFIG_PPS
  CONFIG_E1000E
  CONFIG_I40E
  CONFIG_IGB

Kernel hacking
  CONFIG_FTRACE
  CONFIG_FUNCTION_TRACER
  CONFIG_PRINTK_TIME
  CONFIG_PANIC_ON_OOPS

Some of these kernel config options may be out of scope or too broad. I just provide them for reference.
We may send you more information in the future.

Best regards,
Daniel

--
IoT Technology center
Toshiba Corp. Industrial ICT solutions, 
Daniel SANGORRIN
	


-------------- next part --------------
A non-text attachment was scrubbed...
Name: cip-configs.zip
Type: application/octet-stream
Size: 7544 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20170328/95188efc/attachment.obj>

[cip-dev] Kernel feature support

[Jan Kiszka]

On 2017-03-09 15:33, Ben Hutchings wrote:
> We've previously agreed that not all kernel features (drivers,
> filesystems, network protocols, etc.) can be supported in an SLTS
> branch.  I'd like to start working out what the supported features
> should be for the 4.4 branch.
> 
> Are members able to share their kernel .config files, showing which
> features are enabled?  Or would you prefer to specify your needs at a
> slightly higher level?

Some more configs from our side. Some are just stripped-down defconfigs,
some are 4.1-based (to become 4.4 eventually), but I hope they are
useful. Any out-of-tree switch is to be ignored, of course.

I hope there will be more configs in the future. E.g., some projects on
4.4 are still running an expanded development feature set.

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: configs.tar.xz
Type: application/x-xz
Size: 48900 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20170412/06b0ec9b/attachment-0001.xz>

[cip-dev] Kernel feature support

[Masato Minda]

Dear Ben;

I apologize for the very late submission. Here is the config of our product.

Thanks in advance.

--
Masato Minda <minmin@plathome.co.jp>
Plat'Home Co., Ltd.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20170413/3b9899c9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: plathome-obsvx1-config.gz
Type: application/x-gzip
Size: 29351 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20170413/3b9899c9/attachment-0001.gz>

[cip-dev] Kernel feature support

[Wes Huang (黃淵河)]

Hi,

Sorry for the late reply.

Please find attached a Moxa kernel configuration using CIP kernel 4.4.

Best regards,

Wes Huang
Software R&D
Moxa Systems
Tel : 886-2-8919-1230 Ext.7718
Fax: 886-2-8919-1231
Wes.Huang at moxa.com
[Moxa_Logo]
This email and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this email. Any unauthorized duplication, utilization, disclosure, or distribution of the material in this email and its attached files is strictly forbidden.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180331/3d025eed/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2354 bytes
Desc: image001.gif
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180331/3d025eed/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: moxa_defconfig
Type: application/octet-stream
Size: 105998 bytes
Desc: moxa_defconfig
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180331/3d025eed/attachment-0001.obj>

[cip-dev] Kernel feature support

[Daniel Sangorrin]

Dear Wes,

Could you use generate a defconfig from your .config to see the options that you have enabled or modified more clearly?

$ make savedefconfig
$ less defconfig

Thanks,
Daniel

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Wes Huang (???)
> Sent: Saturday, March 31, 2018 4:56 PM
> To: cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] Kernel feature support
> 
> Hi,
> 
> 
> 
> Sorry for the late reply.
> 
> 
> 
> Please find attached a Moxa kernel configuration using CIP kernel 4.4.
> 
> 
> 
> Best regards,
> 
> 
> 
> Wes Huang
> 
> Software R&D
> 
> Moxa Systems
> 
> Tel : 886-2-8919-1230 Ext.7718
> 
> Fax: 886-2-8919-1231
> 
> Wes.Huang at moxa.com
> 
> 
> This email and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have
> received this e-mail in error) please notify the sender immediately and destroy this email. Any unauthorized duplication, utilization,
> disclosure, or distribution of the material in this email and its attached files is strictly forbidden.
> 
> 

[cip-dev] Kernel feature support

[Wes Huang (黃淵河)]

Hi Daniel,

Please refer to attached file. Thanks!

Hi Zoran,

Thanks for your kind reminder. Here is the new one.

Best regards, 

Wes Huang
Software R&D
Moxa Systems
Tel : 886-2-8919-1230 Ext.7718
Fax: 886-2-8919-1231
Wes.Huang at moxa.com

This email and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this email. Any unauthorized duplication, utilization, disclosure, or distribution of the material in this email and its attached files is strictly forbidden. 


-----Original Message-----
From: Daniel Sangorrin [mailto:daniel.sangorrin at toshiba.co.jp] 
Sent: Monday, April 02, 2018 11:20 AM
To: Wes Huang (???); cip-dev at lists.cip-project.org
Subject: RE: [cip-dev] Kernel feature support

Dear Wes,

Could you use generate a defconfig from your .config to see the options that you have enabled or modified more clearly?

$ make savedefconfig
$ less defconfig

Thanks,
Daniel

> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org 
> [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Wes Huang 
> (???)
> Sent: Saturday, March 31, 2018 4:56 PM
> To: cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] Kernel feature support
> 
> Hi,
> 
> 
> 
> Sorry for the late reply.
> 
> 
> 
> Please find attached a Moxa kernel configuration using CIP kernel 4.4.
> 
> 
> 
> Best regards,
> 
> 
> 
> Wes Huang
> 
> Software R&D
> 
> Moxa Systems
> 
> Tel : 886-2-8919-1230 Ext.7718
> 
> Fax: 886-2-8919-1231
> 
> Wes.Huang at moxa.com
> 
> 
> This email and any attached files may contain confidential and/or 
> privileged information. If you are not the intended recipient (or have 
> received this e-mail in error) please notify the sender immediately and destroy this email. Any unauthorized duplication, utilization, disclosure, or distribution of the material in this email and its attached files is strictly forbidden.
> 
> 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: moxa_defconfig
Type: application/octet-stream
Size: 27984 bytes
Desc: moxa_defconfig
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180402/75b95ba4/attachment-0001.obj>

[cip-dev] Kernel feature support

[Zoran S]

Hello Wes,

> CONFIG_ARCH_NR_GPIO=0
> CONFIG_HAVE_PREEMPT_LAZY=y
*> CONFIG_PREEMPT_NONE=y*
> # CONFIG_PREEMPT_VOLUNTARY is not set
> # CONFIG_PREEMPT__LL is not set
> # CONFIG_PREEMPT_RTB is not set
*> # CONFIG_PREEMPT_RT_FULL is not set*
> CONFIG_HZ_FIXED=0

You should refine your rt criterion. IMHO.

Zoran
_______

On Sat, Mar 31, 2018 at 9:56 AM, Wes Huang (???) <Wes.Huang@moxa.com> wrote:

> Hi,
>
>
>
> Sorry for the late reply.
>
>
>
> Please find attached a Moxa kernel configuration using CIP kernel 4.4.
>
>
>
> *Best regards, *
>
>
>
> *Wes Huang*
>
> Software R&D
>
> *Moxa Systems*
>
> *Tel : 886-2-8919-1230 Ext.7718*
>
> *Fax: 886-2-8919-1231*
>
> Wes.Huang at moxa.com
>
> [image: Moxa_Logo]
> This email and any attached files may contain confidential and/or
> privileged information. If you are not the intended recipient (or have
> received this e-mail in error) please notify the sender immediately and
> destroy this email. Any unauthorized duplication, utilization, disclosure,
> or distribution of the material in this email and its attached files is
> strictly forbidden.
>
>
>
> _______________________________________________
> cip-dev mailing list
> cip-dev at lists.cip-project.org
> https://lists.cip-project.org/mailman/listinfo/cip-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180402/2ae8739e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 2354 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20180402/2ae8739e/attachment.gif>

[cip-dev] Kernel feature support

[Ben Hutchings]

On Sat, 2018-03-31 at 07:56 +0000, Wes Huang (???) wrote:
> Hi,
> ?
> Sorry for the late reply.
> ?
> Please find attached a Moxa kernel configuration using CIP kernel
> 4.4.

Thanks, I've added that to my collection.

(I should really put these up on Gitlab somewhere.)

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

[cip-dev] Kernel feature support

[Ben Hutchings]

On Sat, 2018-03-31 at 07:56 +0000, Wes Huang (???) wrote:
> Hi,
> ?
> Sorry for the late reply.
> ?
> Please find attached a Moxa kernel configuration using CIP kernel
> 4.4.

And sorry for this extremely late response.

I will recommend disabling various features.  I recognise that you may
have applications that already require the features, and it may be
impractical to change that.  But you should consider seriously that
they may reduce the long-term security and reliability of those
applications.

Filesystems: I recommend disabling btrfs (CONFIG_BTRFS_FS), ceph
(CONFIG_CEPH_LIB, CONFIG_CEPH_FS), cifs (CONFIG_CIFS_FS), nfs
(CONFIG_NFS_FS, CONFIG_NFSD), ntfs (CONFIG_NTFS_FS), and xfs
(CONFIG_XFS_FS), for the reasons given in
<https://lists.cip-project.org/pipermail/cip-dev/2017-May/000263.html>.
I would add to that list afs (CONFIG_AFS_FS), coda (CONFIG_CODA_FS),
gfs2 (CONFIG_GFS2_FS), ncpfs (CONFIG_NCPFS_FS), and ocfs2
(CONFIG_OCFS2_FS) which have the same issue as the other network
filesystems.

Network protocols: I recommend disabling batman-adv
(CONFIG_BATMAN_ADV), dcb (CONFIG_DCB), hsr (CONFIG_HSR), phonet
(CONFIG_PHONET), sctp (CONFIG_IP_SCTP), for the reasons given in
<https://lists.cip-project.org/pipermail/cip-dev/2017-May/000263.html>.
I would now add to the list dccp (CONFIG_IP_DCCP), which has a poor
security record.

Storage drivers: I recommend disabling dm-cache (CONFIG_DM_CACHE),
dm-switch (CONFIG_DM_SWITCH), MD multipath (CONFIG_MD_MULTIPATH) for
the reasons given in
<https://lists.cip-project.org/pipermail/cip-dev/2017-July/000387.html>.

Network drivers: I recommend disabling USB-attached network drivers
and wireless networking if possible, for the reasons given in
<https://lists.cip-project.org/pipermail/cip-dev/2017-July/000387.html>.

I recommend disabling CONFIG_DEVKMEM and CONFIG_DEVMEM, for the reasons
given in
<https://lists.cip-project.org/pipermail/cip-dev/2017-July/000387.html>.

I recommend enabling the kernel stack protector (either
CONFIG_CC_STACKPROTECTOR_REGULAR or CONFIG_CC_STACKPROTECTOR_STRONG)
and enabling heap address randomisation for user-space by default, by
*disabling* CONFIG_COMPAT_BRK.

I recommend enabling module symbol versioning (CONFIG_MODVERSIONS) in
order to catch mistakes.

Since you have CONFIG_PERF_EVENTS enabled, consider restricting use of
performance events to privileged users.  (This requires a patch that
was not accepted upstream, so unfortunately it's not suitable for CIP
kernel branches.  It's in the Debian and Android kernel sources.)

I recommend disabling obsolete system calls (CONFIG_SYSFS_SYSCALL,
CONFIG_UID16, and CONFIG_USELIB).

You have user namespaces (CONFIG_USER_NS) enabled.  Consider disabling
it or restricting creation of user namespaces to privileged users. 
(This also requires a patch that was not accepted upstream.  It's in
the Debian kernel sources.)

I recommend enabling linked list debug checks (CONFIG_LIST_DEBUG),
which can make it harder to exploit some bugs.

I recommend disabling timer statistics (CONFIG_TIMER_STATS).  This
feature has been removed upstream, so is not maintainable.??Apparently
there are tracepoints that provide similar functionality.?

Ben. 

-- 
Ben Hutchings, Software Developer                ?        Codethink Ltd
https://www.codethink.co.uk/                 Dale House, 35 Dale Street
                                     Manchester, M1 2HF, United Kingdom