search for: resumpt

...ss them with high quality, with interesting optimization potential, and without loss of semantic fidelity. Furthermore, I believe that LLVM IR should be able to reasonably express the full range of behavior of the platform's exceptions implementation. Specifically, we should able to implement resumptive exception handlers on unwinders that support them, which (to summarize briefly) is all of above. Now, obviously, actually implementing codegen lowering for resumptive handlers is not an immediate priority (although the problems there roughly coincide with the problems we'd face in implement...

...want to consider immediately. Those are interesting questions, but they're separate questions, and we should settle on these basic requirements first. For example, if it's a real goal to make LLVM IR capable of supporting a wider range of unwinders than it currently can — at a gloss, non-resumptive EH with a single, non-reentrant landing pad per region and LSDA layout approximating what's consumed by __gxx_personality_v0 — then that touches on almost everything else. Contrariwise, if we're only really interested in finding a better fix to the current IPO problems, then maybe we ca...

...odepaths based on the boolean). I love it!!! it is so much simpler. Indeed, we absolutely don't need to care about the resume and cleanup branches. Let me restate the model as I understand it. Lowering of coro.suspend number X: 1) split block at coro.suspend, new block becomes jump point for resumption X 2) RAUW coro.suspend with i1 true in resume clone i1 false in destroy clone 3) replace coro.suspend with br %return.block in 'f', 'ret void' in clones Scratch the proposed corosuspend instruction. I think the intrinsic will work just fine! Gor

Hi John, I'll read your email with greater care along the week, but I have added a page on the wiki to help us organise our thoughts. http://wiki.llvm.org/Exception_Handling I'll change it as I go reading your email, but for now, I've separated into each of the requirements you said. New ones could be added, existing ones merged, but the most important is to add more complete

...ine? We handled this in WinEHPrepare by cloning any BBs which >> were shared. I experimented with several approaches, but, cloning ended up being the simplest and most reliable. Suspend points express three different control flows that can happen at the suspend point: a suspension (default), resumption (0) and destruction (1). %0 = call i8 @llvm.coro.suspend([..]) switch i8 %0, label %suspend [i8 0, label %resume, i8 1, label %destroy] I slap a switch that jumps to all suspend points in the function. Then I clone the function twice (one will become resume...

On Apr 13, 2011, at 21:43 CDT, John McCall wrote: > And it's okay to have limited goals! I personally don't; I think we > should aim to get the IR design good enough to support crazy resumptive > languages with crazy custom unwinding schemes. But I need to know what > range of problems we're willing to consider solving before I can usefully > weigh different solutions. I will dare a comment on this topic well over my head, so my answer will probably only reflect my ignor...

[Patch 4/4]: Xend interface for HVM S3 - extend "xm resume <domid>" to be able to S3 resume HVM domain. - when user issue "xm resume" command for HVM domain, xend will use xc lib API to call HVMOP_s3_resume hypercall. Note: it may not appropriate use xm resume for HVM s3, since xm resume is originally designed for save/restor purpose. It will be fine that

cc llvm-dev On Thu, Jul 21, 2016 at 9:57 AM, Vadim Chugunov <vadimcn at gmail.com> wrote: > Hi Gor, > Does you design support resumption with parameter(s)? (such as Python's > generator.send(x)). I suppose the "promise" could be used for passing data > both ways, but if that's the plan, please mention this explicitly in the > design doc. > Also, how is loading/storing to promise going to be lowered...

...negotiated Early data was not sent Verify return code: 0 (ok) --- --- Post-Handshake New Session Ticket arrived: SSL-Session: Protocol : TLSv1.3 Cipher : TLS_AES_256_GCM_SHA384 Session-ID: A9CA3DA57FDA9BF9D9EFBBD0E5CE5D8F7A5DE091C10E54310D52A23DCB7DA95B Session-ID-ctx: Resumption PSK: C7BA79D9FB045352371121AC97F891FBD4C2578AA48A7CD57747A941C6864CCE5163D5AF94BE01D75233148BD75E755E PSK identity: None PSK identity hint: None SRP username: None TLS session ticket lifetime hint: 7200 (seconds) TLS session ticket: 0000 - 6e fd 36 f6 0f 16 dc d0-f...

On May 4, 2011, at 8:23 AM, Evan Cheng wrote: >> I don't know how realistic it is to model the loop buffer in the register allocator, but this would a very interesting thing to try to optimize for in a later pass. If an inner loop "almost" fits, then it would probably be worth heroic effort to try to reduce the size of it to shave off a few bytes. > > Jakob and I have

hi, I seem to have a problem with the Linux xen-network driver leaking skbs. This is probably my own fault, upon resumption after migration I call this: void network_resume(void) { struct net_device* dev = __dev_get_by_name("eth0"); MOD_DEC_USE_COUNT; network_open(dev); } -- which works fine. However, in network_open() the call to NETOP_RESET_RINGS seems to clear all the pointers to the old s...

...a pointer to the exception handling object. The other is a "selector" value, that we can then use to determine which (if any) of the clauses should be run. > ...and then a miracle happens in CodeGen, and most of the intrinsics are thrown away and the > hard register contents at the resumption at a landingpad from an Unwind include the value that > llvm.eh.typeid.for() would have returned... > The llvm.eh.typeid.for is a hold-over from the old design. It's returns a constant value that can be compared against the "selector" the personality function returns. It rem...

...We also create a struct that will keep the objects that need to persist across suspend points. This transformation is done by CoroSplit CGSCC pass run as a part of the IPO optimizations pipeline. CoroElide Pass: (Function Pass @ EP_ScalarOptimizerLate extension point) --------------- The coroutine resumption intrinsics get replaced with direct calls to those outlined functions where possible. Then inliner can inline much leaner and nicer coroutine or any of the outlined parts as desired. If we discover that the lifetime of a coroutine is fully enclosed in the lifetime of the caller, we remove dynam...

...No ALPN negotiated Early data was not sent Verify return code: 0 (ok) --- --- Post-Handshake New Session Ticket arrived: SSL-Session: Protocol : TLSv1.3 Cipher : TLS_AES_256_GCM_SHA384 Session-ID: A9CA3DA57FDA9BF9D9EFBBD0E5CE5D8F7A5DE091C10E54310D52A23DCB7DA95B Session-ID-ctx: Resumption PSK: C7BA79D9FB045352371121AC97F891FBD4C2578AA48A7CD57747A941C6864CCE5163D5AF94BE01D75233148BD75E755E PSK identity: None PSK identity hint: None SRP username: None TLS session ticket lifetime hint: 7200 (seconds) TLS session ticket: 0000 - 6e fd 36 f6 0f 16 dc d0-f1 9f 02 4b 32 20 5...

...s does not change from the current scheme where the "llvm.eh.typeid.for()" is called and its result is compared with the landingpad instruction's result... ...and then a miracle happens in CodeGen, and most of the intrinsics are thrown away and the hard register contents at the resumption at a landingpad from an Unwind include the value that llvm.eh.typeid.for() would have returned... this is the sort of thing I'm talking about when I imply that the current scheme is poorly documented! Also, what is going to happen for the case of cleanup AND catches, currently the r...

...t 4:50 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Thu, Jun 9, 2016 at 2:33 PM, Gor Nishanov <gornishanov at gmail.com> wrote: >> >> Lowering of coro.suspend number X: >> >> 1) split block at coro.suspend, new block becomes jump point for >> resumption X >> 2) RAUW coro.suspend with i1 true in resume clone i1 false in destroy >> clone >> 3) replace coro.suspend with br %return.block in 'f', 'ret void' in clones >> >> Scratch the proposed corosuspend instruction. I think the intrinsic will >>...

