search for: interrupt

...hen running KDE 4) I am unable to isolate a cause, or resolution for getting the kworker usage back to normal. Very basic description of specs are as follows: AMD FX-8350 (not overclocked) 32GB Corsair memory (1866Mhz non-overclocked) Sabortooth 990FX MB I have checked the locations for interrupts which has been indicated online, however, I do not have any specific interrupts that are showing as even having a high integer value to unset. Here is the result of running the referenced command to view interrupts. [sysadmin at imaginationland ~]$ grep . -r /sys/firmware/acpi/interrupts/ /sy...

Hi, During the compilatin of xen i have the following error message: i8259.c:66:9: error: initialization from incompatible pointer type [-Werror] i8259.c:66:9: error: (near initialization for ‘interrupt[6]’) [-Werror] i8259.c:66:9: error: initialization from incompatible pointer type [-Werror] i8259.c:66:9: error: (near initialization for ‘interrupt[7]’) [-Werror] i8259.c:66:9: error: initialization from incompatible pointer type [-Werror] i8259.c:66:9: error: (near initialization for ‘interrupt[8...

Hi, During the compilatin of xen i have the following error message: i8259.c:66:9: error: initialization from incompatible pointer type [-Werror] i8259.c:66:9: error: (near initialization for ‘interrupt[6]’) [-Werror] i8259.c:66:9: error: initialization from incompatible pointer type [-Werror] i8259.c:66:9: error: (near initialization for ‘interrupt[7]’) [-Werror] i8259.c:66:9: error: initialization from incompatible pointer type [-Werror] i8259.c:66:9: error: (near initialization for ‘interrupt[8...

I have an on-going problem with DigiBoard Xem boards causing interrupt storms (since 4.x days). The FreeBSD driver polls the board and doesn't have a functional interrupt handler (and Linux behaves in the same way). It seems that under some conditions, the board will assert its interrupt line and, since there's no interrupt handler to clear whatever triggere...

...hen running KDE 4) I am unable to isolate a cause, or resolution for getting the kworker usage back to normal. Very basic description of specs are as follows: AMD FX-8350 (not overclocked) 32GB Corsair memory (1866Mhz non-overclocked) Sabortooth 990FX MB I have checked the locations for interrupts which has been indicated online, however, I do not have any specific interrupts that are showing as even having a high integer value to unset. Here is the result of running the referenced command to view interrupts. [sysadmin at imaginationland ~]$ grep . -r /sys/firmware/acpi/interrupts/ /sy...

I am adding interrupt support for LWP, whose spec is available at http://support.amd.com/us/Processor_TechDocs/43724.pdf. Basically OS can specify an interrupt vector in LWP_CFG MSR; the interrupt will be triggered when event buffer overflows. For HVM guests, I want to re-inject this interrupt back into the guest VM...

...patches from Yunhong''s mail. The basic idea including: 1) Keep vector global resource owned by xen, while split pirq into per-domain information. 2) Domain0 kernel will operate msi resource for domain0/domU, while QEMU will operate MSI resource for HVM domain. 3) Xen will do EOI for MSI interrupt. Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com <mailto:yunhong.jiang@intel.com> > There are no much changes made compared with the original patches. But there do have some issues that we need your kind comments. 1> ACK-NEW method is necessary to avoid IRQ storm. Bu...

> There are times when arg0 can be NULL [for the interrupt-start or > interrupt-complete probe] if there''s no associated device. > There''s already a bug open to address the error in the documentation. > 6284911 args to interrupt-start and interrupt-complete need more info Hmm, I noticed that, too. There''s currently a...

Anyone knows a way to re-throw a caught interrupt condition, so that it behaves just like the original one? I.e. no error message is printed, but the execution is stopped of course. With just calling stop in the error handler, it prints the error message, or, if there is no error message (like in the original interrupt condition), another error ha...

Good morning, I am new to Xen, and trying to understand how Xen works. I have some questions about virtualization of interrupts on Xen. Thanks in advance for all helps. 1) From papers about Xen architecture found at Xen homepage, Xen seemingly intercepts interrupts of Dom1 (paravirtualization). So interrupts occur in Dom1''s context are sent to Xen, and Xen handles them. Is that correct? But then how can Dom1 get...

