[Qemu-commits] [qemu/qemu] 39c93c: s390/ipl: Fix spurious errors in virtio

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: 39c93c67c5995bd8db7a3fa3b95dcd4e6bc881a7
      
https://github.com/qemu/qemu/commit/39c93c67c5995bd8db7a3fa3b95dcd4e6bc881a7
  Author: Christian Borntraeger <address@hidden>
  Date:   2013-05-31 (Fri, 31 May 2013)

  Changed paths:
    M pc-bios/s390-ccw/virtio.c

  Log Message:
  -----------
  s390/ipl: Fix spurious errors in virtio

With the ccw ipl code sometimes an error message like
"virtio: trying to map MMIO memory" or
"Guest moved used index from %u to %u" appeared. Turns out
that the ccw bios did not zero out the vring, which might
cause stale values in avail->idx and friends, especially
on reboot.

Lets zero out the relevant fields. To activate the patch we
need to rebuild s390-ccw.img as well.

Signed-off-by: Christian Borntraeger <address@hidden>
Message-id: address@hidden
Signed-off-by: Anthony Liguori <address@hidden>


  Commit: dec3fc9657e0682637de4d5a29d947284d01985c
      
https://github.com/qemu/qemu/commit/dec3fc9657e0682637de4d5a29d947284d01985c
  Author: Richard Henderson <address@hidden>
  Date:   2013-05-31 (Fri, 31 May 2013)

  Changed paths:
    M target-i386/translate.c

  Log Message:
  -----------
  target-i386: Fix aflag logic for CODE64 and the 0x67 prefix

The code reorganization in commit 4a6fd938 broke handling of PREFIX_ADR.
While fixing this, tidy and comment the code so that it's more obvious
what's going on in setting both aflag and dflag.

The TARGET_X86_64 ifdef can be eliminated because CODE64 expands to the
constant zero when TARGET_X86_64 is undefined.

Cc: Paolo Bonzini <address@hidden>
Reported-by: Laszlo Ersek <address@hidden>
Signed-off-by: Richard Henderson <address@hidden>
Reviewed-by: Paolo Bonzini <address@hidden>
Message-id: address@hidden
Signed-off-by: Anthony Liguori <address@hidden>


Compare: https://github.com/qemu/qemu/compare/0a1f348c429a...dec3fc9657e0