All of lore.kernel.org
 help / color / mirror / Atom feed
* [Xenomai] High latency and smi with intel vendor chip
       [not found] <mailman.1.1371808801.4609.xenomai@xenomai.org>
@ 2013-06-21 13:07 ` Franz Engel
  2013-06-21 14:00   ` Jan Kiszka
  0 siblings, 1 reply; 8+ messages in thread
From: Franz Engel @ 2013-06-21 13:07 UTC (permalink / raw)
  To: xenomai

Hi,

In my dmesg I get the following message:
dmesg | grep -i xeno
[    4.478964] I-pipe: head domain Xenomai registered.
[    4.494089] Xenomai: hal/x86_64 started.
[    4.505969] Xenomai: scheduling class idle registered.
[    4.521300] Xenomai: scheduling class rt registered.
[    4.538525] Xenomai: real-time nucleus v2.6.2.1 (Day At The Beach) loaded.
[    4.559065] Xenomai: debug mode enabled.
[    4.579351] Xenomai: SMI-enabled chipset found
[    4.592628] Xenomai: SMI workaround failed!
[    4.605677] Xenomai: starting native API services.
[    4.619979] Xenomai: starting POSIX services.
[    4.633088] Xenomai: starting RTDM services.


And I have very high latencies. I read that I should try to insert my the ID of my LCP into the /usr/src/xenomai/ksrc/arch/x86/smi.c file. But I'm not sure how. I would try it like this:
{PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82801JIR_0)}
But I don't know if the "0" is correct. Is the last sign the "rev"? I this case, what is my last sign?

In general, is it a good idea to disable the ISA Bridge with the smi.c file?

What I have to do after modifing this file? Do I have to recompile my kernel, or is it enough to make/make install xenomai?


Thats the output of lcpi:
lspci -n
00:00.0 0600: 8086:3403 (rev 22)
00:01.0 0604: 8086:3408 (rev 22)
00:02.0 0604: 8086:3409 (rev 22)
00:03.0 0604: 8086:340a (rev 22)
00:07.0 0604: 8086:340e (rev 22)
00:08.0 0604: 8086:340f (rev 22)
00:09.0 0604: 8086:3410 (rev 22)
00:0a.0 0604: 8086:3411 (rev 22)
00:10.0 0800: 8086:3425 (rev 22)
00:10.1 0800: 8086:3426 (rev 22)
00:11.0 0800: 8086:3427 (rev 22)
00:11.1 0800: 8086:3428 (rev 22)
00:14.0 0800: 8086:342e (rev 22)
00:14.1 0800: 8086:3422 (rev 22)
00:14.2 0800: 8086:3423 (rev 22)
00:14.3 0800: 8086:3438 (rev 22)
00:16.0 0880: 8086:3430 (rev 22)
00:16.1 0880: 8086:3431 (rev 22)
00:16.2 0880: 8086:3432 (rev 22)
00:16.3 0880: 8086:3433 (rev 22)
00:16.4 0880: 8086:3429 (rev 22)
00:16.5 0880: 8086:342a (rev 22)
00:16.6 0880: 8086:342b (rev 22)
00:16.7 0880: 8086:342c (rev 22)
00:1a.0 0c03: 8086:3a37
00:1a.1 0c03: 8086:3a38
00:1a.7 0c03: 8086:3a3c
00:1b.0 0403: 8086:3a3e
00:1c.0 0604: 8086:3a40
00:1c.4 0604: 8086:3a48
00:1c.5 0604: 8086:3a4a
00:1d.0 0c03: 8086:3a34
00:1d.1 0c03: 8086:3a35
00:1d.2 0c03: 8086:3a36
00:1d.3 0c03: 8086:3a39
00:1d.7 0c03: 8086:3a3a
00:1e.0 0604: 8086:244e (rev 90)
00:1f.0 0601: 8086:3a16
00:1f.2 0101: 8086:3a20
00:1f.3 0c05: 8086:3a30
00:1f.5 0101: 8086:3a26
02:00.0 0200: 8086:10d3
03:00.0 0200: 8086:10d3
08:00.0 0300: 1002:9552
08:00.1 0403: 1002:aa38
09:00.0 0200: 8086:105e (rev 06)
09:00.1 0200: 8086:105e (rev 06)
0b:00.0 0200: 8086:105e (rev 06)
0b:00.1 0200: 8086:105e (rev 06)


lspci -v
00:00.0 Host bridge: Intel Corporation 5500 I/O Hub to ESI Port (rev 22)
    Subsystem: ASUSTeK Computer Inc. Device 8363
    Flags: fast devsel
    Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
    Capabilities: [90] Express Root Port (Slot-), MSI 00
    Capabilities: [e0] Power Management version 3

