1. 20 1月, 2017 4 次提交
  2. 09 1月, 2017 11 次提交
  3. 27 12月, 2016 1 次提交
  4. 16 11月, 2016 1 次提交
  5. 28 10月, 2016 2 次提交
  6. 25 10月, 2016 1 次提交
  7. 24 10月, 2016 1 次提交
  8. 18 10月, 2016 1 次提交
  9. 10 10月, 2016 1 次提交
  10. 04 10月, 2016 2 次提交
  11. 14 7月, 2016 1 次提交
    • A
      hw/arm/virt: tcg: adjust MPIDR like KVM · 95eb49c8
      Andrew Jones 提交于
      KVM adjusts the MPIDR of guest vcpus based on the architecture of
      the host, 32-bit vs. 64-bit, and, for 64-bit, also on the type of
      GIC the guest is using. To be consistent and improve SGI efficiency
      we make the same adjustments for TCG as 64-bit KVM hosts. We neglect
      to add consistency with 32-bit KVM hosts, as that would reduce SGI
      efficiency and KVM is expected to change.
      
      As MPIDR is a system register, and thus guest visible, we only make
      adjustments for current and later versioned machines.
      Signed-off-by: NAndrew Jones <drjones@redhat.com>
      Message-id: 1467378129-23302-3-git-send-email-drjones@redhat.com
      Reviewed-by: NPeter Maydell <peter.maydell@linaro.org>
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      95eb49c8
  12. 08 7月, 2016 2 次提交
    • I
      arm: virt: Parse cpu_model only once · 09f71b05
      Igor Mammedov 提交于
      Considering that features are converted to global properties and
      global properties are automatically applied to every new instance
      of created CPU (at object_new() time), there is no point in
      parsing cpu_model string every time a CPU created. So move
      parsing outside CPU creation loop and do it only once.
      
      Parsing also should be done before any CPU is created so that
      features would affect the first CPU a well.
      Signed-off-by: NIgor Mammedov <imammedo@redhat.com>
      Reviewed-by: NPeter Maydell <peter.maydell@linaro.org>
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      09f71b05
    • I
      cpu: Use CPUClass->parse_features() as convertor to global properties · 62a48a2a
      Igor Mammedov 提交于
      Currently CPUClass->parse_features() is used to parse -cpu
      features string and set properties on created CPU instances.
      
      But considering that features specified by -cpu apply to every
      created CPU instance, it doesn't make sense to parse the same
      features string for every CPU created. It also makes every target
      that cares about parsing features string explicitly call
      CPUClass->parse_features() parser, which gets in a way if we
      consider using generic device_add for CPU hotplug as device_add
      has not a clue about CPU specific hooks.
      
      Turns out we can use global properties mechanism to set
      properties on every created CPU instance for a given type. That
      way it's possible to convert CPU features into a set of global
      properties for CPU type specified by -cpu cpu_model and common
      Device.device_post_init() will apply them to CPU of given type
      automatically regardless whether it's manually created CPU or CPU
      created with help of device_add.
      Signed-off-by: NIgor Mammedov <imammedo@redhat.com>
      Reviewed-by: NEduardo Habkost <ehabkost@redhat.com>
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      62a48a2a
  13. 04 7月, 2016 1 次提交
  14. 14 6月, 2016 5 次提交
  15. 09 6月, 2016 1 次提交
  16. 06 6月, 2016 2 次提交
  17. 21 5月, 2016 1 次提交
  18. 12 5月, 2016 1 次提交
  19. 31 3月, 2016 1 次提交