[Qemu-commits] [qemu/qemu] 3d1bba: glib: Fix some misuses of gsize/size_t types

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: 3d1bba20913356ff4f8ff2c38519f10c5f4b77e6
      
https://github.com/qemu/qemu/commit/3d1bba20913356ff4f8ff2c38519f10c5f4b77e6
  Author: Peter Crosthwaite <address@hidden>
  Date:   2013-05-22 (Wed, 22 May 2013)

  Changed paths:
    M hw/nvram/fw_cfg.c
    M qemu-char.c

  Log Message:
  -----------
  glib: Fix some misuses of gsize/size_t types

This unbreaks cross compile builds:

configure --target-list="i386-softmmu" --cpu=i386

When building on a 64bit machine.

Reported-by: David Holsgrove <address@hidden>
Signed-off-by: Peter Crosthwaite <address@hidden>
Reviewed-by: Paolo Bonzini <address@hidden>
Reviewed-by: Edgar E. Iglesias <address@hidden>
Message-id: address@hidden
Signed-off-by: Anthony Liguori <address@hidden>


  Commit: 95916abcf428fb03644468c7fbce64356c6483c0
      
https://github.com/qemu/qemu/commit/95916abcf428fb03644468c7fbce64356c6483c0
  Author: Peter Crosthwaite <address@hidden>
  Date:   2013-05-22 (Wed, 22 May 2013)

  Changed paths:
    M qom/object.c

  Log Message:
  -----------
  qom/object: Don't poll cast cache for NULL objects

object_dynamic_cast_assert used to be tolerant of NULL objects and not
assert. It's clear from the implementation that this is the expected
behavior.

The preceding check of the cast cache dereferences obj however causing
a segfault. Fix by conditionalizing the cast cache logic on obj being
non-null.

Signed-off-by: Peter Crosthwaite <address@hidden>
Reviewed-by: Andreas Färber <address@hidden>
Reviewed-by: Anthony Liguori <address@hidden>
Reviewed-by: Paolo Bonzini <address@hidden>
Reviewed-by: Edgar E. Iglesias <address@hidden>
Message-id: address@hidden
Signed-off-by: Anthony Liguori <address@hidden>


  Commit: 17bf9735dd5a46d829cfb175703c6a2c254a9aa2
      
https://github.com/qemu/qemu/commit/17bf9735dd5a46d829cfb175703c6a2c254a9aa2
  Author: Brad Smith <address@hidden>
  Date:   2013-05-22 (Wed, 22 May 2013)

  Changed paths:
    M include/qemu-common.h

  Log Message:
  -----------
  ui/gtk.c: Fix *BSD build of Gtk+ UI

Fix the build of the Gtk+ UI on *BSD systems.

Signed-off-by: Brad Smith <address@hidden>
Reviewed-by: Laszlo Ersek <address@hidden>
Message-id: address@hidden
Signed-off-by: Anthony Liguori <address@hidden>


  Commit: 6a85e60cb994bd95d1537aafbff65816f3de4637
      
https://github.com/qemu/qemu/commit/6a85e60cb994bd95d1537aafbff65816f3de4637
  Author: Lei Li <address@hidden>
  Date:   2013-05-22 (Wed, 22 May 2013)

  Changed paths:
    M qapi-schema.json
    M qemu-char.c
    M qemu-options.hx

  Log Message:
  -----------
  chardev: Make the name of memory device consistent

Now we have memory char device, but the backend name of it
is a little confusion. We actually register it by 'memory', but
the description in qemu-option, the name of open functions
and the new api backend called it 'ringbuf'. It should keep
consistent. This patch named it all to 'memory'.

Signed-off-by: Lei Li <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Message-id: address@hidden
Signed-off-by: Anthony Liguori <address@hidden>


  Commit: 2b220025993e76d4116781ca91a4fabc5ad9c722
      
https://github.com/qemu/qemu/commit/2b220025993e76d4116781ca91a4fabc5ad9c722
  Author: Lei Li <address@hidden>
  Date:   2013-05-22 (Wed, 22 May 2013)

  Changed paths:
    M qemu-char.c

  Log Message:
  -----------
  chardev: Get filename for new qapi backend

This patch sets the filename when the new qapi backend
init from opts.

The previous patch and discussions as link below:

http://patchwork.ozlabs.org/patch/243896/

If anyone who have better idea to fix this please let
me know your suggestions.

Signed-off-by: Lei Li <address@hidden>
Message-id: address@hidden
Signed-off-by: Anthony Liguori <address@hidden>


  Commit: 644c98587d4ccc09e7592e1688e4e7fa363c5a75
      
https://github.com/qemu/qemu/commit/644c98587d4ccc09e7592e1688e4e7fa363c5a75
  Author: Dmitry Fleytman <address@hidden>
  Date:   2013-05-22 (Wed, 22 May 2013)

  Changed paths:
    M hw/net/virtio-net.c
    M include/hw/i386/pc.h
    M include/hw/virtio/virtio-net.h

  Log Message:
  -----------
  virtio-net: dynamic network offloads configuration

Virtio-net driver currently negotiates network offloads
on startup via features mechanism and have no ability to
disable and re-enable offloads later.
This patch introduced a new control command that allows
to configure device network offloads state dynamically.
The patch also introduces a new feature flag
VIRTIO_NET_F_CTRL_GUEST_OFFLOADS.

Signed-off-by: Dmitry Fleytman <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Message-id: address@hidden
Signed-off-by: Anthony Liguori <address@hidden>


  Commit: 3459f01b2d9612070ec23221a4ccb60a41b775ae
      
https://github.com/qemu/qemu/commit/3459f01b2d9612070ec23221a4ccb60a41b775ae
  Author: Alex Williamson <address@hidden>
  Date:   2013-05-22 (Wed, 22 May 2013)

  Changed paths:
    M hw/i386/kvm/pci-assign.c

  Log Message:
  -----------
  pci-assign: Add MSI affinity support

To support guest MSI affinity changes update the MSI message any time
the guest writes to the address or data fields.

Signed-off-by: Alex Williamson <address@hidden>
Acked-by: Michael S. Tsirkin <address@hidden>
Message-id: address@hidden
Signed-off-by: Anthony Liguori <address@hidden>


Compare: https://github.com/qemu/qemu/compare/1239b472bb0d...3459f01b2d96