00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 22) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=0
    I/O behind bridge: 0000e000-0000efff
    Memory behind bridge: fbe00000-fbefffff
    Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Device 8363
    Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
    Capabilities: [90] Express Root Port (Slot+), MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel driver in use: pcieport

00:02.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 2 (rev 22) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0
    Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Device 8363
    Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
    Capabilities: [90] Express Root Port (Slot+), MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel driver in use: pcieport

00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 22) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
    I/O behind bridge: 0000d000-0000dfff
    Memory behind bridge: fbd00000-fbdfffff
    Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Device 8363
    Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
    Capabilities: [90] Express Root Port (Slot+), MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel driver in use: pcieport

00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
    I/O behind bridge: 0000c000-0000cfff
    Memory behind bridge: fbc00000-fbcfffff
    Prefetchable memory behind bridge: 00000000d0000000-00000000dfffffff
    Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Device 8363
    Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
    Capabilities: [90] Express Root Port (Slot+), MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel driver in use: pcieport

00:08.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 8 (rev 22) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=07, subordinate=07, sec-latency=0
    Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Device 8363
    Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
    Capabilities: [90] Express Root Port (Slot+), MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel driver in use: pcieport

00:09.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 22) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
    Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Device 8363
    Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
    Capabilities: [90] Express Root Port (Slot+), MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel driver in use: pcieport

00:0a.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 10 (rev 22) (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
    Capabilities: [40] Subsystem: ASUSTeK Computer Inc. Device 8363
    Capabilities: [60] MSI: Enable- Count=1/2 Maskable+ 64bit-
    Capabilities: [90] Express Root Port (Slot+), MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel driver in use: pcieport

00:10.0 PIC: Intel Corporation 5520/5500/X58 Physical and Link Layer Registers Port 0 (rev 22) (prog-if 00 [8259])
    Subsystem: Device 0043:0063
    Flags: fast devsel
    Capabilities: [50] Vendor Specific Information: Len=ff <?>

00:10.1 PIC: Intel Corporation 5520/5500/X58 Routing and Protocol Layer Registers Port 0 (rev 22) (prog-if 00 [8259])
    Subsystem: Device 0043:0063
    Flags: fast devsel

00:11.0 PIC: Intel Corporation 5520/5500 Physical and Link Layer Registers Port 1 (rev 22) (prog-if 00 [8259])
    Subsystem: Device 0043:0063
    Flags: fast devsel
    Capabilities: [50] Vendor Specific Information: Len=ff <?>

00:11.1 PIC: Intel Corporation 5520/5500 Routing & Protocol Layer Register Port 1 (rev 22) (prog-if 00 [8259])
    Subsystem: Device 0043:0063
    Flags: fast devsel

00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 22) (prog-if 00 [8259])
    Subsystem: Device 0043:0063
    Flags: fast devsel
    Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 22) (prog-if 00 [8259])
    Subsystem: Device 0043:0063
    Flags: fast devsel
    Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 22) (prog-if 00 [8259])
    Subsystem: Device 0043:0063
    Flags: fast devsel
    Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00

00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 22) (prog-if 00 [8259])
    Subsystem: Device 0043:0063
    Flags: fast devsel

00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
    Subsystem: ASUSTeK Computer Inc. Device 8363
    Flags: fast devsel, IRQ 43
    Memory at fb9d8000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [80] MSI-X: Enable- Count=1 Masked-
    Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel modules: ioatdma

00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
    Subsystem: ASUSTeK Computer Inc. Device 8363
    Flags: fast devsel, IRQ 44
    Memory at fb9dc000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [80] MSI-X: Enable- Count=1 Masked-
    Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel modules: ioatdma

00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
    Subsystem: ASUSTeK Computer Inc. Device 8363
    Flags: fast devsel, IRQ 45
    Memory at fb9e0000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [80] MSI-X: Enable- Count=1 Masked-
    Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel modules: ioatdma

00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
    Subsystem: ASUSTeK Computer Inc. Device 8363
    Flags: fast devsel, IRQ 46
    Memory at fb9e4000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [80] MSI-X: Enable- Count=1 Masked-
    Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel modules: ioatdma

00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
    Subsystem: ASUSTeK Computer Inc. Device 8363
    Flags: fast devsel, IRQ 43
    Memory at fb9e8000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [80] MSI-X: Enable- Count=1 Masked-
    Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel modules: ioatdma

00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
    Subsystem: ASUSTeK Computer Inc. Device 8363
    Flags: fast devsel, IRQ 44
    Memory at fb9ec000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [80] MSI-X: Enable- Count=1 Masked-
    Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel modules: ioatdma

