similar to: [040/111] xen: Do not suspend IPI IRQs.

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

Hi list(...), I've narrowed down a weird bug. It's like a ghost in the machine, in that functions seem to remember things that they should not be able to. In the example below, the result of the second (and subseqent) calls depend on what was given in the first call. foo <- function(given = NULL) { callObj <- quote(callFunc()) if (!is.null(given)) callObj$given

Use PM_FREEZE, PM_THAW and PM_RESTORE power events for suspend/resume/checkpoint functionality, instead of PM_SUSPEND and PM_RESUME. Use of these pm events fixes the Xen Guest hangup when taking checkpoints. When a suspend event is cancelled (while taking checkpoints once/continuously), we use PM_THAW instead of PM_RESUME. PM_RESTORE is used when suspend is not cancelled. See

Package: xen Version: 4.3.0-3+b1 When trying to migrate from a 4.3 host to a 4.1 host (which should fail of course, but gracefully), the PV guest on the sending host crashes. To be honest, I have no idea which component to file this bug against. The sending host has been upgraded to jessie. Here're the relevant package versions: ii libxen-4.3 4.3.0-3+b1

Thank you for useful feedbacks! Here is the updated version. Could you put this on top of your patches, Rusty? Thanks, H.Seto If stop_machine() invoked while one of onlined cpu is locked up by some reason, stop_machine cannot finish its work because the locked cpu cannot stop. This means all other healthy cpus will be blocked infinitely by one dead cpu. This patch allows stop_machine to

Thank you for useful feedbacks! Here is the updated version. Could you put this on top of your patches, Rusty? Thanks, H.Seto If stop_machine() invoked while one of onlined cpu is locked up by some reason, stop_machine cannot finish its work because the locked cpu cannot stop. This means all other healthy cpus will be blocked infinitely by one dead cpu. This patch allows stop_machine to

If stop_machine() invoked while one of onlined cpu is locked up by some reason, stop_machine cannot finish its work because the locked cpu cannot stop. This means all other healthy cpus will be blocked infinitely by one dead cpu. This patch allows stop_machine to return -EBUSY with some printk messages if any of stop_machine's threads cannot start running on its target cpu in time. You can

If stop_machine() invoked while one of onlined cpu is locked up by some reason, stop_machine cannot finish its work because the locked cpu cannot stop. This means all other healthy cpus will be blocked infinitely by one dead cpu. This patch allows stop_machine to return -EBUSY with some printk messages if any of stop_machine's threads cannot start running on its target cpu in time. You can

Iirc I derived this from a prior commit from either Ian or Jeremy. Didn''t really check it out, so there''s very likely a more correct fix than what''s attached here. /local/exp/dns/scratch/xenbits/xen-unstable.hg/linux-2.6-pvops.git/arch/x86/xen/time.c: In function ''xen_setup_timer'':

What is the point of specifying "current" as the address to monitor? The memory location of interest really is irq_stat[cpu].__softirq_pending, and if that was used it would then also be possible to actually avoid sending IPIs when monitor/mwait are in use, as is being done on Linux. Jan _______________________________________________ Xen-devel mailing list

Hi, The following patch series fixes hangup after creating checkpoint on Xen. The Linux Xen guest can be saved the state to restore later, and also created snapshot like checkpoint via the hypervisor. But, when the snapshot is created for the PV guest, it will hangup. We added ''PMSG_CANCEL'' message and ''cancel'' handler in dev_pm_ops struct in the pm-linux

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

This patch series implements SMP boot for arch/arm, as far as getting all CPUs up and running the idle loop. Changes from v1: - moved barriers out of loop in udelay() - dropped broken GIC change in favour of explanatory comment - made the increment of ready_cpus atomic (I couldn''t move the increment to before signalling the next CPU because the PT switch has to happen between

Hi all, I have dom0 and a guest on the same cpu: cpu0. However, when I look at interrupts and ipis (with Xenperf) I get the following. There is nothing going on Cpu3 so why the high number of IPIs? I have done a reset of the counters, but after I run my workload on the guest cpu3 IPIS go from 0 to 210276 (Dom- has only 1 cpu and xm vcpu-list shows the other 3 cpus in blocked state. The

-----BEGIN PGP SIGNED MESSAGE----- - --------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: New PAM packages available Advisory ID: RHSA-1999:040 Issue date: 10/13/1999 Updated on: 10/13/1999 Keywords: pam security login NIS server Cross references: N/A -

Hi, I have some problem with computer browser and Net Logon. I suspect the MS-patches named MS06-40 (921883). http://www.microsoft.com/technet/security/Bulletin/MS06-040.mspx Could anyone confim if this patches couse problem or not. Actually I use samba 3.0.21c and I would like to know if samba 3.0.23c could resolve problem. thanks St?phane Purnelle

Wondering if the fix for this has been found? I'm having the same thing with Solaris 10. tim

Dear List, I'm trying to compile tftp-hpa-040 under Solris 8: Step 1: "configre" works fine: root at isu001[/usr/src/tftp-hpa-0.40] > ./configure checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for

Hi, Just recently the logs of a production Samba server are being populated by the following message: "smbd/session.c:111(session_claim) Re-using invalid record" Does anyone have any tips for fixing this "invalid record"? (I believe it is related to the utmp = yes option which is set in /etc/samba/smb.conf). I do not believe this log message is serious, but we are

ive been trying to dig through this problem for awhile now but cant seem to view my rails app from outside the LAN. my nginx file prints this.. 2008/03/14 17:33:01 [error] 12090#0: *254 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: my-desktop, URL: "/", upstream: "http://127.0.0.1:8003/", host: "localhost:3050"