1. 08 4月, 2015 1 次提交
  2. 04 4月, 2015 1 次提交
  3. 02 4月, 2015 1 次提交
  4. 26 3月, 2015 1 次提交
  5. 20 3月, 2015 1 次提交
  6. 19 3月, 2015 2 次提交
  7. 18 3月, 2015 2 次提交
  8. 17 3月, 2015 1 次提交
  9. 16 3月, 2015 1 次提交
  10. 12 3月, 2015 12 次提交
  11. 11 3月, 2015 4 次提交
  12. 10 3月, 2015 8 次提交
  13. 09 3月, 2015 5 次提交
    • G
      sPAPR: Implement EEH RTAS calls · ee954280
      Gavin Shan 提交于
      The emulation for EEH RTAS requests from guest isn't covered
      by QEMU yet and the patch implements them.
      
      The patch defines constants used by EEH RTAS calls and adds
      callbacks sPAPRPHBClass::{eeh_set_option, eeh_get_state, eeh_reset,
      eeh_configure}, which are going to be used as follows:
      
        * RTAS calls are received in spapr_pci.c, sanity check is done
          there.
        * RTAS handlers handle what they can. If there is something it
          cannot handle and the corresponding sPAPRPHBClass callback is
          defined, it is called.
        * Those callbacks are only implemented for VFIO now. They do ioctl()
          to the IOMMU container fd to complete the calls. Error codes from
          that ioctl() are transferred back to the guest.
      
      [aik: defined RTAS tokens for EEH RTAS calls]
      Signed-off-by: NGavin Shan <gwshan@linux.vnet.ibm.com>
      Reviewed-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      ee954280
    • M
      spapr_vio: Convert to realize() · 28b07e73
      Markus Armbruster 提交于
      Bonus fix: always set an error on failure.  Some failures were silent
      before, except for the generic error set by device_realize().
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      28b07e73
    • D
      pseries: Switch VGA endian on H_SET_MODE · eefaccc0
      David Gibson 提交于
      When the guest switches the interrupt endian mode, which essentially
      means a global machine endian switch, we want to change the VGA
      framebuffer endian mode as well in order to be backward compatible
      with existing guests who don't know about the new endian control
      register.
      Signed-off-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Reviewed-by: NMichael Roth <mdroth@linux.vnet.ibm.com>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      eefaccc0
    • D
      pseries: Move rtc_offset into RTC device's state structure · 880ae7de
      David Gibson 提交于
      The initial creation of the PAPR RTC qdev class left a wart - the rtc's
      offset was left in the sPAPREnvironment structure, accessed via a global.
      
      This patch moves it into the RTC device's own state structure, were it
      belongs.  This requires a small change to the migration stream format.  In
      order to handle incoming streams from older versions, we also need to
      retain the rtc_offset field in the sPAPREnvironment structure, so that it
      can be loaded into via the vmsd, then pushed into the RTC device.
      
      Since we're changing the migration format, this also takes the opportunity
      to:
      
        * Change the rtc offset from a value in seconds to a value in
          nanoseconds, allowing nanosecond offsets between host and guest
          rtc time, if desired.
      
        * Remove both the already unused "next_irq" field and now unused
          "rtc_offset" field from the new version of the spapr migration
          stream
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      880ae7de
    • D
      pseries: Make the PAPR RTC a qdev device · 28df36a1
      David Gibson 提交于
      At present the PAPR RTC isn't a "device" as such - it's accessed only via
      firmware/hypervisor calls, and is handled in the sPAPR core code.  This
      becomes inconvenient as we extend it in various ways.
      
      This patch makes the PAPR RTC a separate device in the qemu device model.
      
      For now, the only piece of device state - the rtc_offset - is still kept in
      the global sPAPREnvironment structure.  That's clearly wrong, but leaving
      it to be fixed in a following patch makes for a clearer separation between
      the internal re-organization of the device, and the behavioural changes
      (because the migration stream format needs to change slightly when the
      offset is moved into the device's own state).
      Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      28df36a1