00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
    Subsystem: ASUSTeK Computer Inc. Device 8363
    Flags: fast devsel, IRQ 45
    Memory at fb9f0000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [80] MSI-X: Enable- Count=1 Masked-
    Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel modules: ioatdma

00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22)
    Subsystem: ASUSTeK Computer Inc. Device 8363
    Flags: fast devsel, IRQ 46
    Memory at fb9f4000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [80] MSI-X: Enable- Count=1 Masked-
    Capabilities: [90] Express Root Complex Integrated Endpoint, MSI 00
    Capabilities: [e0] Power Management version 3
    Kernel modules: ioatdma

00:1a.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 (prog-if 00 [UHCI])
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, medium devsel, latency 0, IRQ 16
    I/O ports at 7400 [size=32]
    Capabilities: [50] PCI Advanced Features
    Kernel driver in use: uhci_hcd

00:1a.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 (prog-if 00 [UHCI])
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, medium devsel, latency 0, IRQ 21
    I/O ports at 7480 [size=32]
    Capabilities: [50] PCI Advanced Features
    Kernel driver in use: uhci_hcd

00:1a.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 (prog-if 20 [EHCI])
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, medium devsel, latency 0, IRQ 18
    Memory at fb9fd000 (32-bit, non-prefetchable) [size=1K]
    Capabilities: [50] Power Management version 2
    Capabilities: [58] Debug port: BAR=1 offset=00a0
    Capabilities: [98] PCI Advanced Features
    Kernel driver in use: ehci_hcd

00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
    Subsystem: ASUSTeK Computer Inc. Device 82cb
    Flags: bus master, fast devsel, latency 0, IRQ 14
    Memory at fb9f8000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [50] Power Management version 2
    Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00

00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
    I/O behind bridge: 00001000-00001fff
    Memory behind bridge: c0000000-c01fffff
    Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
    Capabilities: [40] Express Root Port (Slot+), MSI 00
    Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
    Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 8363
    Capabilities: [a0] Power Management version 2
    Kernel driver in use: pcieport

