search for: irqs

...ages: 129947 [ 0.000000] Kernel command line: root=UUID=e4354c74-bdb0-4e78-8c26-7964a61e08bd ro console=ttyS0,115200 [ 0.000000] Enabling fast FPU save and restore... done. [ 0.000000] Enabling unmasked SIMD FPU exception support... done. [ 0.000000] Initializing CPU#0 [ 0.000000] NR_IRQS:512 [ 0.000000] xen_set_ioapic_routing: irq 0 gsi 0 vector 240 ioapic 0 pin 0 triggering 0 polarity 0 [ 0.000000] xen_set_ioapic_routing: irq 1 gsi 1 vector 32 ioapic 0 pin 1 triggering 0 polarity 0 [ 0.000000] xen_set_ioapic_routing: irq 3 gsi 3 vector 40 ioapic 0 pin 3 triggering 0 polar...

...there is no ixgbe message in dmesg. I can list irq from dmesg (with NIC detected) and dmesg.old (NIS is not tedected) grep irq dmesg [??? 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [??? 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [??? 0.000000] NR_IRQS:327936 nr_irqs:1024 0 [??? 0.531915] pcieport 0000:00:01.0: irq 120 for MSI/MSI-X [??? 0.532038] pcieport 0000:00:1b.0: irq 121 for MSI/MSI-X [??? 0.532309] pcieport 0000:00:1c.5: irq 122 for MSI/MSI-X [??? 0.532534] pcieport 0000:00:1d.0: irq 123 for MSI/MSI-X [??? 0.604204] 00:05: ttyS0 at I/O 0x...

The main change from the patches I sent out earlier this week is support for guests that use the PIC. A callback for PIC irq ack handling is also introduced. Currently, there's no mechanism to register/unregister callers to the irq ack callbacks, but they can be added when there's more than one user for the functionality. Please review.

The main change from the patches I sent out earlier this week is support for guests that use the PIC. A callback for PIC irq ack handling is also introduced. Currently, there's no mechanism to register/unregister callers to the irq ack callbacks, but they can be added when there's more than one user for the functionality. Please review.

...g. > > I can list irq from dmesg (with NIC detected) and dmesg.old (NIS is not > tedected) > grep irq dmesg > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) > [ 0.000000] NR_IRQS:327936 nr_irqs:1024 0 > [ 0.531915] pcieport 0000:00:01.0: irq 120 for MSI/MSI-X > [ 0.532038] pcieport 0000:00:1b.0: irq 121 for MSI/MSI-X > [ 0.532309] pcieport 0000:00:1c.5: irq 122 for MSI/MSI-X > [ 0.532534] pcieport 0000:00:1d.0: irq 123 for MSI/MSI-X > [ 0.60420...

Hello, I had noticed strange crackling sound on my phone calls going through my zaptel device (TDM400P), so i decided to check on possible timer issue, and found lots of issues on forums concerning the sensibility of zaptel with IRQs, and tried about everything: moving PCI slots, noapic and acpi=off boot options, play with different kernel options: iosched/preemption/timer/..., play with BIOS PCI options, change priorities, PCI latencies, IRQ balance, smp_afinity, ................ but impossible to come up with anything cor...

I setup a CentOS 6 server to use with KVM/QEMU, and I am getting the following error a good bit, granted it doesn't seem to be causing any trouble. I figured I would post and see if anyone has any ideas on the issue, or if I can just dismiss it. If I look at my logging/dmesg, I see: do_IRQ: 19.217 No irq handler for vector (irq -1) do_IRQ: 3.178 No irq handler for vector (irq -1) do_IRQ:

...ive_setup_ioapic_entry(int, struct > IO_APIC_route_entry *, > struct io_apic_irq_attr *); > extern void eoi_ioapic_irq(unsigned int irq, struct irq_cfg *cfg); > > -extern void native_compose_msi_msg(struct pci_dev *pdev, > +extern void native_compose_msi_msg(struct msi_irqs *msi, > unsigned int irq, unsigned int dest, > struct msi_msg *msg, u8 hpet_id); > extern void native_eoi_ioapic_pin(int apic, int pin, int vector); > diff --git a/arch/x86/include/asm/irq_remapping.h > b/arch/x86/include/asm/irq_remapping.h > index b7747c4..a1000...

...ive_setup_ioapic_entry(int, struct > IO_APIC_route_entry *, > struct io_apic_irq_attr *); > extern void eoi_ioapic_irq(unsigned int irq, struct irq_cfg *cfg); > > -extern void native_compose_msi_msg(struct pci_dev *pdev, > +extern void native_compose_msi_msg(struct msi_irqs *msi, > unsigned int irq, unsigned int dest, > struct msi_msg *msg, u8 hpet_id); > extern void native_eoi_ioapic_pin(int apic, int pin, int vector); > diff --git a/arch/x86/include/asm/irq_remapping.h > b/arch/x86/include/asm/irq_remapping.h > index b7747c4..a1000...

...ent virtio-mmio only support single irq, >> so some advanced features such as vhost-net with irqfd >> are not supported. And the net performance is not >> the best without vhost-net and irqfd supporting. >> >> This patch support virtio-mmio to request multiple >> irqs like virtio-pci. With this patch and qemu assigning >> multiple irqs for virtio-mmio device, it's ok to use >> vhost-net with irqfd on arm/arm64. >> >> As arm doesn't support msi-x now, we use GSI for >> multiple irq. In this patch we use "vm_try_to_find_v...

...ent virtio-mmio only support single irq, >> so some advanced features such as vhost-net with irqfd >> are not supported. And the net performance is not >> the best without vhost-net and irqfd supporting. >> >> This patch support virtio-mmio to request multiple >> irqs like virtio-pci. With this patch and qemu assigning >> multiple irqs for virtio-mmio device, it's ok to use >> vhost-net with irqfd on arm/arm64. >> >> As arm doesn't support msi-x now, we use GSI for >> multiple irq. In this patch we use "vm_try_to_find_v...

...58,7 +158,7 @@ extern int native_setup_ioapic_entry(int, struct IO_APIC_route_entry *, struct io_apic_irq_attr *); extern void eoi_ioapic_irq(unsigned int irq, struct irq_cfg *cfg); -extern void native_compose_msi_msg(struct pci_dev *pdev, +extern void native_compose_msi_msg(struct msi_irqs *msi, unsigned int irq, unsigned int dest, struct msi_msg *msg, u8 hpet_id); extern void native_eoi_ioapic_pin(int apic, int pin, int vector); diff --git a/arch/x86/include/asm/irq_remapping.h b/arch/x86/include/asm/irq_remapping.h index b7747c4..a10003d 100644 --- a/arch/x86/inclu...

irq: Exclude percpu IRQs from being fixed up Xen spin unlock uses spurious ipi "lock_kicker_irq" to wake up blocked vCPUs waiting on that lock. This irq should always be disabled. However, when Dom0 is shuting down, function fixup_irqs is called which unmasks all irqs. Function unmask_irq effectively re-enables...

We (Michael Fetterman, George Dunlap and I) have been working over the last while on a full replacement for Xen''s shadow pagetable support. This mail contains some design notes, below; a patch against xen-unstable, giving a snapshot of the current state of the new shadow code, is at http://www.cl.cam.ac.uk/~tjd21/shadow2.patch Comments on both are welcome, although the code is not

I have brand new PC with this components: CPU Intel? Pentium G5400, LGA1151 motherboard ASUS PRIME B360M-C 16 GB RAM HDD 2x ADATA SSD 256GB XPG GAMMIX S11, PCIe Gen3x4 M.2 2280 (RAID1) NIC Intel X550-T1 Ethernet Converged Network Adapter I installed CentOS 7 and two NICs were detected: eno1 (on motherboard) enp1s0 (Intel X550-T1) When I restart the machine sometimes enp1s0 is missing. It is not

Recently our automated testing system has caught a curious assertion while testing Xen 4.1.5 on a HaswellDT system. (XEN) Assertion ''(sp == 0) || (peoi[sp-1].vector < vector)'' failed at irq.c:1030 (XEN) ----[ Xen-4.1.5 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff82c48016b2b4>] do_IRQ+0x514/0x750 (XEN) RFLAGS: 0000000000010093 CONTEXT:

Hello I just installed a TE110P in a Dell Poweredge 750 (rackmount), which is connected via crossover T1 cable to a adit 600. Anyway, I've encountered an array of errors, which I believe I have narrowed down to the 22 IRQ misses I encounter on zttool. I've noticed that the te110p and the usb device share an IRQ. Could that be the source of my woes? Would disabling the usb device in the

Hello, when I try to start xend I receive this error: root@xenized:~# xend start ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 36, in <module> from xen.xend.server import SrvDaemon File

...ingle irq, > >> so some advanced features such as vhost-net with irqfd > >> are not supported. And the net performance is not > >> the best without vhost-net and irqfd supporting. > >> > >> This patch support virtio-mmio to request multiple > >> irqs like virtio-pci. With this patch and qemu assigning > >> multiple irqs for virtio-mmio device, it's ok to use > >> vhost-net with irqfd on arm/arm64. > >> > >> As arm doesn't support msi-x now, we use GSI for > >> multiple irq. In this patch we u...

c/s 25336:edd7c7ad1ad2 introduced the concept of a bogus vector, for in irqs delivered through the i8259 PIC after IO-APICs had been set up. However, if supurious PIC vectors are received, many "No irq handler for vector" log messages can be seen on the console. This patch adds to the bogus vector logic to detect spurious PIC vectors and simply ignore them. _ma...