1. 05 3月, 2014 5 次提交
  2. 03 3月, 2014 1 次提交
  3. 02 3月, 2014 3 次提交
  4. 01 3月, 2014 8 次提交
  5. 27 2月, 2014 8 次提交
    • M
      sun4m: Add Sun CG3 framebuffer initialisation function · af87bf29
      Mark Cave-Ayland 提交于
      In order to allow the user to choose the framebuffer for sparc-softmmu, add
      -vga tcx and -vga cg3 options to the QEMU command line. If no option is
      specified, the default TCX framebuffer is used.
      
      Since proprietary FCode ROMs use a resolution of 1152x900, slightly relax the
      validation rules to allow both displays to be initiated at the higher
      resolution used by these ROMs upon request (OpenBIOS FCode ROMs default to
      the normal QEMU sun4m default resolution of 1024x768).
      
      Finally move any fprintf(stderr ...) statements in the areas affected by this
      patch over to the new error_report() function.
      Signed-off-by: NMark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
      CC: Blue Swirl <blauwirbel@gmail.com>
      CC: Anthony Liguori <aliguori@amazon.com>
      CC: Peter Maydell <peter.maydell@linaro.org>
      CC: Bob Breuer <breuerr@mc.net>
      CC: Artyom Tarasenko <atar4qemu@gmail.com>
      af87bf29
    • M
      sun4m: Set HostID in NVRAM · f9681f11
      Mark Cave-Ayland 提交于
      On SparcStations, the HostID field in the NVRAM is equal to the last
      three bytes of the MAC address (which is also stored in the NVRAM).
      
      This constant is used as an identification/serial number on Solaris.
      Signed-off-by: NOlivier Danet <odanet@caramail.com>
      Signed-off-by: NMark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
      f9681f11
    • H
      s390x/event-facility: code restructure · 477a72a1
      Heinz Graalfs 提交于
      Code restructure in order to simplify class hierarchy
        - remove S390SCLPDevice abstract base class
          and move function pointers into new SCLPEventFacilityClass
        - implement SCLPEventFacility as SysBusDevice
        - use define constants for instance creation strings
      
      The following ascii-art shows the class structure wrt the SCLP EventFacility
      before (CURRENT) and after the restructure (NEW):
      
      ----
      CURRENT:
      
         "s390-sclp-events-bus"
         +-------------------------+
         |      SCLPEventsBus      |
         |-------------------------|
         |BusState qbus            |
         +-------------------------+
      
         +-------------------------+
         |   SCLPEventFacility     |  - to be replaced by new SCLPEventFacility,
         |-------------------------|    which will be a SysBusDevice
         |SCLPEventsBus sbus       |
         |DeviceState *qdev        |
         |unsigned int receive_mask|
         +-------------------------+
      
         +-------------------------+
         |   S390SCLPDeviceClass   |  - to be replaced by new SCLPEventFacilityClass
         |-------------------------|
         |DeviceClass qdev         |
         |*(init)()                |
         +-------------------------+
      
         "s390-sclp-event-facility"
                   |
               instance-of
                   |
                   V
         "s390-sclp-device"           - this is an abstract class
         +-------------------------+
         |     S390SCLPDevice   (A)|  - to be replaced by new SCLPEventFacility
         |-------------------------|
         |SysBusDevice busdev      |
         |SCLPEventFacility *ef    |
         |                         |
         |*(sclp_command_handler)()|  - these 2 go to new SCLPEventFacilityClass
         |*(event_pending)()       |
         +-------------------------+
      
      ----
      NEW:
      
         "s390-sclp-events-bus"
         +-------------------------+
         |      SCLPEventsBus      |
         |-------------------------|
         |BusState qbus            |
         +-------------------------+
      
         +-------------------------+
         | SCLPEventFacilityClass  |
         |-------------------------|
         |DeviceClass parent_class |
         |                         |
         |*(init)()                |
         |*(command_handler)()     |
         |*(event_pending)()       |
         +-------------------------+
      
         "s390-sclp-event-facility"
         +-------------------------+
         |   SCLPEventFacility     |
         |-------------------------|
         |SysBusDevice parent_class|
         |SCLPEventsBus sbus       |
         |unsigned int receive_mask|
         +-------------------------+
      Signed-off-by: NHeinz Graalfs <graalfs@linux.vnet.ibm.com>
      Reviewed-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      477a72a1
    • J
      s390x/kvm: implement floating-interrupt controller device · 3a553fc6
      Jens Freimann 提交于
      This patch implements a floating-interrupt controller device (flic)
      which interacts with the s390 flic kvm_device.
      Signed-off-by: NJens Freimann <jfrei@linux.vnet.ibm.com>
      Reviewed-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      3a553fc6
    • W
      include/qemu/crc32c.h: Rename include guards to match filename · 0956ff5a
      Will Newton 提交于
      Signed-off-by: NWill Newton <will.newton@linaro.org>
      Reviewed-by: NPeter Maydell <peter.maydell@linaro.org>
      Message-id: 1393411566-24104-2-git-send-email-will.newton@linaro.org
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      0956ff5a
    • C
      arm: vgic device control api support · 1da41cc1
      Christoffer Dall 提交于
      Support creating the ARM vgic device through the device control API and
      setting the base address for the distributor and cpu interfaces in KVM
      VMs using this API.
      
      Because the older KVM_CREATE_IRQCHIP interface needs the irq chip to be
      created prior to creating the VCPUs, we first test if we can use the
      device control API in kvm_arch_irqchip_create (using the test flag from
      the device control API).  If we cannot, it means we have to fall back to
      KVM_CREATE_IRQCHIP and use the older ioctl at this point in time.  If
      however, we can use the device control API, we don't do anything and
      wait until the arm_gic_kvm driver initializes and let that use the
      device control API.
      Signed-off-by: NChristoffer Dall <christoffer.dall@linaro.org>
      Message-id: 1392687720-26806-5-git-send-email-christoffer.dall@linaro.org
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      1da41cc1
    • C
      kvm: Common device control API functions · 0a6a7cca
      Christoffer Dall 提交于
      Introduces two simple functions:
          int kvm_device_ioctl(int fd, int type, ...);
          int kvm_create_device(KVMState *s, uint64_t type, bool test);
      
      These functions wrap the basic ioctl-based interactions with KVM in a
      way similar to other KVM ioctl wrappers.
      Reviewed-by: NPeter Maydell <peter.maydell@linaro.org>
      Signed-off-by: NChristoffer Dall <christoffer.dall@linaro.org>
      Message-id: 1392687720-26806-4-git-send-email-christoffer.dall@linaro.org
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      0a6a7cca
    • C
      kvm: Introduce kvm_arch_irqchip_create · d6032e06
      Christoffer Dall 提交于
      Introduce kvm_arch_irqchip_create an arch-specific hook in preparation
      for architecture-specific use of the device control API to create IRQ
      chips.
      
      Following patches will implement the ARM irqchip create method to prefer
      the device control API over the older KVM_CREATE_IRQCHIP API.
      Reviewed-by: NPeter Maydell <peter.maydell@linaro.org>
      Signed-off-by: NChristoffer Dall <christoffer.dall@linaro.org>
      Message-id: 1392687720-26806-3-git-send-email-christoffer.dall@linaro.org
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      d6032e06
  6. 26 2月, 2014 5 次提交
  7. 25 2月, 2014 5 次提交
  8. 22 2月, 2014 5 次提交