search for: freeze

...lin at dberlin.org> wrote: > > > On Sun, Oct 23, 2016 at 9:30 AM, Nuno Lopes <nuno.lopes at ist.utl.pt> wrote: > >> > So just to be clear (mainly so i can go back to letting y'all hash this >> out), in value numbering: >> > 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...

> So just to be clear (mainly so i can go back to letting y'all hash this out), in value numbering: > 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 ma...

The fact two IR values are defined the same way doesn't necessarily imply 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...

On Tue, Oct 25, 2016 at 10:19 AM, Nuno Lopes <nuno.lopes at ist.utl.pt> wrote: > >>>> So just to be clear (mainly so i can go back to letting y'all hash > this out), in value numbering: > >>>> 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...

> 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

...70]: Vacuuming is disabled for persistent database registry.tdb 2014/02/26 11:58:55.986739 [6553670]: Vacuuming is disabled for persistent database secrets.tdb 2014/02/26 11:58:56.034569 [6553670]: Vacuuming is disabled for persistent database share_info.tdb 2014/02/26 11:58:56.034715 [6553670]: Freeze priority 1 2014/02/26 11:58:56.040888 [6553670]: Freeze priority 2 2014/02/26 11:58:56.043987 [6553670]: Freeze priority 3 2014/02/26 11:58:56.437970 [6553670]: Freeze priority 1 2014/02/26 11:58:56.438152 [6553670]: Freeze priority 2 2014/02/26 11:58:56.438292 [6553670]: Freeze priority 3 2014/02/...

Hi Peter, Should 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...

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 == %a. It is a normal SSA value with some unspecific...

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 instr...

...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?

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" agent command via libvirt, thus you must have the guest agent the same way as you used it before. Using qemu-agent-command is a backdoor for testing arbi...

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...

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) bi...

> 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 be simplified to...

...expectation is somewhat reasonable. In our compiler, the clamp gets replaced by the logically equivalent corresponding sequence of icmp/select instructions, which leads to multiple reads from v, which changes the result when v is undef. We should be able to fix this in our compiler by inserting a freeze instruction, but to me this raises 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 c...

...C:\ProgramData\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...

After upgrading one of our servers from Fedora 7 to Fedora 9, from Samba 3.0 to 3.2.0-2.17.fc9 I noticed this strange phenomena: Windows 2003 and XP clients freeze when you type "\\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....

Hello, I recently installed Ubuntu 24.04 on a MacBook Pro (Mid-2010) running a NVIDIA GeForce GT 330M adapter. Unfortunately the computer is constantly freezing. If I pass "nomodeset" to grub, the nouveau driver is not used and the computer does not freeze so it seems to be related to the nouveau driver. I am wanting to know if there are any parameters I can pass to nouveau to resolve the freezing. I have tried temporarily replacing nomodeset with nouveau.noaccel=1 then with nouveau.nofbaccel=1 but both caused the booting to freeze. I have also tr...

...w. There have been a few proposals, but they've all failed to pass the bar and/or to gather significant support (my own proposals included). We (David, Gil, John, Juneyoung, Sanjoy, Youngju, Yoonseung, and myself) have a new proposal to kill undef instead and replace it with poison + a new 'freeze' instruction. We believe this proposal simplifies things at the IR level, allows us to fix long-standing bugs in LLVM, and is roughly performance-neutral for now (and can enable further optimizations in the future). Sorry for the longish email. We will give a talk about this proposal at the...