...Blocks| |2076 Resolution|--- |FIXED CC| |djm at mindrot.org Status|NEW |RESOLVED --- Comment #4 from Damien Miller <djm at mindrot.org> --- Yes, resumption is implemented for both get and put now. Referenced Bugs: https://bugzilla.mindrot.org/show_bug.cgi?id=2076 [Bug 2076] Bugs intended to be fixed in 6.3 -- You are receiving this mail because: You are the assignee for the bug. You are watching someone on the CC list of the bug.

...st return if it isn't. This, together with commit d22915d22ded ("drm/nouveau/devinit/tu102-: wait for GFW_BOOT_PROGRESS == COMPLETED") developed independently and landed earlier, fixes runtime power management of the NVIDIA card in Lenovo Legion 5-15ARH05. Without this patch, the GPU resumption code will "timeout", sometimes hanging userspace. As a bonus, we'll also stop preventing _PR3 usage from the bridge for unrelated devices, which is always nice, I guess. Signed-off-by: Ratchanan Srirattanamet <peathot at hotmail.com> Closes: https://gitlab.freedesktop.org/d...

Just updated CentOS 9 Stream on a Lenovo T17 Gen 4 Intel and not it won't suspend with the following error: [ 52.604998] Restarting kernel threads ... done. [ 52.605111] OOM killer enabled. [ 52.605111] Restarting tasks ... done. [ 52.606604] random: crng reseeded on system resumption [ 52.616014] thermal thermal_zone9: failed to read out thermal zone (-61) [ 52.791625] PM: suspend exit [ 52.791733] PM: suspend entry (s2idle) [ 52.797260] Filesystems sync: 0.005 seconds [ 52.797579] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 52.799127] OOM k...

Hi, I have always wondered why it was called "--partial" and behaves as it does. I personnaly think that is an excellent idea, but rather than change the "--partial" behaviour why do we not have "--resumption" parameter instead to do exactly what has been suggested. Thanks Stephen