search for: suspend

Hi Eli: >> semantics of the fork intrinsic... thinking about it a bit more, I think >> you're going to run into problems with trying to keep around a return block >> through optimizations: How about this? Make all control flow explicit (duh). declare i8 coro.suspend([...]) returns: 0 - resume 1 - cleanup anything else - suspend Now we can get rid of the coro.fork altogether. [...] %0 = call i8 @llvm.coro.suspend([...]) switch i8 %0, label %suspend [ i32 0, label %resume, i32 1, label %clea...

Hi Eli: >> Block1: >> %0 = call i8 coro.suspend() >> switch i8 %0, label suspend1 [i8 0 %return] ; or icmp + br i1 >> Suspend1: >> switch i8 %0, label %resume1 [i8 1 %destroy1] ; or icmp + br i1 >> >> This doesn't look right: intuitively the suspend happens after the return >> block runs. Perhap...

Everywhere else the constant is multiplied by 16/4, so it looks like nvc0_fence_suspend/resume is buggy here. Signed-off-by: Maarten Lankhorst <m.b.lankhorst at gmail.com> Cc: stable at vger.kernel.org [3.7+] --- diff --git a/drivers/gpu/drm/nouveau/nvc0_fence.c b/drivers/gpu/drm/nouveau/nvc0_fence.c index 85a0e78..4f46d8b 100644 --- a/drivers/gpu/drm/nouveau/nvc0_fence.c +++...

Hi, all, When working on adding PM support to xen, we realized that some enhancements are required to suspend/resume domU. Following is some background and thoughts, and welcome on comments. :-) Currently we use a simple approach (pause/unpause) for domU when ready to pull whole platform into a power save state, saying a S3. Because pause/unpause is out of domU''s knowledge, domU observes sof...

hello i think i found a bug i wanted nut to suspend to ram instead of powering off so i made a script that runs the commands but i ran into a problem i changed the shutdown command in upsmon.conf to my suspend script and i tested with upsmon -c fsd everything worked fine system went into suspend and i woke it backup by pressing the power button, now...

...the branch I have in linux-next plus some older PV on HVM fixes to stable-2.6.32.x. Please pull: git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git stable-2.6.32-pvhvm Ian Campbell (11): xen: do not respond to unknown xenstore control requests xen: use new schedop interface for suspend xen: switch to new schedop hypercall by default. xen: suspend: use HYPERVISOR_suspend for PVHVM case instead of open coding xen: suspend: refactor cancellation flag into a structure xen: suspend: pass extra hypercall argument via suspend_info struct xen: suspend: add &...

https://bugs.freedesktop.org/show_bug.cgi?id=79988 Priority: medium Bug ID: 79988 Assignee: nouveau at lists.freedesktop.org Summary: Suspend to ram stoped to work QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: marccollin7379 at gmail.com Hardware: Other Status: NEW Version: 7.6 (2010.12)...

nouveau's ->suspend and ->resume callbacks are currently skipped if the device's status is either DRM_SWITCH_POWER_OFF (powered off by vga_switcheroo manual power control) or DRM_SWITCH_POWER_DYNAMIC_OFF (runtime suspended). In the former case this makes sense since the device is powered off behind the PM core...

...gt; mutated > >> between the first return and the resume. > > Hmmm... I don't see the problem. I think hoisting the store is perfectly > legal > transformation with all semantics preserved. > > Let's look at your example: > > >> block1: > >> suspend > >> switch (resume, destroy, return) > >> > >> resume: > >> store zero to global @g > >> doA() > >> [...] > >> > >> destroy: > >> store zero to global @g > >> doB() > >> [...] > &g...

On Thu, Jun 9, 2016 at 1:49 PM, Eli Friedman <eli.friedman at gmail.com> wrote: >> Right... but that doesn't mean the call to the suspend intrinsic has to be >> the last non-terminator instruction in the basic block before you run >> CoroSplit. You can split the basic block in CoroSplit so any instructions >> after the suspend call are part of a different basic block. Then resume and >> destroy both branch t...

