All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Kernel feature support - architecture options and drivers
Date: Fri, 21 Jul 2017 18:11:11 +0100	[thread overview]
Message-ID: <1500657071.12197.183.camel@codethink.co.uk> (raw)
In-Reply-To: <2b838876-3237-ab6f-4377-0bbbdc7c6e65@siemens.com>

On Fri, 2017-07-21 at 17:19 +0200, Jan Kiszka wrote:
> On 2017-07-21 15:18, Ben Hutchings wrote:
> > Intel Quark support (CONFIG_X86_INTEL_QUARK) is enabled in the
> > siemens_iot2000 config.  Are you really using Quark SoCs?
> 
> Yeah...
> http://w3.siemens.com/mcms/pc-based-automation/en/industrial-iot/pages/default.aspx.
> This revision will stop being shipped at latest in 2020, but there will
> be a lot of these chips in the field until then.
>
> Likely all needed patches will be in 4.13 (just still struggling to get
> userspace software ported from the Intel BSP to mainline). So I'm
> planning to submit the essential patches for CIP integration "soon".

I assume you're aware of erratum #24 affecting the LOCK prefix?  There
seems to be no solution except to use Intel's forked version of binutils
which deletes the LOCK prefix.  I don't know if it's an issue for kernel
code, but probably not - the kernel shouldn't use LOCK if CONFIG_SMP is
not enabled, and in any case shouldn't get a page fault on such an
instruction..

> > uhci-hcd (CONFIG_USB_UHCI_HCD) is for obsolete hardware (so far as I
> > know) but is enabled in the plathome_obsvx1, siemens_server and toshiba
> > x86 configs.  Please disable it.
> 
> You need it for old USB 2.0 chipsets that have separate USB 1.1 and 2.0
> interfaces. Those would then no longer word with 1.1 devices. But I bet
> none of the provided products contain that.

I know there were some UHCI/EHCI pairings but I haven't seen a UHCI in a
long time.

> > KVM (CONFIG_VIRTUALIZATION) adds a large attack surface (guest-to-host)
> > and is likely to be hard to maintain in the long term.  Several of the
> > configurations (hitachi_omap, plathome_obsvx1, siemens_iot2000,
> > siemens_server) enable this.  Do you need it?
> 
> Not on the IOT2000 (f...ine Yocto rules made that pop up, I still need
> to convert to a plain defconfig), not for production purposes on our
> server, but we do have products (not listed so far) with KVM.
> 
> With - buzzword alarm - "edge computing", it is getting more and more
> important as isolation tool for "apps". Containers/namespaces are
> sometimes not strong enough.
[...]

I understand that - just trying to check that is actually being used.

Ben.

-- 
Ben Hutchings
Software Developer, Codethink Ltd.

  reply	other threads:[~2017-07-21 17:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-21 13:18 [cip-dev] Kernel feature support - architecture options and drivers Ben Hutchings
2017-07-21 14:24 ` Agustin Benito Bethencourt
2017-07-21 15:19 ` Jan Kiszka
2017-07-21 17:11   ` Ben Hutchings [this message]
2017-07-21 17:27     ` Jan Kiszka
2017-07-28  4:49 ` 河合英宏 / KAWAI,HIDEHIRO
2017-08-18 13:38   ` Ben Hutchings
2017-08-21  7:46     ` 河合英宏 / KAWAI,HIDEHIRO
2017-08-30  5:59 ` Masato Minda

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=1500657071.12197.183.camel@codethink.co.uk \
    --to=ben.hutchings@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.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.