00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5 (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
    I/O behind bridge: 0000b000-0000bfff
    Memory behind bridge: fbb00000-fbbfffff
    Prefetchable memory behind bridge: 00000000c0400000-00000000c05fffff
    Capabilities: [40] Express Root Port (Slot+), MSI 00
    Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
    Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 8363
    Capabilities: [a0] Power Management version 2
    Kernel driver in use: pcieport

00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6 (prog-if 00 [Normal decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
    I/O behind bridge: 0000a000-0000afff
    Memory behind bridge: fba00000-fbafffff
    Prefetchable memory behind bridge: 00000000c0600000-00000000c07fffff
    Capabilities: [40] Express Root Port (Slot+), MSI 00
    Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
    Capabilities: [90] Subsystem: ASUSTeK Computer Inc. Device 8363
    Capabilities: [a0] Power Management version 2
    Kernel driver in use: pcieport

00:1d.0 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 (prog-if 00 [UHCI])
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, medium devsel, latency 0, IRQ 23
    I/O ports at 7800 [size=32]
    Capabilities: [50] PCI Advanced Features
    Kernel driver in use: uhci_hcd

00:1d.1 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 (prog-if 00 [UHCI])
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, medium devsel, latency 0, IRQ 19
    I/O ports at 7880 [size=32]
    Capabilities: [50] PCI Advanced Features
    Kernel driver in use: uhci_hcd

00:1d.2 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 (prog-if 00 [UHCI])
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, medium devsel, latency 0, IRQ 18
    I/O ports at 7c00 [size=32]
    Capabilities: [50] PCI Advanced Features
    Kernel driver in use: uhci_hcd

00:1d.3 USB controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 (prog-if 00 [UHCI])
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, medium devsel, latency 0, IRQ 16
    I/O ports at 8000 [size=32]
    Capabilities: [50] PCI Advanced Features
    Kernel driver in use: uhci_hcd

00:1d.7 USB controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 (prog-if 20 [EHCI])
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, medium devsel, latency 0, IRQ 23
    Memory at fb9fe000 (32-bit, non-prefetchable) [size=1K]
    Capabilities: [50] Power Management version 2
    Capabilities: [58] Debug port: BAR=1 offset=00a0
    Capabilities: [98] PCI Advanced Features
    Kernel driver in use: ehci_hcd

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) (prog-if 01 [Subtractive decode])
    Flags: bus master, fast devsel, latency 0
    Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
    Capabilities: [50] Subsystem: ASUSTeK Computer Inc. Device 8363

00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, medium devsel, latency 0
    Capabilities: [e0] Vendor Specific Information: Len=0c <?>
    Kernel modules: lpc_ich

00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port SATA IDE Controller #1 (prog-if 8f [Master SecP SecO PriP PriO])
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 23
    I/O ports at 8c00 [size=8]
    I/O ports at 8880 [size=4]
    I/O ports at 8800 [size=8]
    I/O ports at 8480 [size=4]
    I/O ports at 8400 [size=16]
    I/O ports at 8080 [size=16]
    Capabilities: [70] Power Management version 3
    Capabilities: [b0] PCI Advanced Features
    Kernel driver in use: ata_piix

00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: medium devsel, IRQ 14
    Memory at fb9ff000 (64-bit, non-prefetchable) [size=256]
    I/O ports at 0400 [size=32]
    Kernel modules: i2c-i801

00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port SATA IDE Controller #2 (prog-if 85 [Master SecO PriO])
    Subsystem: ASUSTeK Computer Inc. Device 8362
    Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 21
    I/O ports at 9c00 [size=8]
    I/O ports at 9880 [size=4]
    I/O ports at 9800 [size=8]
    I/O ports at 9480 [size=4]
    I/O ports at 9400 [size=16]
    I/O ports at 9080 [size=16]
    Capabilities: [70] Power Management version 3
    Capabilities: [b0] PCI Advanced Features
    Kernel driver in use: ata_piix

02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
    Subsystem: ASUSTeK Computer Inc. Device 8369
    Flags: bus master, fast devsel, latency 0, IRQ 17
    Memory at fbae0000 (32-bit, non-prefetchable) [size=128K]
    I/O ports at ac00 [size=32]
    Memory at fbadc000 (32-bit, non-prefetchable) [size=16K]
    Capabilities: [c8] Power Management version 2
    Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [e0] Express Endpoint, MSI 00
    Capabilities: [a0] MSI-X: Enable- Count=5 Masked-
    Kernel driver in use: e1000e
    Kernel modules: e1000e

03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
    Subsystem: ASUSTeK Computer Inc. Device 8369
    Flags: bus master, fast devsel, latency 0, IRQ 16
    Memory at fbbe0000 (32-bit, non-prefetchable) [size=128K]
    I/O ports at bc00 [size=32]
    Memory at fbbdc000 (32-bit, non-prefetchable) [size=16K]
    Capabilities: [c8] Power Management version 2
    Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [e0] Express Endpoint, MSI 00
    Capabilities: [a0] MSI-X: Enable- Count=5 Masked-
    Kernel driver in use: e1000e
    Kernel modules: e1000e

08:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV710 [Mobility Radeon HD 4300 Series] (prog-if 00 [VGA controller])
    Subsystem: Giga-byte Technology Device 21ac
    Flags: bus master, fast devsel, latency 0, IRQ 30
    Memory at d0000000 (64-bit, prefetchable) [size=256M]
    Memory at fbcb0000 (64-bit, non-prefetchable) [size=64K]
    I/O ports at c000 [size=256]
    Expansion ROM at fbcc0000 [disabled] [size=128K]
    Capabilities: [50] Power Management version 3
    Capabilities: [58] Express Legacy Endpoint, MSI 00
    Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Kernel driver in use: radeon
    Kernel modules: radeon

08:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI RV710/730 HDMI Audio [Radeon HD 4000 series]
    Subsystem: Giga-byte Technology Device aa38
    Flags: bus master, fast devsel, latency 0, IRQ 5
    Memory at fbcfc000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [50] Power Management version 3
    Capabilities: [58] Express Legacy Endpoint, MSI 00
    Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+

09:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
    Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter
    Flags: bus master, fast devsel, latency 0, IRQ 24
    Memory at fbd80000 (32-bit, non-prefetchable) [size=128K]
    Memory at fbd60000 (32-bit, non-prefetchable) [size=128K]
    I/O ports at d880 [size=32]
    Expansion ROM at fbd40000 [disabled] [size=128K]
    Capabilities: [c8] Power Management version 2
    Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [e0] Express Endpoint, MSI 00
    Kernel driver in use: rt_e1000
    Kernel modules: e1000e

09:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
    Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter
    Flags: bus master, fast devsel, latency 0, IRQ 34
    Memory at fbde0000 (32-bit, non-prefetchable) [size=128K]
    Memory at fbdc0000 (32-bit, non-prefetchable) [size=128K]
    I/O ports at dc00 [size=32]
    Expansion ROM at fbda0000 [disabled] [size=128K]
    Capabilities: [c8] Power Management version 2
    Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [e0] Express Endpoint, MSI 00
    Kernel driver in use: e1000e
    Kernel modules: e1000e

0b:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
    Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter
    Flags: bus master, fast devsel, latency 0, IRQ 28
    Memory at fbe80000 (32-bit, non-prefetchable) [size=128K]
    Memory at fbe60000 (32-bit, non-prefetchable) [size=128K]
    I/O ports at e880 [size=32]
    Expansion ROM at fbe40000 [disabled] [size=128K]
    Capabilities: [c8] Power Management version 2
    Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [e0] Express Endpoint, MSI 00
    Kernel driver in use: rt_e1000
    Kernel modules: e1000e

0b:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
    Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter
    Flags: bus master, fast devsel, latency 0, IRQ 40
    Memory at fbee0000 (32-bit, non-prefetchable) [size=128K]
    Memory at fbec0000 (32-bit, non-prefetchable) [size=128K]
    I/O ports at ec00 [size=32]
    Expansion ROM at fbea0000 [disabled] [size=128K]
    Capabilities: [c8] Power Management version 2
    Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [e0] Express Endpoint, MSI 00
    Kernel driver in use: rt_e1000
    Kernel modules: e1000e

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] High latency and smi with intel vendor chip
  2013-06-21 13:07 ` [Xenomai] High latency and smi with intel vendor chip Franz Engel
@ 2013-06-21 14:00   ` Jan Kiszka
  2013-06-22 11:57     ` Franz Engel
  2013-06-27 18:35     ` Gilles Chanteperdrix
  0 siblings, 2 replies; 8+ messages in thread
From: Jan Kiszka @ 2013-06-21 14:00 UTC (permalink / raw)
  To: Franz Engel; +Cc: xenomai

On 2013-06-21 15:07, Franz Engel wrote:
> Hi,
> 
> In my dmesg I get the following message:
> dmesg | grep -i xeno
> [    4.478964] I-pipe: head domain Xenomai registered.
> [    4.494089] Xenomai: hal/x86_64 started.
> [    4.505969] Xenomai: scheduling class idle registered.
> [    4.521300] Xenomai: scheduling class rt registered.
> [    4.538525] Xenomai: real-time nucleus v2.6.2.1 (Day At The Beach) loaded.
> [    4.559065] Xenomai: debug mode enabled.
> [    4.579351] Xenomai: SMI-enabled chipset found
> [    4.592628] Xenomai: SMI workaround failed!
> [    4.605677] Xenomai: starting native API services.
> [    4.619979] Xenomai: starting POSIX services.
> [    4.633088] Xenomai: starting RTDM services.
> 
> 
> And I have very high latencies. I read that I should try to insert my the ID of my LCP into the /usr/src/xenomai/ksrc/arch/x86/smi.c file.

That is no longer true since 2.6.2.1. Xenomai already detects your LPC
(see above), but the BIOS has apparently locked SMI disabling down.

In this case, you may want to play with smi_mask (see documentation of
"SMI_EN — SMI Control and Enable Register" in the Intel chipset manuals)
to see if disabling of individual SMI features work. If not, the board
is useless for low-latency real-time purposes.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] High latency and smi with intel vendor chip
  2013-06-21 14:00   ` Jan Kiszka
@ 2013-06-22 11:57     ` Franz Engel
  2013-06-24  6:40       ` Jan Kiszka
  2013-06-27 18:35     ` Gilles Chanteperdrix
  1 sibling, 1 reply; 8+ messages in thread
