search for: interruptibility

Greetings everyone. I am experiencing the kworker issue where a kworker is using 100% of a given core. This behavior was only observed after having installed a new water cooler, to replace a cooler that had died. (Sealed closed loop device from Corsair) The processor is staying around 40 degrees celsius as reported by the MB UEFI interface. (ksysguard shows between 29 degrees and 30 degrees,

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

Greetings again everyone. Can someone please respond to this? I am not sure what is causing this issue, however, others seem to have experienced it in the past. Could this be caused by the processor being damaged? Nothing has changed on the system, except for the heat warning shutoff when the water cooler died, and the system was not restarted until the new one was installed. Any input

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. Here is one idea similar to virtualized PMU: It first registers a special

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

> 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 thread on yahoo''s solarisx86

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?

On 2014/11/11 23:11, Pawel Moll wrote: > On Tue, 2014-11-04 at 09:35 +0000, Shannon Zhao wrote: >> As the current 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. > > Could you, please, help understanding me where

On 2014/11/11 23:11, Pawel Moll wrote: > On Tue, 2014-11-04 at 09:35 +0000, Shannon Zhao wrote: >> As the current 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. > > Could you, please, help understanding me where

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) -

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

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

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...\n"); Sys.sleep(5); }, interrupt =

On 2014/11/13 2:33, Pawel Moll wrote: > On Wed, 2014-11-12 at 08:32 +0000, Shannon Zhao wrote: >> On 2014/11/11 23:11, Pawel Moll wrote: >>> On Tue, 2014-11-04 at 09:35 +0000, Shannon Zhao wrote: >>>> As the current virtio-mmio only support single irq, >>>> so some advanced features such as vhost-net with irqfd >>>> are not supported. And the

On 2014/11/13 2:33, Pawel Moll wrote: > On Wed, 2014-11-12 at 08:32 +0000, Shannon Zhao wrote: >> On 2014/11/11 23:11, Pawel Moll wrote: >>> On Tue, 2014-11-04 at 09:35 +0000, Shannon Zhao wrote: >>>> As the current virtio-mmio only support single irq, >>>> so some advanced features such as vhost-net with irqfd >>>> are not supported. And the