search for: 1,185

Hi all, I noticed that the x86 backend tends to emit unnecessary vector insert instructions immediately after sse scalar fp instructions like addss/mulss. For example: ///////////////////////////////// __m128 foo(__m128 A, __m128 B) { _mm_add_ss(A, B); } ///////////////////////////////// produces the sequence: addss %xmm0, %xmm1 movss %xmm1, %xmm0 which could be easily optimized into addss %xmm1, %xmm0 The first step is to understand why the compiler produces the redundant instructions....

Signed-off-by: Yuval Shaia <yuval.shaia at oracle.com> --- hw/Kconfig | 1 + hw/rdma/Kconfig | 4 + hw/rdma/Makefile.objs | 2 + hw/rdma/virtio/virtio-rdma-ib.c | 287 ++++++++++++++++++++ hw/rdma/virtio/virtio-rdma-ib.h | 93 +++++++ hw/rdma/virtio/virtio-rdma-main.c | 185 +++++++++...

hi, I've written a start of an c32-module to do basic substition: add subst.c32 this is a start of a generic substition module --- commit 9a1f41a7e6599fe6a162197cd9ddc6610185e780 tree cfb799a0be9844926afe44e21b2eb96630666c44 parent 89478bdbfa7167bc1b627a478d042c99e46f06b7 author Maurice Massar <massar at unix-ag.uni-kl.de> Tue, 10 Apr 2007 20:13:39 +0200 committer Maurice Massar <massar at unix-ag.uni-kl.de> Tue, 10 Apr 2007...

...options for remote disks and libvirt access, much like other libguestfs tools. virt-builder --get-kernel now just spawns virt-get-kernel. --- .gitignore | 5 ++ Makefile.am | 3 +- builder/Makefile.am | 2 - builder/builder.ml | 15 +++- builder/get_kernel.ml | 92 -------------------- builder/get_kernel.mli | 19 ----- configure.ac | 1 + get-kernel/Makefile.am | 146 ++++++++++++++++++++++++++++++++ get-kernel/get_kernel.ml | 185 +++++++++++++++++++++++++++++++++++++++++...

libswfdec/Makefile.am | 7 - libswfdec/swfdec_as_strings.c | 2 libswfdec/swfdec_load_object.c | 215 +++++++++++++++++++++++++++++++++++++ libswfdec/swfdec_load_object.h | 35 ++---- libswfdec/swfdec_load_object_as.c | 48 ++++++++ libswfdec/swfdec_load_object_as.h | 31 +++++ libswfdec/swfdec_player.c | 5 libswfdec/swfdec_player_internal.h | 1 libswfdec/swfdec_xml...

...-+ +--|---+ +--|---+ +--|---+ +--V----+---V---+----V---+ +--V----+---V---+----V---+ | group | group | default| | group | group | default| band groups | | | group | | | | group | +-------+-------+--------+ +-------+-------+--------+ | band1 | | band2 | band devices +-----------|------------+ +-----------|------------+ +-----------V--------------+-------------V------------+ | | | | sdb1 | sdb2 | physical dev...

...-+ +--|---+ +--|---+ +--|---+ +--V----+---V---+----V---+ +--V----+---V---+----V---+ | group | group | default| | group | group | default| band groups | | | group | | | | group | +-------+-------+--------+ +-------+-------+--------+ | band1 | | band2 | band devices +-----------|------------+ +-----------|------------+ +-----------V--------------+-------------V------------+ | | | | sdb1 | sdb2 | physical dev...

This introduces vringh, which are generic accessors for virtio rings (host side). There's a host-side implementation in vhost, but it assumes that the rings are in userspace, and is tied to the vhost implementation. I have patches to adapt it to use vringh, but I'm pushing this in the next merge window for Sjur, who has CAIF patches which need it. This also includes a test program in

This introduces vringh, which are generic accessors for virtio rings (host side). There's a host-side implementation in vhost, but it assumes that the rings are in userspace, and is tied to the vhost implementation. I have patches to adapt it to use vringh, but I'm pushing this in the next merge window for Sjur, who has CAIF patches which need it. This also includes a test program in

...e can expect only that driver is (partialy) loaded and basic queries and resource allocation is done. One note regarding the patchset. I know it is not standard to collaps patches from several repos as i did here (qemu and linux) but decided to do it anyway so the whole picture can be seen. patch 1: virtio-net: Move some virtio-net-pci decl to include/hw/virtio This is a prelimenary patch just as a hack so i will not need to impelement new netdev patch 2: hw/virtio-rdma: VirtIO rdma device The implementation of the device patch 3: RDMA/virtio-rdma: VirtIO rdma driver The device driver --...

...e can expect only that driver is (partialy) loaded and basic queries and resource allocation is done. One note regarding the patchset. I know it is not standard to collaps patches from several repos as i did here (qemu and linux) but decided to do it anyway so the whole picture can be seen. patch 1: virtio-net: Move some virtio-net-pci decl to include/hw/virtio This is a prelimenary patch just as a hack so i will not need to impelement new netdev patch 2: hw/virtio-rdma: VirtIO rdma device The implementation of the device patch 3: RDMA/virtio-rdma: VirtIO rdma driver The device driver --...

...d. attached the updated patch to apply to svn/trunk. j -------------- next part -------------- A non-text attachment was scrubbed... Name: theora-mmx.patch.gz Type: application/x-gzip Size: 8648 bytes Desc: not available Url : http://lists.xiph.org/pipermail/theora-dev/attachments/20040824/5a5f2731/theora-mmx.patch-0001.bin

libswfdec-gtk/swfdec_gtk_loader.c | 57 ++++-- libswfdec/Makefile.am | 8 libswfdec/swfdec_as_array.c | 9 - libswfdec/swfdec_as_context.c | 42 ++-- libswfdec/swfdec_as_frame.c | 14 - libswfdec/swfdec_as_frame_internal.h | 3 libswfdec/swfdec_as_interpret.c | 44 +++- libswfdec/swfdec_as_object.c | 129 ++++++++------ libswfdec/swfdec_as_object.h | 29 ++- libswfdec/swfdec_as_string.c | 73 +...

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