...API for the LLVM context diagnostic handler and used Andy’s suggested name for the callback. The opaque handle was suggested by Duncan and can provide optional user specified information that is provided back during the callback (i.e. barrier, etc). Cheers, Juergen Core.h: typedef void (*LLVMMaySuspendCallback)(LLVMContextRef, void *); /** * Set the may-suspend callback function for this context. * * @see LLVMContext::setMaySuspendCallback() */ void LLVMContextSetMaySuspendCallback(LLVMContextRef C, LLVMMaySuspendCallback Callback,...

Currently running Wine 1.2-rc2 on Ubuntu 10.04 x64 on a Lenovo ThinkPad x61. After doing a suspend, I can't run Wine. The app I normally run with Wine is Lotus Notes. But I've tried something as simple as going in to the wine config. I tried doing a wineserver -k but that doesn't help either. Only thing I found to work is a full reboot. This has actually been happening since Ubuntu...

Hi all. I'm having problems trying to suspend/hibernate my Dell Latitude D810 Laptop. Basically I have an ATI X600 videographics and SATA harddrive and run httpd and mysqld daemons on it. I use fglrx (ATI propietary drivers) and the open too with no success. I tried with 1 and 2 screens configurations with no success. I tried with CA and/o...

On Fri 03-07-20 10:34:09, Catangiu, Adrian Costin wrote: > This patch adds logic to the kernel power code to zero out contents of > all MADV_WIPEONSUSPEND VMAs present in the system during its transition > to any suspend state equal or greater/deeper than Suspend-to-memory, > known as S3. How does the application learn that its memory got wiped? S2disk is an async operation and it can happen at any time during the task execution. So how does t...

On Fri 03-07-20 10:34:09, Catangiu, Adrian Costin wrote: > This patch adds logic to the kernel power code to zero out contents of > all MADV_WIPEONSUSPEND VMAs present in the system during its transition > to any suspend state equal or greater/deeper than Suspend-to-memory, > known as S3. How does the application learn that its memory got wiped? S2disk is an async operation and it can happen at any time during the task execution. So how does t...

...you're going to run into problems with trying to keep around a return > block > >> through optimizations: > > Thinking about it a bit more, it is even simpler, I don't have to involve > coro.end in this case at all and should not worry about branches, RAUW-ing > coro.suspend with an appropriate constant takes care of it all. > > Here is an updated version. > 1) coro.fork is gone, gone gone!!!! > 2) coro.suspend is changed as follows: > > declare i8 coro.suspend([...]) > > returns: > 0 - in resume clone > 1 - in destroy...

The RHEL 5 release notes for their desktop version claim "Improved ACPI support with features such as suspend to disk" but this isn't working with CentOS 5. I've installed all the packages and updates for CentOS 5 i386 on a ThinkPad T43 but when selecting suspend, Gnome pops up a URL to a site that didn't seem to give a solution. Gnome makes an entry in /var/log/messages indicating that t...

How do I "enable" qemu-ga on a guest to be able to (I think this means have a success-response:true) for: guest-suspend-hybrid; guest-suspend-ram; guest-suspend-disk; and guest-shutdown? At least I think that's my question. http://wiki.stoney-cloud.org/wiki/Qemu_Guest_Agent_Integration shows these same 4 as false, so I'm not sure if they're always supposed to be that way. My overall point is to be able...

Hi Ben, On Tue, Nov 08, 2016 at 09:29:38PM +0100, Peter Wu wrote: > On Tue, Nov 08, 2016 at 12:57:00PM +0100, Lukas Wunner wrote: > > nouveau's ->suspend and ->resume callbacks are currently skipped if the > > device's status is either DRM_SWITCH_POWER_OFF (powered off by > > vga_switcheroo manual power control) or DRM_SWITCH_POWER_DYNAMIC_OFF > > (runtime suspended). > > > > In the former case this makes sense...

Changes since last sent: * add a patch to set the device into DRM_SWITCH_POWER_CHANGING state (can be dropped actually, I thought I was needing it, came up with a different approach and forgot to delete it, doesn't hurt though) * expose information about runtime suspending to nvkm so that we can run the pcie workaround only on runtime suspend Karol Herbst (8): pci: disable ASPM before changing the link speed pci/gk104: enable dl_mgr safe mode pci/gk104: wait for ltssm idle before changing the link pci: enable pcie link changes for pascal drm: set powe...