From: Franz Engel @ 2013-06-22 11:57 UTC (permalink / raw)
  To: 'Jan Kiszka'; +Cc: xenomai

Franz Engel wrote:
> Jan Kiszkas wrote:
> > Franz Engel wrote:
> > Hi,
> >
> > In my dmesg I get the following message:
> > dmesg | grep -i xeno
> > [    4.478964] I-pipe: head domain Xenomai registered.
> > [    4.494089] Xenomai: hal/x86_64 started.
> > [    4.505969] Xenomai: scheduling class idle registered.
> > [    4.521300] Xenomai: scheduling class rt registered.
> > [    4.538525] Xenomai: real-time nucleus v2.6.2.1 (Day At The Beach)
> loaded.
> > [    4.559065] Xenomai: debug mode enabled.
> > [    4.579351] Xenomai: SMI-enabled chipset found
> > [    4.592628] Xenomai: SMI workaround failed!
> > [    4.605677] Xenomai: starting native API services.
> > [    4.619979] Xenomai: starting POSIX services.
> > [    4.633088] Xenomai: starting RTDM services.
> >
> >
> > And I have very high latencies. I read that I should try to insert my
> the ID of my LCP into the /usr/src/xenomai/ksrc/arch/x86/smi.c file.
> 
> That is no longer true since 2.6.2.1. Xenomai already detects your LPC
> (see above), but the BIOS has apparently locked SMI disabling down.
> 
> In this case, you may want to play with smi_mask (see documentation of
> "SMI_EN - SMI Control and Enable Register" in the Intel chipset
> manuals) to see if disabling of individual SMI features work. If not,
> the board is useless for low-latency real-time purposes.

