search for: _while_

"3" for advanced options does not have an effect _while_ the vm-message is played. all other options like "7" delete or "6" next message are working. after the vm-message is played, it's working. the question: is this intentional? or a bug? the available documentation does not describe this case. Kristijan

...on depends on virtual register values that are not available at the new location. [Larin, Sergei] This looks similar to the previous case. Good thing that you can potentially have zero cost remat (if you can place your new instruction inside existing bundle), but to know this you need an answer _while_ you are computing the cost. For that I can easily imagine a back end hook of something like CanAddMIToBundle(MI, BundleHeader). This is often easier than the previous task. 3. Remat. LiveRangeEdit::rematerializeAt() calls TII.reMaterialize() (sic) to insert a copy of the defining instruction at th...

...or_code: call *%edi jmp ret_from_exception CFI_ENDPROC -.previous +KPROBE_EXIT = ENTRY(coprocessor_error) RING0_INT_FRAME @@ -715,7 +715,7 @@ debug_stack_correct: call do_debug jmp ret_from_exception CFI_ENDPROC -.previous +KPROBE_EXIT = /* * NMI is doubly nasty. It can happen _while_ we're handling @@ -795,12 +795,12 @@ nmi_16bit_stack: call do_nmi RESTORE_REGS lss 12+4(%esp), %esp # back to 16bit stack -1: INTERRUPT_RETURN - CFI_ENDPROC -.section __ex_table,"a" +1: iret + CFI_ENDPROC +.pushsection __ex_table,"a" .align 4 .long 1b,iret_exc -.p...

...or_code: call *%edi jmp ret_from_exception CFI_ENDPROC -.previous +KPROBE_EXIT = ENTRY(coprocessor_error) RING0_INT_FRAME @@ -715,7 +715,7 @@ debug_stack_correct: call do_debug jmp ret_from_exception CFI_ENDPROC -.previous +KPROBE_EXIT = /* * NMI is doubly nasty. It can happen _while_ we're handling @@ -795,12 +795,12 @@ nmi_16bit_stack: call do_nmi RESTORE_REGS lss 12+4(%esp), %esp # back to 16bit stack -1: INTERRUPT_RETURN - CFI_ENDPROC -.section __ex_table,"a" +1: iret + CFI_ENDPROC +.pushsection __ex_table,"a" .align 4 .long 1b,iret_exc -.p...

Just to clarify, I'm looking at this from an application layer Point of View. One of the reasons why I'm looking at it that way, is because Tim said he was looking at LinuxHA..."application level" redundancy that uses IP. Tim, just to let you know, I don't believe that LinuxHA will work in the way you described, only because of the different IP ranges. It looks like Linux

On Jun 7, 2012, at 10:25 AM, "Sergei Larin" <slarin at codeaurora.org> wrote: > Generally as far as I concern, there is no way “generic” (platform independent) code can add instructions to bundles optimally I agree, there are too many ways of modeling stuff with bundles. That is why I took the philosophical stance of treating bundles as black boxes during RA. I think the

Hi all, I had asked the other day about my new machine amd 6000+ and strangely SLOWWING down then eventually stopping. I have tried a new 500W power supply, I took out the extra video card, and just used the one on the motherboard (both are nvidia one with DVI one RGB). I took out all the RAM and tried differnent RAM. I ran memtest86 (ran fine until the machine turn off). Harddrives should be

...alues that are not > available at the new location. > > */[Larin, Sergei] This looks similar to the previous case. Good thing > that you can potentially have zero cost remat (if you can place your > new instruction inside existing bundle), but to know this you need an > answer _while_ you are computing the cost. For that I can easily > imagine a back end hook of something like CanAddMIToBundle(MI, > BundleHeader). This is often easier than the previous task./* > I like the idea. The cost can potentially be zero, at least from a latency point of view (we care about p...

Hi everyone, I hope this is the correct list to discuss this issue; please feel free to redirect me otherwise. I have a nested virtualization setup that looks as follows: - Host: Ubuntu 16.04, kernel 4.4.0 (an OpenStack Nova compute node) - L0 guest: openSUSE Leap 42.3, kernel 4.4.104-39-default - Nested guest: SLES 12, kernel 3.12.28-4-default The nested guest is configured with

Hello! I am about to buy a new computer, and because encoding/decoding .ogg files is the most processor intensive thing I intend to regularly do, I would like to know which is the "recommended" processor for real-time encoding (I record my favourite radio shows). TIA! Bye, Joane Lispton PS: I receive the FM radio stations through my cable (the one which brings me cable TV),

...vailable >> at the new location. >> >> */[Larin, Sergei] This looks similar to the previous case. Good thing >> that you can potentially have zero cost remat (if you can place your >> new instruction inside existing bundle), but to know this you need an >> answer _while_ you are computing the cost. For that I can easily >> imagine a back end hook of something like CanAddMIToBundle(MI, >> BundleHeader). This is often easier than the previous task./* >> > > I like the idea. The cost can potentially be zero, at least from a > latency point o...

...ive migration? >> >> Following up from our IRC discussion (on #kvm, Freenode). Re-posting my >> comment here: >> >> So I just did a test of 'managedsave' (which is just "save the state of >> the running VM to a file" in libvirt parlance) of L1, _while_ L2 is >> running, and I seem to reproduce your case (see the call trace >> attached). >> >> # Ensure L2 (the nested guest) is running on L1. Then, from L0, do >> # the following: >> [L0] $ virsh managedsave L1 >> [L0] $ virsh start L1 --con...

...ing the > L0 guest to support managed save and live migration? Following up from our IRC discussion (on #kvm, Freenode). Re-posting my comment here: So I just did a test of 'managedsave' (which is just "save the state of the running VM to a file" in libvirt parlance) of L1, _while_ L2 is running, and I seem to reproduce your case (see the call trace attached). # Ensure L2 (the nested guest) is running on L1. Then, from L0, do # the following: [L0] $ virsh managedsave L1 [L0] $ virsh start L1 --console Result: See the call trace attached to this bug. But L1...

...rt managed save and live migration? > > Following up from our IRC discussion (on #kvm, Freenode). Re-posting my > comment here: > > So I just did a test of 'managedsave' (which is just "save the state of > the running VM to a file" in libvirt parlance) of L1, _while_ L2 is > running, and I seem to reproduce your case (see the call trace > attached). > > # Ensure L2 (the nested guest) is running on L1. Then, from L0, do > # the following: > [L0] $ virsh managedsave L1 > [L0] $ virsh start L1 --console > > Result: See...

...three keys. three hard-to-remember overloaded keys to boot... > I've never found it useful > to have an "as I type" preview. i have. i've found it to be _tremendously_ useful. well, i prefer if there's a slight delay in the update, so it doesn't trigger _while_ i'm writing, but rather after any pause, the length of which is user-chosen. (does anyone here remember the "showdown" site?) > I've never found it useful > to have an "as I type" preview. > Therefore it's not in Composer. again, it woulda bee...

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths