search for: freezes

...e operand to the >> same value >> > *as long as* >> > 2. I replace all freeze values of the same operand with a single one. >> > >> > Or am i misunderstanding? >> > If i've got it right, the issue i see with #2 is whether i can hoist >> freezes or not. >> > >> > If not, it may not be possible to cover all uses. >> > >> > IE >> > if (a) { >> > %1 = freeze (%x) >> > } else if (b) { >> > %2 = freeze (%x) >> > } else if (c){ >> > %3 = freeze (%x)...

...g: > 1. I can value number all freeze operations on the same operand to the same value > *as long as* > 2. I replace all freeze values of the same operand with a single one. > > Or am i misunderstanding? > If i've got it right, the issue i see with #2 is whether i can hoist freezes or not. > > If not, it may not be possible to cover all uses. > > IE > if (a) { > %1 = freeze (%x) > } else if (b) { > %2 = freeze (%x) > } else if (c){ > %3 = freeze (%x) > } > > I cannot replace these with a single freeze def without placing a fre...

...mply they are actually the same value. e.g. %a = load volatile i32, i32* %p %b = load volatile i32, i32* %p As Sanjoy said, though, it should always be legal to optimize all uses of different "freeze(%x)" values to use the same def - this is equivalent to choosing the same value for all freezes. It's just not necessary to do so. On Thu, Oct 20, 2016 at 1:58 PM, Krzysztof Parzyszek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > In both of these cases, the expression tree in the IR is going to look like > == (freeze(%x), freeze(%x)) > > The %a and %b are just...

...> >>>> *as long as* > >>>> 2. I replace all freeze values of the same operand with a single one. > >>>> > >>>> Or am i misunderstanding? > >>>> If i've got it right, the issue i see with #2 is whether i can hoist > freezes or not. > >>>> > >>>> If not, it may not be possible to cover all uses. > >>>> > >>>> IE > >>>> if (a) { > >>>> %1 = freeze (%x) > >>>> } else if (b) { > >>>> %2 = freeze (%x...

> Only freezing it will > replace it with something concrete such that if x is poison then > freeze(x) == freeze(x), etc. Nit: it's not true that freeze(x) == freeze(x) in the current proposal. Each freeze can choose its own value. John

Hello, I've got a two node CTDB/Samba cluster that I'm having trouble with trying to add back a node after having to do an OS reload on it. The servers are running CTDB 2.5.1 and Samba 4.1.4 on AIX 7.1 TL2. The Samba CTDB databases and Samba service work fine from the node that was not reloaded. The rebuilt node is failing to re-add itself to the cluster. I'm looking for

...hould I assume that the virsh domfsfreeze, does not require the qemu-agent service in the guest? PS. I couldn't find the result. Afaik it looks like it is returning the amount of frozen/thawed filesystem's -----Original Message----- Cc: libvirt-users Subject: Re: guest-fsfreeze-freeze freezes all mounted block devices On Fri, Feb 14, 2020 at 22:14:55 +0100, Marc Roos wrote: > > I wondered if anyone here can confirm that > > virsh qemu-agent-command domain '{"execute":"guest-fsfreeze-freeze"}' Note that libvirt implements this directly via '...

Hi Krzysztof, Krzysztof Parzyszek wrote: > On 10/18/2016 4:29 PM, Nuno Lopes wrote: >> Even %a and %b might not be the same in "%a = freeze(%x), %b = >> freeze(%x)" (each freeze returns an arbitrary, but fixed, value). > > Assume that %x is known to be a poison value and have: > %a = freeze(%x) > %b = freeze(%x) > > Is %a == %a true? Yes, %a is always

Hi all, After a recent upstream merge into our downstream sources we are suddenly encountering the freeze instruction in LLVM IR for div/rem pairs. This seems to be related to [1]. Our downstream target is GlobalISel only and unfortunately GlobalISel doesn't support this instruction yet, so most of our internal test-suite is now breaking due to GlobalISel not being able to translate this

...ut of pocket for a while, so don't shoot me, if this has already been brought up. I'm having a problem with my desktop freezing up, and I'm running Cent OS 6. It seems to happen while I'm running firefox. I'm not sure if it's firefox, or the OS that's locking up. When it freezes up, nothing will respond, so I'm inclined to think it's the OS that's freezing up. Has anyone else been having this problem? Thanks Jim

I wondered if anyone here can confirm that virsh qemu-agent-command domain '{"execute":"guest-fsfreeze-freeze"}' Freezes all mounted block devices filesystems. So if I use 4 block devices they are all frozen for snapshotting. Or just the root fs?

