1. 20 Jun, 2013 6 commits
  2. 29 May, 2013 9 commits
  3. 24 May, 2013 6 commits
  4. 22 Mar, 2013 1 commit
    • Hu Tao's avatar
      memory: fix a bug of detection of memory region collision · 2c7cfd65
      Hu Tao authored
      The collision reports before and after this patch are:
      
      before:
      
      warning: subregion collision cfc/4 (pci-conf-data) vs cf8/4 (pci-conf-idx)
      warning: subregion collision 8000000/f8000000 (pci-hole) vs 0/8000000 (ram-below-4g)
      warning: subregion collision 100000000/4000000000000000 (pci-hole64) vs 8000000/f8000000 (pci-hole)
      warning: subregion collision 4d1/1 (kvm-elcr) vs 4d0/1 (kvm-elcr)
      warning: subregion collision fec00000/1000 (kvm-ioapic) vs 8000000/f8000000 (pci-hole)
      warning: subregion collision 80/1 (ioport80) vs 7e/2 (kvmvapic)
      warning: subregion collision fed00000/400 (hpet) vs 8000000/f8000000 (pci-hole)
      warning: subregion collision 81/3 (dma-page) vs 80/1 (ioport80)
      warning: subregion collision 8/8 (dma-cont) vs 0/8 (dma-chan)
      warning: subregion collision d0/10 (dma-cont) vs c0/10 (dma-chan)
      warning: subregion collision 0/80 (ich9-pm) vs 8/8 (dma-cont)
      warning: subregion collision 0/80 (ich9-pm) vs 0/8 (dma-chan)
      warning: subregion collision 0/80 (ich9-pm) vs 64/1 (i8042-cmd)
      warning: subregion collision 0/80 (ich9-pm) vs 60/1 (i8042-data)
      warning: subregion collision 0/80 (ich9-pm) vs 61/1 (elcr)
      warning: subregion collision 0/80 (ich9-pm) vs 40/4 (kvm-pit)
      warning: subregion collision 0/80 (ich9-pm) vs 70/2 (rtc)
      warning: subregion collision 0/80 (ich9-pm) vs 20/2 (kvm-pic)
      warning: subregion collision 0/80 (ich9-pm) vs 7e/2 (kvmvapic)
      warning: subregion collision 4/2 (acpi-cnt) vs 0/4 (acpi-evt)
      warning: subregion collision 30/8 (apci-smi) vs 20/10 (apci-gpe0)
      warning: subregion collision b0000000/10000000 (pcie-mmcfg) vs 8000000/f8000000 (pci-hole)
      
      after:
      
      warning: subregion collision fec00000/1000 (kvm-ioapic) vs 8000000/f8000000 (pci-hole)
      warning: subregion collision fed00000/400 (hpet) vs 8000000/f8000000 (pci-hole)
      warning: subregion collision 0/80 (ich9-pm) vs 8/8 (dma-cont)
      warning: subregion collision 0/80 (ich9-pm) vs 0/8 (dma-chan)
      warning: subregion collision 0/80 (ich9-pm) vs 64/1 (i8042-cmd)
      warning: subregion collision 0/80 (ich9-pm) vs 60/1 (i8042-data)
      warning: subregion collision 0/80 (ich9-pm) vs 61/1 (elcr)
      warning: subregion collision 0/80 (ich9-pm) vs 40/4 (kvm-pit)
      warning: subregion collision 0/80 (ich9-pm) vs 70/2 (rtc)
      warning: subregion collision 0/80 (ich9-pm) vs 20/2 (kvm-pic)
      warning: subregion collision 0/80 (ich9-pm) vs 7e/2 (kvmvapic)
      warning: subregion collision b0000000/10000000 (pcie-mmcfg) vs 8000000/f8000000 (pci-hole)
      Signed-off-by: default avatarHu Tao <hutao@cn.fujitsu.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      2c7cfd65
  5. 16 Feb, 2013 1 commit
  6. 02 Feb, 2013 1 commit
  7. 20 Dec, 2012 1 commit
  8. 19 Dec, 2012 3 commits
  9. 10 Nov, 2012 2 commits
  10. 29 Oct, 2012 1 commit
    • Avi Kivity's avatar
      memory: fix rendering of a region obscured by another · d26a8cae
      Avi Kivity authored
      The memory core drops regions that are hidden by another region (for example,
      during BAR sizing), but it doesn't do so correctly if the lower address of the
      existing range is below the lower address of the new range.
      
      Example (qemu-system-mips -M malta -kernel vmlinux-2.6.32-5-4kc-malta
               -append "console=ttyS0"  -nographic -vga cirrus):
      
      Existing range: 10000000-107fffff
      New range:      100a0000-100bffff
      
      Correct behaviour: drop new range
      Incorrect behaviour: add new range
      
      Fix by taking this case into account (previously we only considered
      equal lower boundaries).
      Tested-by: default avatarAurelien Jarno <aurelien@aurel32.net>
      Signed-off-by: default avatarAvi Kivity <avi@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      d26a8cae
  11. 23 Oct, 2012 1 commit
    • Avi Kivity's avatar
      Rename target_phys_addr_t to hwaddr · a8170e5e
      Avi Kivity authored
      target_phys_addr_t is unwieldly, violates the C standard (_t suffixes are
      reserved) and its purpose doesn't match the name (most target_phys_addr_t
      addresses are not target specific).  Replace it with a finger-friendly,
      standards conformant hwaddr.
      
      Outstanding patchsets can be fixed up with the command
      
        git rebase -i --exec 'find -name "*.[ch]"
                              | xargs s/target_phys_addr_t/hwaddr/g' origin
      Signed-off-by: default avatarAvi Kivity <avi@redhat.com>
      Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
      a8170e5e
  12. 22 Oct, 2012 5 commits
  13. 17 Oct, 2012 2 commits
    • Avi Kivity's avatar
      memory: abort if a memory region is destroyed during a transaction · 2be0e25f
      Avi Kivity authored
      Destroying a memory region is illegal within a transaction, as until
      the transaction is committed, the memory core may hold references to
      the region.  Add an assert to check for violations of this rule.
      Signed-off-by: default avatarAvi Kivity <avi@redhat.com>
      2be0e25f
    • Alexander Graf's avatar
      memory: Make eventfd adhere to device endianness · 28f362be
      Alexander Graf authored
      Our memory API MMIO regions know the concept of device endianness. This
      is used to automatically swap endianness between devices and host CPU,
      depending on whether buses in between would swizzle the bits.
      
      The ioeventfd value comparison does not adhere to that semantic though.
      Probably because nobody has been running ioeventfd on a BE platform and
      the only device implementing ioeventfd right now is LE (PCI) based.
      
      So add swizzling to ioeventfd registration / deletion to make the rest
      of the code as consistent as possible.
      
      Thanks a lot to Michael Tsirkin to point me towards the right direction.
      Signed-off-by: default avatarAlexander Graf <agraf@suse.de>
      Signed-off-by: default avatarAvi Kivity <avi@redhat.com>
      28f362be
  14. 15 Oct, 2012 1 commit