I found the documentation for my chipset. But I'm not sure with the
interpretation. I think that chapter 13.8.3.11 "SMI_EN-SMI Control and
Enable Register"
(http://www.intel.com/content/dam/doc/datasheet/io-controller-hub-10-family-
datasheet.pdf) is the chapter that descript the options for SMI. But I don't
know how to interpret it. It would be very nice if somebody could look into
and say me how to understand it and how I can use this information to reduce
my latency (if possible).
> 
> Jan
Franz



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] High latency and smi with intel vendor chip
  2013-06-22 11:57     ` Franz Engel
@ 2013-06-24  6:40       ` Jan Kiszka
  2013-06-24  7:20         ` Jan Kiszka
  0 siblings, 1 reply; 8+ messages in thread
From: Jan Kiszka @ 2013-06-24  6:40 UTC (permalink / raw)
  To: Franz Engel; +Cc: xenomai

On 2013-06-22 13:57, Franz Engel wrote:
> Franz Engel wrote:
>> Jan Kiszkas wrote:
>>> Franz Engel wrote:
>>> Hi,
>>>
>>> In my dmesg I get the following message:
>>> dmesg | grep -i xeno
>>> [    4.478964] I-pipe: head domain Xenomai registered.
>>> [    4.494089] Xenomai: hal/x86_64 started.
>>> [    4.505969] Xenomai: scheduling class idle registered.
>>> [    4.521300] Xenomai: scheduling class rt registered.
>>> [    4.538525] Xenomai: real-time nucleus v2.6.2.1 (Day At The Beach)
>> loaded.
>>> [    4.559065] Xenomai: debug mode enabled.
>>> [    4.579351] Xenomai: SMI-enabled chipset found
>>> [    4.592628] Xenomai: SMI workaround failed!
>>> [    4.605677] Xenomai: starting native API services.
>>> [    4.619979] Xenomai: starting POSIX services.
>>> [    4.633088] Xenomai: starting RTDM services.
>>>
>>>
>>> And I have very high latencies. I read that I should try to insert my
>> the ID of my LCP into the /usr/src/xenomai/ksrc/arch/x86/smi.c file.
>>
>> That is no longer true since 2.6.2.1. Xenomai already detects your LPC
>> (see above), but the BIOS has apparently locked SMI disabling down.
>>
>> In this case, you may want to play with smi_mask (see documentation of
>> "SMI_EN - SMI Control and Enable Register" in the Intel chipset
>> manuals) to see if disabling of individual SMI features work. If not,
>> the board is useless for low-latency real-time purposes.
> 
> I found the documentation for my chipset. But I'm not sure with the
> interpretation. I think that chapter 13.8.3.11 "SMI_EN-SMI Control and
> Enable Register"
> (http://www.intel.com/content/dam/doc/datasheet/io-controller-hub-10-family-
> datasheet.pdf) is the chapter that descript the options for SMI. But I don't
> know how to interpret it. It would be very nice if somebody could look into
> and say me how to understand it and how I can use this information to reduce
> my latency (if possible).

Try to clear bits 18, 17, 14, 13, 11, 6 and 3.

You can also use smictrl [1] for these experiments. Maybe you have to
add your chipset in this case (it still uses explicit chipset listings,
need to port Xenomai's logic over), but you won't have to reboot for this.

Jan

[1] http://git.kiszka.org/?p=smictrl.git;a=summary

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] High latency and smi with intel vendor chip
  2013-06-24  6:40       ` Jan Kiszka
@ 2013-06-24  7:20         ` Jan Kiszka
  2013-06-27 17:26           ` Franz Engel
  0 siblings, 1 reply; 8+ messages in thread
From: Jan Kiszka @ 2013-06-24  7:20 UTC (permalink / raw)
  To: Franz Engel; +Cc: xenomai

