search for: waken

Zhang, Xiantao wrote: >>From 62895ff991d48398a77afdbf7f2bef127e802230 Mon Sep 17 00:00:00 2001 > From: Xiantao Zhang <xiantao.zhang at intel.com> > Date: Fri, 28 Mar 2008 09:49:57 +0800 > Subject: [PATCH] KVM: IA64: Add kvm arch-specific core code for > kvm/ia64. > > kvm_ia64.c is created to handle kvm ia64-specific core logic. > Signed-off-by: Xiantao Zhang

Zhang, Xiantao wrote: >>From 62895ff991d48398a77afdbf7f2bef127e802230 Mon Sep 17 00:00:00 2001 > From: Xiantao Zhang <xiantao.zhang at intel.com> > Date: Fri, 28 Mar 2008 09:49:57 +0800 > Subject: [PATCH] KVM: IA64: Add kvm arch-specific core code for > kvm/ia64. > > kvm_ia64.c is created to handle kvm ia64-specific core logic. > Signed-off-by: Xiantao Zhang

...19,24 +236,30 @@ static void pv_wait_node(struct mcs_spinlock *node) > } > > /* > + * Called after setting next->locked = 1 & lock acquired. > + * Check if the the CPU has been halted. If so, set the _Q_SLOW_VAL flag > + * and put an entry into the lock hash table to be waken up at unlock time. > */ > -static void pv_kick_node(struct mcs_spinlock *node) > +static void pv_scan_next(struct qspinlock *lock, struct mcs_spinlock *node) I'm not too sure about that name change.. > { > struct pv_node *pn = (struct pv_node *)node; > + struct __qspinl...

...19,24 +236,30 @@ static void pv_wait_node(struct mcs_spinlock *node) > } > > /* > + * Called after setting next->locked = 1 & lock acquired. > + * Check if the the CPU has been halted. If so, set the _Q_SLOW_VAL flag > + * and put an entry into the lock hash table to be waken up at unlock time. > */ > -static void pv_kick_node(struct mcs_spinlock *node) > +static void pv_scan_next(struct qspinlock *lock, struct mcs_spinlock *node) I'm not too sure about that name change.. > { > struct pv_node *pn = (struct pv_node *)node; > + struct __qspinl...

...after the sync starts, it hangs. At this point, the NFS host(hosting the --backup-dir) responds just fine. However, the rsync host can only be accessed via console(no ssh, no ping...Nothing). Now here's the kicker: once I access the rsync host, it resumes the transfer as if it was waiting to be wakened. If I stay logged in and wait for it to hang again, all that is required for the sync to resume is a touch of the keyboard again, as if it was somehow waiting to be wakened. One important thing I should mention is if I unmount the NFS share and run the command with the --backup-dir to the local...

Peter Mladek reported that balloon might never refill completely after restore. This is because fill_balloon is only called once there. Calling fill_balloon repeatedly seems too aggressive, especially in light of the fact that it sleeps on failure: let's wake the config change handler and fill it asynchronously. Reported-by: Petr Mladek <pmladek at suse.com> Signed-off-by: Michael S.

Peter Mladek reported that balloon might never refill completely after restore. This is because fill_balloon is only called once there. Calling fill_balloon repeatedly seems too aggressive, especially in light of the fact that it sleeps on failure: let's wake the config change handler and fill it asynchronously. Reported-by: Petr Mladek <pmladek at suse.com> Signed-off-by: Michael S.

...to test this - for some reason my test VM > doesn't resume (with or without the patch). > Petr, does this work for you? Ah, I have just realized that the problem happens only after the conversion to the workqueue. It works without this patch with the current code. The balloon kthread is waken when released from __refrigerator(). I am sorry for the noise. I wanted to split the conversion to workqueues into two patches to make it better readable. We need to queue the balloon resizing work here. I wrongly assumed that the original kthread must have the same problem. Best Regards, Petr &...

...here''s only one idle domain now. However I''m not sure why something will go wrong when NR_CPUS > MAX_VIRT_CPUS. As long as you want to wake up an AP, you have to go through do_boot_cpu where idle_vcpu will be created. The only drawback is that some physical cpus will not be waken up by "max_cpus = MAX_VIRT_CPUS" you mentioned in another thread. That needs to be fixed which however shouldn''t crash anything since uninitialized cpus won''t be used. Thanks, Kevin _______________________________________________ Xen-devel mailing list Xen-devel@lis...

