SMI tuning

--===============9013810833573969760==
Content-Type: multipart/alternative; boundary="f403045c29286e6703056620e75f"

--f403045c29286e6703056620e75f
Content-Type: text/plain; charset="UTF-8"

I am moving to a new hardware platform due to obsolescence issues and
testing the latency with the kern/latency app shows some mostly 10-22usec
ovl max but some occasional large spikes (2msec).  In the past I have used
rtai_smi module to fix this type problem and now I have added the new Intel
SMI chipset but and unable to mask the SMI bits.  This motherboard contains:

Intel(R) Xeon(R) W-2133 CPU @ 3.60GHz -- Skylake
Intel C422 chipset

When I load the rtai_smi module, I see:

[ 2386.756382] RTAI: Intel SMI chipset found (8086:a2d3), enabling SMI
workaround.
[ 2386.756409] Bits enabled: GBL_SMI, EOS (special), MCSMI, TCO, PERIODIC,
LEGACY_USB2, INTEL_USB2.
[ 2386.756411] Original SMI configuration value 0xffffff03 has been cleared
with mask = 0x1 (saved mask setting 0x1), new value 0
xffffff03.
[ 2386.756413] Bits enabled: GBL_SMI, EOS (special), MCSMI, TCO, PERIODIC,
LEGACY_USB2, INTEL_USB2.

Does anyone have experience with these new chipsets?

Regards,
Wm

--f403045c29286e6703056620e75f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I am moving to a new hardware platform due to obsolescence=
 issues and testing the latency with the kern/latency app shows some mostly=
 10-22usec ovl max but some occasional large spikes (2msec).=C2=A0 In the p=
ast I have used rtai_smi module to fix this type problem and now I have add=
ed the new Intel SMI chipset but and unable to mask the SMI bits.=C2=A0 Thi=
s motherboard contains:<div><br></div><div>Intel(R) Xeon(R) W-2133 CPU @ 3.=
60GHz -- Skylake<br></div><div>Intel C422 chipset</div><div><br></div><div>=
When I load the rtai_smi module, I see:</div><div><br></div><div><div>[ 238=
6.756382] RTAI: Intel SMI chipset found (8086:a2d3), enabling SMI workaroun=
d.</div><div>[ 2386.756409] Bits enabled: GBL_SMI, EOS (special), MCSMI, TC=
O, PERIODIC, LEGACY_USB2, INTEL_USB2.</div><div>[ 2386.756411] Original SMI=
 configuration value 0xffffff03 has been cleared with mask =3D 0x1 (saved m=
ask setting 0x1), new value 0</div><div>xffffff03.</div><div>[ 2386.756413]=
 Bits enabled: GBL_SMI, EOS (special), MCSMI, TCO, PERIODIC, LEGACY_USB2, I=
NTEL_USB2.</div></div><div><br></div><div>Does anyone have experience with =
these new chipsets?</div><div><br></div><div>Regards,</div><div>Wm</div></d=
iv>

--f403045c29286e6703056620e75f--

--===============9013810833573969760==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Rtai mailing list
[email protected]
https://mail.rtai.org/cgi-bin/mailman/listinfo/rtai
--===============9013810833573969760==--