1. 19 3月, 2012 2 次提交
  2. 18 3月, 2012 9 次提交
  3. 17 3月, 2012 11 次提交
    • S
      w64: Fix data type of next_tb and tcg_qemu_tb_exec · 69784eae
      Stefan Weil 提交于
      next_tb is the numeric value of a tcg target (= QEMU host) address.
      
      Using tcg_target_ulong instead of unsigned long shows this and makes
      the code portable for hosts with an unusual size of long (w64).
      
      The type cast '(long)(next_tb & ~3)' was not needed (casting
      unsigned long to long does not change the bits, and nor does
      casting long to pointer for most (= all non w64) hosts.
      It is removed here.
      
      Macro or function tcg_qemu_tb_exec is used to set next_tb.
      The function also returns next_tb. Therefore tcg_qemu_tb_exec
      must return a tcg_target_ulong.
      Signed-off-by: NStefan Weil <sw@weilnetz.de>
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      69784eae
    • A
      softfloat: fix for C99 · 3bf7e40a
      Avi Kivity 提交于
      C99 appears to consider compound literals as non-constants, and complains
      when they are used in static initializers.  Switch to ordinary initializer
      syntax.
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      Acked-by: NAndreas Färber <afaerber@suse.de>
      Reported-by: NAndreas Färber <andreas.faerber@web.de>
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      3bf7e40a
    • B
      Merge branch 'target-arm.for-upstream' of git://git.linaro.org/people/pmaydell/qemu-arm · 6344d922
      Blue Swirl 提交于
      * 'target-arm.for-upstream' of git://git.linaro.org/people/pmaydell/qemu-arm:
        target-arm: Decode SETEND correctly in Thumb
        target-arm: Clear IT bits when taking exceptions in v7M
        target-arm: Fix typo in ARM946 cp15 c5 handling
      6344d922
    • B
      Merge branch 'malta' of git://qemu.weilnetz.de/qemu · 6b41fecf
      Blue Swirl 提交于
      * 'malta' of git://qemu.weilnetz.de/qemu:
        malta: Fix display for LED array
        malta: Use symbolic hardware addresses
        malta: Always allocate flash memory
        malta: Clean allocation of bios region alias
      6b41fecf
    • B
      Merge branch 'ppc-for-upstream' of git://repo.or.cz/qemu/agraf · cb76e9c7
      Blue Swirl 提交于
      * 'ppc-for-upstream' of git://repo.or.cz/qemu/agraf:
        PPC: Fix openpic with relative memregions
        pseries: Configure PCI bridge using properties
        PPC: KVM: Synchronize regs on CPU dump
        kvm: Comparison with ioctl number macros needs to be unsigned
        ppc: Correctly define POWERPC_INSNS2_DEFAULT
        pseries: Add support for level interrupts to XICS
        PPC: Fix large page support in TCG
        PPC: Add PIR register to POWER7 CPU
        pseries: Remove PCI device from PCI host bridge code
        pseries: Remove unused constant from PCI code
        pseries: Update SLOF firmware image
        PPC64: Add support for ldbrx and stdbrx instructions
        pseries: Don't try to munmap() a malloc()ed TCE table
        ppc: Add missing 'static' to spin_rw_ops
        PPC: 405: Fix ppc405ep initialization
        Bad zero comparison for sas_ss_flags on powerpc
      cb76e9c7
    • A
      vmstate: fix varrays with uint32_t indexes · 1329d189
      Amos Kong 提交于
      VMSTATE_VARRAY_UINT32() is used in hw/ds1225y.c, and we checked
      VMS_VARRAY_UINT32 bit of field->flags in vmstate_load_state(),
      but we don't check this bit in vmstate_save_state().
      Signed-off-by: NAmos Kong <akong@redhat.com>
      Acked-by: NJuan Quintela <quintela@redhat.com>
      Acked-by: NHervé Poussineau <hpoussin@reactos.org>
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      1329d189
    • K
      Fix large memory chunks allocation with tcg_malloc. · 4055299e
      Kirill Batuzov 提交于
      An attempt to allocate a large memory chunk after a small one resulted in
      circular links in list of pools.  It caused the same memory being
      allocated twice for different arrays.
      
      Now pools for large memory chunks are kept in separate list and are
      freed during pool reset because current allocator can not reuse them.
      Signed-off-by: NKirill Batuzov <batuzovk@ispras.ru>
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      4055299e
    • P
      hw/pxa2xx.c: Fix handling of pxa2xx_i2c variable offset within region · 14dd5faa
      Peter Maydell 提交于
      The pxa2xx I2C controller can have its registers at an arbitrary offset
      within the MemoryRegion it creates. We use this to create two controllers,
      one which covers a region of size 0x10000 with registers starting at an
      offset 0x1600 into that region, and a second one which covers a region
      of size just 0x100 with the registers starting at the base of the region.
      
      The implementation of this offsetting uses two qdev properties, "offset"
      (which sets the offset which must be subtracted from the address to
      get the offset into the actual register bank) and "size", which is the
      size of the MemoryRegion. We were actually using "offset" for two
      purposes: firstly the required one of handling the registers not being
      at the base of the MemoryRegion, and secondly as a workaround for a
      deficiency of QEMU. Until commit 5312bd8b, if a MemoryRegion was mapped
      at a non-page boundary, the address passed into the read and write
      functions would be the offset from the start of the page, not the
      offset from the start of the MemoryRegion. So when calculating the value
      to set the "offset" qdev property we included a rounding to a page
      boundary.
      
      Following commit 5312bd8b MemoryRegion read/write functions are now
      correctly passed the offset from the base of the region, and our
      workaround now means we're subtracting too much from addresses, resulting
      in warnings like "pxa2xx_i2c_read: Bad register 0xffffff90".
      The fix for this is simply to remove the rounding to a page boundary;
      this allows us to slightly simplify the expression since
        base - (base & (~region_size)) == base & region_size
      
      The qdev property "offset" itself must remain because it is still
      performing its primary job of handling register banks not being at
      the base of the MemoryRegion.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Reviewed-by: NAndreas Färber <afaerber@suse.de>
      14dd5faa
    • M
      hw/pxa2xx_lcd.c: drop target_phys_addr_t usage in device state · 27424dcc
      Mitsyanko Igor 提交于
      Pxa2xx LCD controller is intended to work with 32-bit bus and it has no knowledge
      of system's physical address size, so it should not use target_phys_addr_t in it's
      state. Convert three variables in DMAChannel state from target_phys_addr_t to uint32_t,
      use VMSTATE_UINT32 instead of VMSTATE_UINTTL for these variables.
      We can do this safely because:
      1) pxa2xx has 32-bit physical address;
      2) rest of the code in file never assumes converted variables to have any size
      different from uint32_t;
      3) we shouldn't have used VMSTATE_UINTTL in the first place because this macro
      is for target_ulong type (which can be different from target_phys_addr_t).
      Signed-off-by: NIgor Mitsyanko <i.mitsyanko@samsung.com>
      Reviewed-by: NAndreas Färber <afaerber@suse.de>
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      27424dcc
    • M
      hw/pxa2xx_dma.c: drop target_phys_addr_t usage in device state · a10394e1
      Mitsyanko Igor 提交于
      Pxa2xx DMA controller is a 32-bit device and it has no knowledge of system's
      physical address size, so it should not use target_phys_addr_t in it's state.
      Convert variables descr, src and dest from type target_phys_addr_t to uint32_t,
      use VMSTATE_UINT32 instead of VMSTATE_UINTTL for these variables.
      
      We can do this safely because:
      1) pxa2xx actually has 32-bit physical address size;
      2) rest of the code in file never assumes descr, src and dest variables to have
      size different from uint32_t;
      3) we shouldn't have used VMSTATE_UINTTL in the first place because this macro
      is for target_ulong type (which can be different from target_phys_addr_t).
      Signed-off-by: NIgor Mitsyanko <i.mitsyanko@samsung.com>
      Reviewed-by: NAndreas Färber <afaerber@suse.de>
      Reviewed-by: NMichael Roth <mdroth@linux.vnet.ibm.com>
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      a10394e1
    • P
      ARM: Remove unnecessary subpage workarounds · 0e4a398a
      Peter Maydell 提交于
      In the ARM per-CPU peripherals (GIC, private timers, SCU, etc),
      remove workarounds for subpage memory region read/write functions
      being passed offsets from the start of the page rather than the
      start of the region. Following commit 5312bd8b the masking off
      of high bits of the address offset is now harmless but unnecessary.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Reviewed-by: NAndreas Färber <afaerber@suse.de>
      0e4a398a
  4. 16 3月, 2012 8 次提交
  5. 15 3月, 2012 10 次提交
    • A
      PPC: Fix openpic with relative memregions · 38ae51a8
      Alexander Graf 提交于
      After commit 5312bd8b we got memory region relative offsets into our mmio
      callbacks instead of page boundary based offsets.
      
      This broke the OpenPIC emulation which expected offsets to be on page boundary
      and substracted its region offset manually.
      
      This patch gets rid of that manual substraction and lets the memory api do its
      magic instead.
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      38ae51a8
    • D
      pseries: Configure PCI bridge using properties · 298a9710
      David Gibson 提交于
      Currently, the function spapr_create_phb() uses its parameters to
      initialize the correct memory windows for the new PCI Host Bridge
      (PHB).  This is not the way things are supposed to be done with qdevs,
      and means you can't create extra PHBs easily using -device.
      
      Since pSeries machines can and do have many PHBs with various
      configurations, this is a real limitation, not just a theoretical.
      This patch, therefore, alters the PHB initialization code to use qdev
      properties to set these parameters of the new bridge, moving most of
      the code from spapr_create_phb() to spapr_phb_init().
      
      While we're at it, we change the naming of each PCI bus and its
      associated memory regions to be less arbitrary and make it easier to
      relate the guest and qemu views of memory to each other.
      Signed-off-by: NAlexey Kardashevskiy <aik@ozlabs.ru>
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Reviewed-by: NAndreas Färber <afaerber@suse.de>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      298a9710
    • A
      PPC: KVM: Synchronize regs on CPU dump · 29979a8d
      Alexander Graf 提交于
      When we dump the CPU registers, there's a certain chance they haven't been
      synchronized with KVM yet, so we have to manually trigger that.
      
      This aligns the code with x86 and fixes a bug where the register state was
      bogus on invalid/unknown kvm exit reasons.
      Reported-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      29979a8d
    • D
      kvm: Comparison with ioctl number macros needs to be unsigned · 92e4b519
      David Gibson 提交于
      In kvm-all.c we store an ioctl cmd number in the irqchip_inject_ioctl field
      of KVMState, which has type 'int'.  This seems to make sense since the
      ioctl() man page says that the cmd parameter has type int.
      
      However, the kernel treats ioctl numbers as unsigned - sys_ioctl() takes an
      unsigned int, and the macros which generate ioctl numbers expand to
      unsigned expressions.  Furthermore, some ioctls (IOC_READ ioctls on x86
      and IOC_WRITE ioctls on powerpc) have bit 31 set, and so would be negative
      if interpreted as an int. This has the surprising and compile-breaking
      consequence that in kvm_irqchip_set_irq() where we do:
          return (s->irqchip_inject_ioctl == KVM_IRQ_LINE) ? 1 : event.status;
      We will get a "comparison is always false due to limited range of data
      type" warning from gcc if KVM_IRQ_LINE is one of the bit-31-set ioctls,
      which it is on powerpc.
      
      So, despite the fact that the man page and posix say ioctl numbers are
      signed, they're actually unsigned.  The kernel uses unsigned, the glibc
      header uses unsigned long, and FreeBSD, NetBSD and OSX also use unsigned
      long ioctl numbers in the code.
      
      Therefore, this patch changes the variable to be unsigned, fixing the
      compile.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      92e4b519
    • M
      ppc: Correctly define POWERPC_INSNS2_DEFAULT · 6bbc5ed1
      Meador Inge 提交于
      'POWERPC_INSNS2_DEFAULT' was defined incorrectly which was causing the
      opcode table creation code to erroneously register 'eieio' and 'mbar'
      for the "default" processor:
      
         ** ERROR: opcode 1a already assigned in opcode table 16
         *** ERROR: unable to insert opcode [1f-16-1a]
         *** ERROR initializing PowerPC instruction 0x1f 0x16 0x1a
      Signed-off-by: NMeador Inge <meadori@codesourcery.com>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      6bbc5ed1
    • D
      pseries: Add support for level interrupts to XICS · d07fee7e
      David Gibson 提交于
      The pseries "xics" interrupt controller, like most interrupt
      controllers can support both message (i.e. edge sensitive) interrupts
      and level sensitive interrupts, but it needs to know which are which.
      
      When I implemented the xics emulation for qemu, the only devices we
      supported were the PAPR virtual IO devices.  These devices only use
      message interrupts, so they were the only ones I implemented in xics.
      
      Since then, however, we have added support for PCI devices, which use
      level sensitive interrupts.  It turns out the message interrupt logic
      still actually works most of the time for these, but there are
      circumstances where we can lost interrupts due to the incorrect
      interrupt logic.
      
      This patch, therefore, implements the correct xics level-sensitive
      interrupt logic.  The type of the interrupt is set when a device
      allocates a new xics interrupt.
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      d07fee7e
    • N
      PPC: Fix large page support in TCG · eb6ea4b2
      Nathan Whitehorn 提交于
      Fix large page support in TCG. The old code would overwrite the large page
      table entry with the fake 4 KB one generated here whenever the ref/change bits
      were updated, causing it to point to the wrong area of memory.
      Signed-off-by: NNathan Whitehorn <nwhitehorn@freebsd.org>
      Acked-by: NDavid Gibson <david@gibson.drobpear.id.au>
      [agraf: fix whitespace, braces]
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      eb6ea4b2
    • N
      PPC: Add PIR register to POWER7 CPU · 2e06214f
      Nathan Whitehorn 提交于
      The POWER7 emulation is missing the Processor Identification Register,
      mandatory in recent POWER CPUs, that is required for SMP on at least
      some operating systems (e.g. FreeBSD) to function properly. This patch
      copies the existing PIR code from the other CPUs that implement it.
      Signed-off-by: NNathan Whitehorn <nwhitehorn@freebsd.org>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      2e06214f
    • A
      pseries: Remove PCI device from PCI host bridge code · 76ab9583
      Alexey Kardashevskiy 提交于
      The sPAPR PCI code defines a PCI device "spapr-pci-host-bridge-pci" which
      is never used.  This came over from the earlier bridge driver we used as
      a template.  Some other bridges appear on their own PCI bus as a device,
      but that is not true of pSeries bridges, which are pure host to PCI with
      no visible presence on the PCI side.
      Signed-off-by: NAlexey Kardashevskiy <aik@ozlabs.ru>
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      76ab9583
    • D
      pseries: Remove unused constant from PCI code · 323abebf
      David Gibson 提交于
      The 'bars' constant array was used in experimental device allocation code
      which is no longer necessary now that we always run the SLOF firmware.
      This patch removes the now redundant variable.
      Signed-off-by: NAlexey Kardashevskiy <aik@ozlabs.ru>
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      323abebf