...nd irqfd supporting. > > Could you, please, help understanding me where does the main issue is? > Is it about: > > 1. The fact that the existing implementation blindly kicks all queues, > instead only of the updated ones? > > or: > > 2. Literally having a dedicated interrupt line (remember, we're talking > "real" interrupts here, not message signalled ones) per queue, so they > can be handled by different processors at the same time? > The main issue is that current virtio-mmio only support one interrupt which is shared by config and queues. Th...

...nd irqfd supporting. > > Could you, please, help understanding me where does the main issue is? > Is it about: > > 1. The fact that the existing implementation blindly kicks all queues, > instead only of the updated ones? > > or: > > 2. Literally having a dedicated interrupt line (remember, we're talking > "real" interrupts here, not message signalled ones) per queue, so they > can be handled by different processors at the same time? > The main issue is that current virtio-mmio only support one interrupt which is shared by config and queues. Th...

Attached is a patch for shared interrupt between dom0 and HVM domain for vtd. Most of problem is caused by that we should inject interrupt to both domains and the physical interrupt deassertion then may be delayed by the device assigned to the HVM. The patch adds a timer, and the time out value is sufficient large to tolerant the d...

Today I updated several servers running CentOS 4.3, and got the new 2.6.9-42 kernel. One of the machines serves as our firewall. After rebooting I lost all forwarding thru the machine. I reverted back to the 2.6.9-34 kernel and connectivity returned. During the few minutes that the new kernel was running I checked that the routing table looked OK, and with tcpdump I saw that indeed no traffic

...ture and tested against more environments than the original patch. Specifically, we have successfully tested the patch with following environements: - 32/64-bit Linux HVM guest - 32-bit Windows XP/Vista (64-bit should work but did not test) - 32PAE/64-bit hypervisor - APIC and PIC interrupt mechanisms - PCIe E1000 and PCI E100 NICs Allen ---------------------- 1) patch description: vtd1.patch: - vt-d specific code - low risk changes in common code vtd2.patch: - io port handling vtd3.patch: - interrupt handling vtd4.patch: - mmio handling vtd5.patch: -...

Hi all, Is there any comment on this patch? Current HID(mouse/tablet) emulator in qemu-dm persistently returns a data in an INTERRUPT transfer, even if the device (mouse/tablet) keeps the same status as the last interrupt transfer. This behavior does not reflect the HID/USB/UHCI spec. According to HID spec, USB HID device (using interrupt pipe) will return an NAK indicate no interrupt pending(i.e. no data needs to be transferred)...

I have an Intel e1000e NIC which I put into passthrough for an HVM domain under Xen 4.2. All the corresponding hardware protections are enabled on my system (DMA + Interrupt remapping), however, once in a while I get a SERR NMI in dom0 (NMI - PCI sys error (SERR) in xl dmesg). I am wondering about its exact reason. I am thinking in the following way: [+] Under Intel VT-x, interrupts are virtualized, thus all the interrupts coming from my HVM domain should be handled b...

With tryCatch() it is possible to catch interrupts with tryCatch(). Then you can use a 'finally' statement to clean up, release resources etc. However, how can I "protect" against additional interrupts? This is a concern when the hold down Ctrl+C and generates a sequence of interrupts. Example: tryCatch({ cat("Press Ctrl+...

...standing me where does the main issue is? >>> Is it about: >>> >>> 1. The fact that the existing implementation blindly kicks all queues, >>> instead only of the updated ones? >>> >>> or: >>> >>> 2. Literally having a dedicated interrupt line (remember, we're talking >>> "real" interrupts here, not message signalled ones) per queue, so they >>> can be handled by different processors at the same time? >>> >> The main issue is that current virtio-mmio only support one interrupt which is...

...standing me where does the main issue is? >>> Is it about: >>> >>> 1. The fact that the existing implementation blindly kicks all queues, >>> instead only of the updated ones? >>> >>> or: >>> >>> 2. Literally having a dedicated interrupt line (remember, we're talking >>> "real" interrupts here, not message signalled ones) per queue, so they >>> can be handled by different processors at the same time? >>> >> The main issue is that current virtio-mmio only support one interrupt which is...