search for: interrupts

...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/ /sys...

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:

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:

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 triggered the interrupt, the IRQ is

...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/ /sys...

...CFG) into guest VM via virtual local APIC. This worked from my test. But adding a interrupt handler seems to be an overkill. Is there any better way to create a dummy interrupt receiver on be-behalf of guest VMs? I also looked into IRQ and MSI solutions inside Xen. But most of them assume that interrupts are from physical device (but not in this LWP case, where interrupt is initiated from CPU itself); so they don''t fit very well. Thanks, -Wei

Hi, Keir, These patches are rebased version of Yunhong''s original patches, which were sent out before XEN 3.2 was released. These patches enable MSI support and limited MSI-X support in XEN. Here is the original description of the patches from Yunhong''s mail. The basic idea including: 1) Keep vector global resource owned by xen, while split pirq into per-domain

...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 thread on yahoo''s solarisx86 mailing list, with an snv_20 user complaining about high interrupt rates (> 32000 interrupts/sec) on a w2100z: http://groups.yahoo.com/group/solarisx86/message/29841 The interrupts are most likely acpi interrupts, but "intrstat" does not report any acpi interrupt activity. This is because arg0 == NULL for acpi interrupts in the interrupt-start action inside intrstat, so that...

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 happens. tryCatch(Sys.sleep(100), interrupt =

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 gets...

...ing 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. Therefore the virtio-mmio driver should read the "VIRTIO_MMIO_IN...

...ing 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. Therefore the virtio-mmio driver should read the "VIRTIO_MMIO_IN...

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 delaying used to wait for the physical interrupt deassertion.

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

The following 5 patches are re-submissions of the vt-d patch. This set of patches has been tested against cs# 15080 and is now much more mature 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) -

...NAK indicate no interrupt pending(i.e. no data needs to be transferred). Current HID always returns a data package, notifying UHC the device have data to transfer and a interrupt on complete will generate at the end of the frame in which this interrupt transfer is completed. In fact, most of these interrupts are useless and time-consuming. UHC should let a TD active if receiving an NAK (in non-setup transaction) and will not generate an interrtupt on complete for this TD. But current UHC emulator in qemu-dm behaves like this: 1)update int_mask when a TD is fetched 2)check int_mask to decide to gener...

...der 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 by the corresponding handler in dom0/(hypervisor?) which decides whether to neglect that interrupt or inject back into the guest to be handled by the corresponding vcpu. Thus, every time an interrupt is generated i...

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+C...

...t;> >>> 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. > > Yes. > > Additiona...

...t;> >>> 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. > > Yes. > > Additiona...