...t-fsfreeze-status will remain "thawed" and calling # @guest-fsfreeze-thaw is not necessary. # # Since: 0.15.0 You might also want to have a look at 'guest-fsfreeze-freeze-list'. > > -----Original Message----- > Cc: libvirt-users > Subject: Re: guest-fsfreeze-freeze freezes all mounted block devices > > On Fri, Feb 14, 2020 at 22:14:55 +0100, Marc Roos wrote: > > > > I wondered if anyone here can confirm that > > > > virsh qemu-agent-command domain '{"execute":"guest-fsfreeze-freeze"}' > > Note that l...

Hi everybody, I am having a problem with the use of domfsfreeze command. It is freezing all the filesystems present on the domain, instead of freezing just the mountpoints provided. I am issuing the command-- # virsh domfsfreeze <domain> --mountpoint <mountpoint> Output was-- Froze 3 filesystem(s) I want to freeze a particular mount point on the VM, so that i can take a

Hi Krzysztof, freeze(poison) is different from undef today, in the sense that it is an instruction that produces some random, but fixed bit pattern. E.g. today in %x = undef %y = xor %x, %x we can fold %y to undef since each use of %x can independently see some arbitrary (up to the compiler / environment) bit pattern. But in the new proposal, in: %x = freeze(poison) %y = xor

> On 10/18/2016 3:12 PM, Sanjoy Das wrote: >> But in the new proposal, in: >> >> %x = freeze(poison) >> %y = xor %x, %x >> >> that is no longer allowed (%y _has_ to be 0) -- all uses of %x will see >> some garbage, but fixed bit pattern. > > What about this: > %x = phi poison, poison (I'm simplifying the syntax here) > Can this

...aises a more complicated point around function inlining that is illustrated by this example: https://alive2.llvm.org/ce/z/wcYxCB (I don't know if the output of Alive2 is meaningful here or if there are limitations around function calls). Function inlining in LLVM currently does *not* introduce freezes. However, calls to intrinsics such as llvm.minimum.* etc. are presumably expected to introduce freezes. So if we think of intrinsics as being implemented by library functions (as is de facto the case with the `clamp` example above), should those library functions be treated differently by inlining?...

...a\Microsoft\Windows\WER\ReportQueue\AppCrash_qemu-ga.exe_bd 2e6535bdb93328680e0285e89e08f2866db83_0b0deada Analysis symbol: Rechecking for solution: 0 Report Id: 3d82596e-517c-11ea-b213-525400e83365 Report Status: 0 -----Original Message----- Cc: libvirt-users Subject: Re: guest-fsfreeze-freeze freezes all mounted block devices On Mon, Feb 17, 2020 at 10:03:27 +0100, Marc Roos wrote: > Hi Peter, > > Should I assume that the virsh domfsfreeze, does not require the > qemu-agent service in the guest? No. That's the official way how to drive the "guest-fsfreeze-freeze" a...

...pe "\\server" in an explorer address bar where "server" is the name of the Samba 3.2 host. Windows 2000 clients don't freeze. 2003/XP clients don't freeze when you enter "\\server\share" They un-freeze if you restart samba, showing all the shares. Refreshing freezes them again. Here are some details on our network - all samba 3.0 and 3.2 hosts are ipv6 capable - some Windows clients are ipv6 capable - DNS hostnames resolve to both ipv4 and ipv6 addresses - NetBIOS over TCP is disabled, nmbd not running - all samba servers are ADS clients in a 2003 domain Her...

...el=1 but both caused the booting to freeze. I have also tried temporarily replacing nomodeset with nouveau.modeset=0 to disable nouveau but got a blank screen whilst booting (I've seen this blank screen reported by others on the web). I should be reporting a bug I assume but when the computer freezes I have to turn the computer off and therefore dmesg is not an option to provide logs. I have noticed in dmesg however 2 messages that read: nouveau 0000:01:00.0: gr: 00100000 [] ch 3 [001fa70000 gnome-shell[1509]] subc 3 class 8597 mthd 1304 data 1d1c1b1a followed by...... nouveau 0000:01:00.0:...

...s://docs.google.com/spreadsheets/d/1_xj6o_ANGcR8xD5Y9rN5VjWbsJaS-GeYKzeW WAR9O2c/edit#gid=0 Statistics on number of Freeze Instructions (up to 5% in total in gcc): https://docs.google.com/spreadsheets/d/1mbOpduooEetIR5i9Db07GHbu72a6mLUmkRIF 1SmZ-6Q/edit#gid=0 LNT raw data: https://github.com/aqjune/freezescript/tree/master/resultcsv-mailinglist/LNT Server1: Intel Core i7 CPU 870 @ 2.93GHz, 8 GBs RAM Server2: Intel Core i5-6600 CPU @ 3.30GHz, 8 GBs RAM Implementation ============== A prototype is available at: - https://github.com/snu-sf/llvm-freeze/tree/x86jmp - https://github.com/snu-sf/clang-...