similar to: trouble building 2.6.38: ''IRQF_FORCE_RESUME'' undeclared

This is a note to let you know that I''ve just added the patch titled genirq: Add IRQF_RESUME_EARLY and resume such IRQs earlier to the 3.1-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: genirq-add-irqf_resume_early-and-resume-such-irqs-earlier.patch and it can be found in the

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 lock_kicker_irq and its irq handler is invoked which reports bug and crashes

I''ve been looking into bug [1]#195 and I have a couple of questions on how timer interrupts and virqs are handled. Is it possible for dom0 linux to irq balance timer interrupts to different cpus? That is, if xen sends a VIRQ_TIMER to vcpu0, backed by cpu0, is it possible for that interrupt to be handled by vcpu1, backed by cpu1 ? After putting in some debug code in to timer_interrupt

Hello, kernels 2.6.35.5 and 2.6.32.22 xen domU panics at the very begining of the boot process. I have bisected it to a single commit, and the first bad commit is: [fb412a178502dc498430723b082a932f797e4763] xen: use percpu interrupts for IPIs and VIRQs kernel v2.6.35.5 with reverted this commit works for me. Here are the kernel configs I was using:

Hello, kernels 2.6.35.5 and 2.6.32.22 xen domU panics at the very begining of the boot process. I have bisected it to a single commit, and the first bad commit is: [fb412a178502dc498430723b082a932f797e4763] xen: use percpu interrupts for IPIs and VIRQs kernel v2.6.35.5 with reverted this commit works for me. Here are the kernel configs I was using:

Keir, this change looks a little odd to me - the code as it was before already set the timeout to jiffies + 1 as the lowest possible value. So I don''t understand how you could have observed any spinning over more than really short periods of time (where you happen to just see jiffies increment while setting the timeout). I''d therefore appreciate any insight to the background of

I tried for a couple of times to add an information that might help you with regard to Bug #603713 by sending mailto "603713 at bugs.debian.org" But it never appeared there - so I try to let you know how to work around that bug this way. If you decide not to take this mail into account I won't bother you any more Regards Andreas -----Urspr?ngliche Nachricht----- Von: Balg, Andreas

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-rc7 + your patches + the last batch of pv_ops patches I posted. This patch generally restricts itself to Xen-specific parts of the tree, though it does make a few small changes elsewhere. These patches include: - some helper routines for allocating address space and walking pagetables - Xen

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-rc7 + your patches + the last batch of pv_ops patches I posted. This patch generally restricts itself to Xen-specific parts of the tree, though it does make a few small changes elsewhere. These patches include: - some helper routines for allocating address space and walking pagetables - Xen

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-git13 + patches-2.6.21-git7-070507-1.tar.gz (I think "unwinder" is the only patch which doesn't apply to git13, and the sched-clock patches are the only ones which this series actually needs). Changes since the last posting: - More netfront review and cleanup - Added ability to

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-git13 + patches-2.6.21-git7-070507-1.tar.gz (I think "unwinder" is the only patch which doesn't apply to git13, and the sched-clock patches are the only ones which this series actually needs). Changes since the last posting: - More netfront review and cleanup - Added ability to

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-git13 + patches-2.6.21-git7-070507-1.tar.gz (I think "unwinder" is the only patch which doesn't apply to git13, and the sched-clock patches are the only ones which this series actually needs). Changes since the last posting: - More netfront review and cleanup - Added ability to

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-git3 + ff patches-2.6.21-git3-070501-1.tar.gz. Changes since the last posting: - reviews of xenbus (me), netfront (hch, rusty, herbert xu) and blockfront (hch), with most comments addressed. Netfront review revealed a couple of real bugs, and the code for all three is looking cleaner

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21-git3 + ff patches-2.6.21-git3-070501-1.tar.gz. Changes since the last posting: - reviews of xenbus (me), netfront (hch, rusty, herbert xu) and blockfront (hch), with most comments addressed. Netfront review revealed a couple of real bugs, and the code for all three is looking cleaner

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21 + 2.6.21-070428-1 + the patches I've posted over the last couple of days. Changes since the last posting: - update per review comments - comment each file - comment barrier use - use common cpu sibling setup - fixed a few minor bugs, specifically a traceirq mismatch warning - some

Hi Andi, This series of patches implements the Xen paravirt-ops interface. It applies to 2.6.21 + 2.6.21-070428-1 + the patches I've posted over the last couple of days. Changes since the last posting: - update per review comments - comment each file - comment barrier use - use common cpu sibling setup - fixed a few minor bugs, specifically a traceirq mismatch warning - some

Unlike x86 and apparently ia64, PowerPC delivers timer interrupts as a different exception than device interrupts. For PowerPC Xen, we emulate this exception rather than delivering timer events as virtual IRQs. This patch introduces no functional changes for x86 and ia64, but is a required change for xen/arch/ppc. Compile-tested on x86-32. Please apply. Signed-off-by: Hollis Blanchard

Hi all, I need a periodic timer running at ideally at 125 microseconds and at least 500 microseconds. I''ve just found the VCPUOP_set_periodic_timer, however there is a comment saying "periods less than one millisecond may not be supported". I will be running on an x64 machine. Is this supported? If not, is there any alternate means of generating a fast interrupt? Regards.

Need help about this error, one per each TK variable in wineinstall which causes aborting compilation. Thank you.

# HG changeset patch # User dme@aw # Date 1234261891 0 # Node ID 1efbb12b68601ff4ed928fbb2b27123643136747 # Parent 72cac93428513c23f3a433d2a16dab010881bb07 PCIQuirk`__devIsUnconstrained refers to an undeclared variable if /etc/xen/xend-pci-permissive.sxp doesn''t exist. Signed-off-by: David Edmondson <dme@sun.com> diff -r 72cac9342851 -r 1efbb12b6860