...nal smp kernel. Is it advisable to use ext-3 and RedHat 7.2 for a software raid0 root filesystem? I understand 7.2 uses a 2.4.7 kernel. I would like to use the smp kernel as this is a 2 proc. box. Stuart __________________________________________________________ I fear that all we have done is to waken a sleeping giant, and fill him with a terrible resolve. -- Admiral Isoroku Yamamoto after the Pearl Harbor Attack

...development tag. And it work as expected on the 5115 with the serial interface. So to Wolfgang, no bug introduced in the serial module when you split'ed the driver. If i get some time to spare, i have a look on the serial module to make it wake up the ups. The 9125 is type pnp so it need to be waken up. Then there are some cleanup to be done to the code. Kjell

...t causes confusion based on the feedbacks from the previous discussion; - xb_preload: with the original implementation, the CPU that successfully do __radix_tree_preload() may get into sleep by kmalloc(), which has a risk of getting the caller of xb_preload() scheduled to another CPU after waken up, and the new CPU may not have radix_tree_node pre-allocated there, this will be a problem when inserting a node to the tree later. This patch moves __radix_tree_preload() after kmalloc() and returns a boolean to indicate the success or failure. Also, add the __must_check annotation to xb...

On Wed, Mar 25, 2015 at 03:47:39PM -0400, Konrad Rzeszutek Wilk wrote: > Ah nice. That could be spun out as a seperate patch to optimize the existing > ticket locks I presume. Yes I suppose we can do something similar for the ticket and patch in the right increment. We'd need to restructure the code a bit, but its not fundamentally impossible. We could equally apply the head hashing to

On Wed, Mar 25, 2015 at 03:47:39PM -0400, Konrad Rzeszutek Wilk wrote: > Ah nice. That could be spun out as a seperate patch to optimize the existing > ticket locks I presume. Yes I suppose we can do something similar for the ticket and patch in the right increment. We'd need to restructure the code a bit, but its not fundamentally impossible. We could equally apply the head hashing to

https://bugs.freedesktop.org/show_bug.cgi?id=31139 Summary: Wake from sleep doesn't turn on display(s) Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

Hi all, <p>i have readed all the realy sad stuff about software patents in europe and what allread exists. There is one side related to speex and i dont know if this is allready discussed here. Take a look at: http://swpat.ffii.org/patents/effects/voip/index.en.html Is speex realy petant free or does patent free only means that is is not patent by the speex authors? Who have checked that

...ode) } /* - * Called after setting next->locked = 1, used to wake those stuck in - * pv_wait_node(). + * Called after setting next->locked = 1 & lock acquired. + * Check if the the CPU has been halted. If so, set the _Q_SLOW_VAL flag + * and put an entry into the lock hash table to be waken up at unlock time. */ -static void pv_kick_node(struct mcs_spinlock *node) +static void pv_scan_next(struct qspinlock *lock, struct mcs_spinlock *node) { struct pv_node *pn = (struct pv_node *)node; + struct __qspinlock *l = (void *)lock; /* - * Note that because node->locked is alread...

...in parallel. I did a lot of investigation and it seemed that we did not need any extra sychronization. Anyway, I rather made the split in a separate patch. See the patch description for more details. Changes against v4: + removed fix of the balloon restore code; it was false alarm; freezer waken the kthread and it restored the balloon later + added a spin lock to prevent updating the balloon when being removed + split the work into two; it allows to update stats even when the balloon is being resized Changes against v3: + rebased on 4.4-rc3 + call cancel_work_sync() when...

...in parallel. I did a lot of investigation and it seemed that we did not need any extra sychronization. Anyway, I rather made the split in a separate patch. See the patch description for more details. Changes against v4: + removed fix of the balloon restore code; it was false alarm; freezer waken the kthread and it restored the balloon later + added a spin lock to prevent updating the balloon when being removed + split the work into two; it allows to update stats even when the balloon is being resized Changes against v3: + rebased on 4.4-rc3 + call cancel_work_sync() when...

...ock_slowpath(struct qspinlock *lock) +{ + struct mcs_spinlock *node = pv_tail_to_qhead(atomic_read(&lock->val)); + + /* + * Found the queue head, now release the lock before waking it up + * If unfair lock is enabled, this allows other ready tasks to get + * lock before the halting CPU is waken up. + */ + __queue_spin_unlock(lock); + pv_kick_node(node); +} +EXPORT_SYMBOL(queue_spin_unlock_slowpath); +#endif /* CONFIG_PARAVIRT_SPINLOCKS */ -- 1.7.1