search for: cpu17

Displaying 10 results from an estimated 10 matches for "cpu17".

Did you mean: cpu1
2014 Aug 04
1
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
...network driver generally 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...
2014 Aug 04
1
[RFC PATCH 00/11] Refactor MSI to support Non-PCI device
...network driver generally 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...
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
...process different things. Eg. network driver generally 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...
2012 Nov 13
1
thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC
...31 0K 384K RUN 15 18.3H 29.59% idle{idle: cpu15} 11 root 155 ki31 0K 384K RUN 16 18.3H 29.59% idle{idle: cpu16} 2968 dovenull 52 0 38568K 12240K pipewr 4 5:24 29.39% pop3-login 11 root 155 ki31 0K 384K RUN 17 18.3H 29.30% idle{idle: cpu17} 2970 dovenull 52 0 42664K 15968K pipewr 10 7:18 28.66% pop3-login 2983 dovenull 52 0 38568K 11984K pipewr 5 5:03 28.66% pop3-login 2976 dovenull 52 0 42664K 17896K pipewr 23 7:46 28.56% pop3-login 2974 dovenull 52 0 46760K 19156K pipewr 16 7:40 28.4...
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.
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)
...n CPU10 (XEN) no_cmci_map[14] (XEN) CMCI: find owner on CPU14 (XEN) CMCI: CPU14 owner_map[b], no_cmci_map[14] (XEN) CMCI: find owner on CPU15 (XEN) CMCI: CPU15 owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU16 (XEN) CMCI: CPU16 owner_map[fffeb], no_cmci_map[14] (XEN) CMCI: find owner on CPU17 (XEN) CMCI: CPU17 owner_map[0], no_cmci_map[14] (XEN) CMCI: find owner on CPU18 (XEN) CMCI: CPU18 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:...
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: 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 microcode: CPU6 resumed (XEN) microcode.c:73:d32767 microcode: CPU18 resumed (XEN) microcode.c:73:d32767 microcode: CPU19 resumed (XEN) microcode.c:73:d32767 microcode: CPU15 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