On 2013-06-24 08:40, Jan Kiszka wrote:
> On 2013-06-22 13:57, Franz Engel wrote:
>> Franz Engel wrote:
>>> Jan Kiszkas wrote:
>>>> Franz Engel wrote:
>>>> Hi,
>>>>
>>>> In my dmesg I get the following message:
>>>> dmesg | grep -i xeno
>>>> [    4.478964] I-pipe: head domain Xenomai registered.
>>>> [    4.494089] Xenomai: hal/x86_64 started.
>>>> [    4.505969] Xenomai: scheduling class idle registered.
>>>> [    4.521300] Xenomai: scheduling class rt registered.
>>>> [    4.538525] Xenomai: real-time nucleus v2.6.2.1 (Day At The Beach)
>>> loaded.
>>>> [    4.559065] Xenomai: debug mode enabled.
>>>> [    4.579351] Xenomai: SMI-enabled chipset found
>>>> [    4.592628] Xenomai: SMI workaround failed!
>>>> [    4.605677] Xenomai: starting native API services.
>>>> [    4.619979] Xenomai: starting POSIX services.
>>>> [    4.633088] Xenomai: starting RTDM services.
>>>>
>>>>
>>>> And I have very high latencies. I read that I should try to insert my
>>> the ID of my LCP into the /usr/src/xenomai/ksrc/arch/x86/smi.c file.
>>>
>>> That is no longer true since 2.6.2.1. Xenomai already detects your LPC
>>> (see above), but the BIOS has apparently locked SMI disabling down.
>>>
>>> In this case, you may want to play with smi_mask (see documentation of
>>> "SMI_EN - SMI Control and Enable Register" in the Intel chipset
>>> manuals) to see if disabling of individual SMI features work. If not,
>>> the board is useless for low-latency real-time purposes.
>>
>> I found the documentation for my chipset. But I'm not sure with the
>> interpretation. I think that chapter 13.8.3.11 "SMI_EN-SMI Control and
>> Enable Register"
>> (http://www.intel.com/content/dam/doc/datasheet/io-controller-hub-10-family-
>> datasheet.pdf) is the chapter that descript the options for SMI. But I don't
>> know how to interpret it. It would be very nice if somebody could look into
>> and say me how to understand it and how I can use this information to reduce
>> my latency (if possible).
> 
> Try to clear bits 18, 17, 14, 13, 11, 6 and 3.
> 
> You can also use smictrl [1] for these experiments. Maybe you have to
> add your chipset in this case (it still uses explicit chipset listings,
> need to port Xenomai's logic over), but you won't have to reboot for this.

Just removed this limitation, smictrl now works like Xenomai /wrt
detecting compatible chipsets.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] High latency and smi with intel vendor chip
  2013-06-24  7:20         ` Jan Kiszka
@ 2013-06-27 17:26           ` Franz Engel
  2013-06-27 18:51             ` Gilles Chanteperdrix
  0 siblings, 1 reply; 8+ messages in thread
From: Franz Engel @ 2013-06-27 17:26 UTC (permalink / raw)
  To: 'Jan Kiszka'; +Cc: xenomai

> On 2013-06-24 08:40, Jan Kiszka wrote:
> > On 2013-06-22 13:57, Franz Engel wrote:
> >> Franz Engel wrote:
> >>> Jan Kiszkas wrote:
> >>>> Franz Engel wrote:
> >>>> Hi,
> >>>>
> >>>> In my dmesg I get the following message:
> >>>> dmesg | grep -i xeno
> >>>> [    4.478964] I-pipe: head domain Xenomai registered.
> >>>> [    4.494089] Xenomai: hal/x86_64 started.
> >>>> [    4.505969] Xenomai: scheduling class idle registered.
> >>>> [    4.521300] Xenomai: scheduling class rt registered.
> >>>> [    4.538525] Xenomai: real-time nucleus v2.6.2.1 (Day At The
> Beach)
> >>> loaded.
> >>>> [    4.559065] Xenomai: debug mode enabled.
> >>>> [    4.579351] Xenomai: SMI-enabled chipset found
> >>>> [    4.592628] Xenomai: SMI workaround failed!
> >>>> [    4.605677] Xenomai: starting native API services.
> >>>> [    4.619979] Xenomai: starting POSIX services.
> >>>> [    4.633088] Xenomai: starting RTDM services.
> >>>>
> >>>>
> >>>> And I have very high latencies. I read that I should try to insert
> >>>> my
> >>> the ID of my LCP into the /usr/src/xenomai/ksrc/arch/x86/smi.c
> file.
> >>>
> >>> That is no longer true since 2.6.2.1. Xenomai already detects your
> >>> LPC (see above), but the BIOS has apparently locked SMI disabling
> down.
> >>>
> >>> In this case, you may want to play with smi_mask (see documentation
> >>> of "SMI_EN - SMI Control and Enable Register" in the Intel chipset
> >>> manuals) to see if disabling of individual SMI features work. If
> >>> not, the board is useless for low-latency real-time purposes.
> >>
> >> I found the documentation for my chipset. But I'm not sure with the
> >> interpretation. I think that chapter 13.8.3.11 "SMI_EN-SMI Control
> >> and Enable Register"
> >> (http://www.intel.com/content/dam/doc/datasheet/io-controller-hub-
> 10-
> >> family-
> >> datasheet.pdf) is the chapter that descript the options for SMI. But
> >> I don't know how to interpret it. It would be very nice if somebody
> >> could look into and say me how to understand it and how I can use
> >> this information to reduce my latency (if possible).
> >
> > Try to clear bits 18, 17, 14, 13, 11, 6 and 3.
> >
> > You can also use smictrl [1] for these experiments. Maybe you have to
> > add your chipset in this case (it still uses explicit chipset
> > listings, need to port Xenomai's logic over), but you won't have to
> reboot for this.
> 
> Just removed this limitation, smictrl now works like Xenomai /wrt
> detecting compatible chipsets.

I cleared the bits (18, 17, 14, 13, 11, 6 and 3), rather, they were already
cleared. The value of the register was 23. But I have still latencies
between 4us and 90us. Is there a best practice to find out what is the
reason for this latencies?



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] High latency and smi with intel vendor chip
  2013-06-21 14:00   ` Jan Kiszka
  2013-06-22 11:57     ` Franz Engel
@ 2013-06-27 18:35     ` Gilles Chanteperdrix
  1 sibling, 0 replies; 8+ messages in thread
