Displaying 11 results from an estimated 11 matches for "cpu22".
Did you mean:
cpu2
2014 Aug 04
1
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
...ivial network thins,
> and others to transmit/receive data.
>
> So, in this case, it seems to driver need to touch the IRQ numbers.
>
> wr-linux:~ # cat /proc/interrupts
> CPU0 CPU1 CPU2 .... CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23
> ......
> 100: 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0
> 101: 2 0 0 0 0 0 302830488 0 0...
2014 Aug 04
1
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
...ivial network thins,
> and others to transmit/receive data.
>
> So, in this case, it seems to driver need to touch the IRQ numbers.
>
> wr-linux:~ # cat /proc/interrupts
> CPU0 CPU1 CPU2 .... CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23
> ......
> 100: 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0
> 101: 2 0 0 0 0 0 302830488 0 0...
2014 Aug 01
2
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
On Wednesday 30 July 2014, Yijing Wang wrote:
> >>>
> >>> The other part I'm not completely sure about is how you want to
> >>> have MSIs map into normal IRQ descriptors. At the moment, all
> >>> MSI users are based on IRQ numbers, but this has known scalability problems.
> >>
> >> Hmmm, I still use the IRQ number to map the
2014 Aug 01
2
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
On Wednesday 30 July 2014, Yijing Wang wrote:
> >>>
> >>> The other part I'm not completely sure about is how you want to
> >>> have MSIs map into normal IRQ descriptors. At the moment, all
> >>> MSI users are based on IRQ numbers, but this has known scalability problems.
> >>
> >> Hmmm, I still use the IRQ number to map the
2014 Aug 04
0
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
...uses one of them to process trivial network thins,
and others to transmit/receive data.
So, in this case, it seems to driver need to touch the IRQ numbers.
wr-linux:~ # cat /proc/interrupts
CPU0 CPU1 CPU2 .... CPU17 CPU18 CPU19 CPU20 CPU21 CPU22 CPU23
......
100: 0 0 0 0 0 0 0 0 0 0 IR-PCI-MSI-edge eth0
101: 2 0 0 0 0 0 302830488 0 0 0 IR-PCI-MSI...
2012 Nov 13
1
thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC
...pu2}
11 root 155 ki31 0K 384K RUN 9 18.4H 32.57% idle{idle: cpu9}
11 root 155 ki31 0K 384K RUN 5 18.4H 32.57% idle{idle: cpu5}
11 root 155 ki31 0K 384K RUN 0 18.4H 32.37% idle{idle: cpu0}
11 root 155 ki31 0K 384K CPU22 22 18.3H 32.37% idle{idle: cpu22}
11 root 155 ki31 0K 384K RUN 7 18.4H 32.28% idle{idle: cpu7}
11 root 155 ki31 0K 384K CPU14 14 18.3H 32.08% idle{idle: cpu14}
11 root 155 ki31 0K 384K RUN 6 18.4H 31.88% idle{idle: cpu6}
11 root...
2008 Aug 22
3
sun4v arch
I would also like to help as well.
As KMacy knows before i asked a lot of questions for T2 types of
servers but unfortunately i have no more access to those kind of
hardware as well.
I;m willing to participate if a team will be formated.
2012 Apr 17
10
kernel panic during zfs import [UPDATE]
Hello everybody,
just to let you know what happened in the meantime:
I was able to open a Service Request at Oracle.
The issue is a known bug (Bug 6742788 : assertion panic at: zfs:zap_deref_leaf)
The bug has bin fixed (according to Oracle support) since build 164, but there is no fix for Solaris 11 available so far (will be fixed in S11U7?).
There is a workaround available that works
2013 Mar 12
14
vpmu=1 and running 'perf top' within a PVHVM guest eventually hangs dom0 and hypervisor has stuck vCPUS. Romley-EP (model=45, stepping=2)
...U18 owner_map[b], no_cmci_map[14]
(XEN) CMCI: find owner on CPU19
(XEN) CMCI: CPU19 owner_map[0], no_cmci_map[14]
(XEN) CMCI: find owner on CPU20
(XEN) CMCI: CPU20 owner_map[b], no_cmci_map[14]
(XEN) CMCI: find owner on CPU21
(XEN) CMCI: CPU21 owner_map[0], no_cmci_map[14]
(XEN) CMCI: find owner on CPU22
(XEN) CMCI: CPU22 owner_map[b], no_cmci_map[14]
(XEN) CMCI: find owner on CPU23
(XEN) CMCI: CPU23 owner_map[0], no_cmci_map[14]
(XEN) CMCI: find owner on CPU24
(XEN) CMCI: CPU24 owner_map[b], no_cmci_map[14]
(XEN) CMCI: find owner on CPU25
(XEN) CMCI: CPU25 owner_map[0], no_cmci_map[14]
(XEN) CMCI:...
2010 Nov 16
0
Bug#603713: xen-hypervisor-4.0-amd64: amd64 Dom0-Kernel crashes in early boot-stage
...EN) microcode.c:73:d32767 microcode: CPU1 resumed
(XEN) microcode.c:73:d32767 microcode: CPU13 resumed
(XEN) microcode.c:73:d32767 microcode: CPU23 resumed
(XEN) microcode.c:73:d32767 microcode: CPU21 resumed
(XEN) microcode.c:73:d32767 microcode: CPU9 resumed
(XEN) microcode.c:73:d32767 microcode: CPU22 resumed
(XEN) microcode.c:73:d32767 microcode: CPU10 resumed
(XEN) microcode.c:73:d32767 microcode: CPU11 resumed
(XEN) microcode.c:73:d32767 microcode: CPU3 resumed
(XEN) microcode.c:73:d32767 microcode: CPU17 resumed
(XEN) microcode.c:73:d32767 microcode: CPU5 resumed
(XEN) microcode.c:73:d32767...
2011 Jul 07
6
Xen unstable on NetBSD
Hello,
I''m trying to compile Xen unstable on NetBSD, I''ve aplied the patches
from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/patches/?only_with_tag=MAIN
and copied the blk files from
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/sysutils/xentools41/files/?only_with_tag=MAIN
(I don''t know which of these patches have been applied to xen
unstable, so