similar to: softirq bound to vcpus

This patch implements cpu offline feature. Best Regards Haitao Shan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

The self_nmi() code cause''s an NMI to be triggered by sending an APIC message to the local processor. However, NMIs are blocked by the VMEXIT, until the next iret or VMENTER. Volume 3 Chapter 27 Section 1 of the Intel SDM states: An NMI causes subsequent NMIs to be blocked, but only after the VM exit completes. As a result, as soon as the VMENTER happens, an immediate VMEXIT happens

Doing some janitorial (you cleaning the flooded toilets and such) work today. I have come across this line of code that really I''m not sure what the intent was..in xen/include/sched.h #define hypercall_preempt_check() (unlikely( \ softirq_pending(smp_processor_id()) | \ (!!current->vcpu_info->evtchn_upcall_pending & \

If the vgic needs to inject a virtual irq into the guest, but no free LR registers are available, add the irq to a list and return. Whenever an LR register becomes available we add the queued irq to it and remove it from the list. We use the gic lock to protect the list and the bitmask. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> --- xen/arch/arm/gic.c |

I''m getting subj trying to run linux-iscsi-4.0.2 on domain0. I tried xen-2.0.6, xen-2-test and xen-3-devel. The same results. I found similar complaints regarding this problem like below: http://www.ussg.iu.edu/hypermail/linux/kernel/0503.1/1622.html http://www.ussg.iu.edu/hypermail/linux/kernel/0503.1/1621.html Not sure if it is xen or linux-iscsi related bug. Any ideas how to cure it

When I call EM::stop from within a Deferrable callback, I''m getting the following: terminate called after throwing an instance of ''std::runtime_error'' what(): already initialized Abort trap Is there any way to trace this a little further? -- Duane Johnson

I have small xen VM running centos4 which acts as a router/firewall, and has been working fine for over 1.5 years with 32MB of RAM and a kernel I either got from xensource.org or built myself from their sources. (centos 4 didn't have a xen kernel back then) I lost the kernel to a corrupted disk and decided to use the centos provided xen kernel. All these months 32MB + 64MB Swap was more than

I was trying to deal with foreign key issues related to order of fixture loading when I came across this: http://techpolesen.blogspot.com/2007/04/rails-fixture-tips.html This got me looking deeper into rails and I noticed that db:fixtures:load calls Fixtures.create_fixtures once for each fixture file. However, Fixtures.create_fixtures is capable of taking multiple files and also handle the

Hi All, If I turn off irqbalance xen/arch/x86/irq.c, does that actually stop XEN from balancing irqs across different physical cpus, or will that override the setting if there are too many interrupts and one of the cpus is overloaded. Example: i have 4 cpus and i have configured irqbalance= off, so there is no irqbalancing done by xen. Now if i have affintized all my physical interrutps to one

Hi, I''m seeing this in the current linux-next tree: ------------[ cut here ]------------ WARNING: at kernel/softirq.c:143 local_bh_enable+0x40/0x87() Modules linked in: xt_state dm_mirror dm_region_hash dm_log microcode [last unloaded: scsi_wait_scan] Pid: 0, comm: swapper Not tainted 2.6.35-rc6-next-20100729+ #29 Call Trace: <IRQ> [<ffffffff81030de3>]

Hello everyone, Reposting with after having applied the (minor) fixes suggested by Wei and Jan. Allen, if you can tell us what you think about this, or suggest someone else to ask some feedback to, if you''re no longer involved with VT-d, that would be great! :-) -- As already discussed here [1], dealing with IOMMU faults in interrupt context may cause nasty things to happen, up to

__napi_schedule might raise softirq but nothing causes do_softirq to trigger, so it does not in fact run. As a result, the error message "NOHZ: local_softirq_pending 08" sometimes occurs during boot of a KVM guest when the network service is started and we are oom: ... Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for

__napi_schedule might raise softirq but nothing causes do_softirq to trigger, so it does not in fact run. As a result, the error message "NOHZ: local_softirq_pending 08" sometimes occurs during boot of a KVM guest when the network service is started and we are oom: ... Bringing up loopback interface: [ OK ] Bringing up interface eth0: Determining IP information for

I recently submitted a pull-request (https://github.com/rails/rails/pull/10939) to address a bug in PostgreSQLAdapter#disable_referential_integrity related to how the existing code behaves in a transaction when the PostgreSQL user account lacks superuser privileges on the PostgreSQL instance. While this permits the code to function without crashing, it doesn''t actually make

Hi, I have a machine under heavy network traffic. Kernel is Centos kernel 2.6.18 SMP 32 bit. Ethernets are 05:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01) 05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01) 06:01.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet

Hello all ! I get the same effect when mounting nfs-exported directories from dom0 in domU. Every mount/umount/showmount command in domU produces the message in the dom0 syslog. I run 2.0.6 compiled from source, with 2.6 dom0 and 2.4 domU on a P4 HT 3.2Ghz. Perhaps this helps to track the problem down. Greetings, Martin ---------- The messages : (dom0 hostname is zen, domU hostname is ftp,

> I get the same effect when mounting nfs-exported directories > from dom0 in domU. > Every mount/umount/showmount command in domU produces the > message in the dom0 syslog. > > I run 2.0.6 compiled from source, with 2.6 dom0 and 2.4 domU > on a P4 HT 3.2Ghz. This is a native Linux bug. A patch has been submitted upstream, but is already in our 2.0-testing and unstable

Hello ext3-users, we have an oopsy situation here: we have 4 machines: 3 client nodes, 1 master: the master holds a fairly big repository of small files. The repo's current size is ~40GB with ~1.2 M files in ~100 directories. Now, we like to rsync changes from the master to the client nodes, which is working perfectly for 2 nodes, but our 3rd node oopses "sometimes", rendering

xen: use iret directly where possible Most of the time we can simply use the iret instruction to exit the kernel, rather than having to use the iret hypercall - the only exception is if we're returning into vm86 mode, or from delivering an NMI (which we don't support yet). When running native, iret has the behaviour of testing for a pending interrupt atomically with re-enabling

xen: use iret directly where possible Most of the time we can simply use the iret instruction to exit the kernel, rather than having to use the iret hypercall - the only exception is if we're returning into vm86 mode, or from delivering an NMI (which we don't support yet). When running native, iret has the behaviour of testing for a pending interrupt atomically with re-enabling