search for: l921

...chine scheduling in the same version of the code. As for live-through information, we found that the machine scheduler does call initLiveThru() and here is a pointer to the code: https://gitlab.com/CSUS_LLVM/LLVM_DRAGONEGG/blob/master/Generic/llvmTip/llvm-master/lib/CodeGen/MachineScheduler.cpp#L921 And here is a pointer to the function initLiveThru() https://gitlab.com/CSUS_LLVM/LLVM_DRAGONEGG/blob/master/Generic/llvmTip/llvm-master/lib/CodeGen/RegisterPressure.cpp#L318 Thanks Ghassan Shobaki Assistant Professor of Computer Science California State University, Sacramento ___________...

Any idea what 'virt-customize' script I should use to convert from virtio-blk (vda, vdb...) to virtio-scsi (sda, sdb...) ? I've tried naively to convince libvirt to use virtio-scsi and still present it to the guest as 'vd*' - that didn't work ( <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/>

...9;s what virt-v2v does, although virt-v2v is especially complicated because it supports doing this for everything back to RHEL 3(!) You probably only need to run dracut if you only care about modern Fedora & RHEL. https://github.com/libguestfs/libguestfs/blob/master/v2v/convert_linux.ml#L794-L921 > I've tried naively to convince libvirt to use virtio-scsi and still present > it to the guest as 'vd*' - that didn't work ( Yeah the target dev names in libvirt XML aren't really arbitrary strings. Device names are controlled by the *guest* kernel, nothing to do with...

...hough virt-v2v is especially > complicated because it supports doing this for everything back to RHEL 3(!) > You probably only need to run dracut if you only care about modern > Fedora & RHEL. > > > https://github.com/libguestfs/libguestfs/blob/master/v2v/convert_linux.ml#L794-L921 > > > I've tried naively to convince libvirt to use virtio-scsi and still > present > > it to the guest as 'vd*' - that didn't work ( > > Yeah the target dev names in libvirt XML aren't really arbitrary > strings. Device names are controlled by the *g...

> On Aug 30, 2017, at 1:43 PM, Matthias Braun <matze at braunis.de> wrote: > > That means you cannot use the code from RegisterPressure.{cpp|h} to compute this. The other liveness analysis we have in llvm codegen is LiveIntervals (LiveItnervalAnalysis) which gives you a list of liveness segments of a given vreg (the same representation is used in most linear scan allocators even