From: Gilles Chanteperdrix @ 2013-06-27 18:35 UTC (permalink / raw)
  To: Jan Kiszka; +Cc: Franz Engel, xenomai

On 06/21/2013 04:00 PM, Jan Kiszka wrote:

> On 2013-06-21 15:07, Franz Engel wrote:
>> Hi,
>>
>> In my dmesg I get the following message:
>> dmesg | grep -i xeno
>> [    4.478964] I-pipe: head domain Xenomai registered.
>> [    4.494089] Xenomai: hal/x86_64 started.
>> [    4.505969] Xenomai: scheduling class idle registered.
>> [    4.521300] Xenomai: scheduling class rt registered.
>> [    4.538525] Xenomai: real-time nucleus v2.6.2.1 (Day At The Beach) loaded.
>> [    4.559065] Xenomai: debug mode enabled.
>> [    4.579351] Xenomai: SMI-enabled chipset found
>> [    4.592628] Xenomai: SMI workaround failed!
>> [    4.605677] Xenomai: starting native API services.
>> [    4.619979] Xenomai: starting POSIX services.
>> [    4.633088] Xenomai: starting RTDM services.
>>
>>
>> And I have very high latencies. I read that I should try to insert my the ID of my LCP into the /usr/src/xenomai/ksrc/arch/x86/smi.c file.
> 
> That is no longer true since 2.6.2.1. Xenomai already detects your LPC
> (see above), but the BIOS has apparently locked SMI disabling down.


This change was made after 2.6.2.1. With 2.6.2.1, it is still necessary
to add the ISA bridge ids to the list.

You do not have to bother if you use the smictrl tool, though.

-- 
                                                                Gilles.


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] High latency and smi with intel vendor chip
  2013-06-27 17:26           ` Franz Engel
@ 2013-06-27 18:51             ` Gilles Chanteperdrix
  0 siblings, 0 replies; 8+ messages in thread
From: Gilles Chanteperdrix @ 2013-06-27 18:51 UTC (permalink / raw)
  To: Franz Engel; +Cc: 'Jan Kiszka', xenomai

On 06/27/2013 07:26 PM, Franz Engel wrote:

> I cleared the bits (18, 17, 14, 13, 11, 6 and 3), rather, they were already
> cleared. The value of the register was 23.


Hi,

You may try to clear all bits except bits 0 and 1. Though, please run
tests, and check for overheating, in case one disabled SMI source is in
fact the fan control.


> But I have still latencies
> between 4us and 90us. Is there a best practice to find out what is the
> reason for this latencies?


First, please tell us which version of Linux you use, with which version
of the I-pipe patch. Then post your kernel configuration. For instance
if you have ACPI and/or USB disabled, you should enable them.

Regards.

-- 
                                                                Gilles.


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2013-06-27 18:51 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <mailman.1.1371808801.4609.xenomai@xenomai.org>
2013-06-21 13:07 ` [Xenomai] High latency and smi with intel vendor chip Franz Engel
2013-06-21 14:00   ` Jan Kiszka
2013-06-22 11:57     ` Franz Engel
2013-06-24  6:40       ` Jan Kiszka
2013-06-24  7:20         ` Jan Kiszka
2013-06-27 17:26           ` Franz Engel
2013-06-27 18:51             ` Gilles Chanteperdrix
2013-06-27 18:35     ` Gilles Chanteperdrix

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.