1. 05 2月, 2018 1 次提交
  2. 27 10月, 2017 3 次提交
  3. 25 10月, 2017 1 次提交
  4. 10 10月, 2017 1 次提交
  5. 01 9月, 2017 1 次提交
  6. 19 7月, 2017 1 次提交
  7. 13 5月, 2017 1 次提交
  8. 13 1月, 2017 1 次提交
    • A
      qom/cpu: move tlb_flush to cpu_common_reset · 1f5c00cf
      Alex Bennée 提交于
      It is a common thing amongst the various cpu reset functions want to
      flush the SoftMMU's TLB entries. This is done either by calling
      tlb_flush directly or by way of a general memset of the CPU
      structure (sometimes both).
      
      This moves the tlb_flush call to the common reset function and
      additionally ensures it is only done for the CONFIG_SOFTMMU case and
      when tcg is enabled.
      
      In some target cases we add an empty end_of_reset_fields structure to the
      target vCPU structure so have a clear end point for any memset which
      is resetting value in the structure before CPU_COMMON (where the TLB
      structures are).
      
      While this is a nice clean-up in general it is also a precursor for
      changes coming to cputlb for MTTCG where the clearing of entries
      can't be done arbitrarily across vCPUs. Currently the cpu_reset
      function is usually called from the context of another vCPU as the
      architectural power up sequence is run. By using the cputlb API
      functions we can ensure the right behaviour in the future.
      Signed-off-by: NAlex Bennée <alex.bennee@linaro.org>
      Reviewed-by: NRichard Henderson <rth@twiddle.net>
      Reviewed-by: NDavid Gibson <david@gibson.dropbear.id.au>
      1f5c00cf
  9. 21 12月, 2016 1 次提交
    • T
      Move target-* CPU file into a target/ folder · fcf5ef2a
      Thomas Huth 提交于
      We've currently got 18 architectures in QEMU, and thus 18 target-xxx
      folders in the root folder of the QEMU source tree. More architectures
      (e.g. RISC-V, AVR) are likely to be included soon, too, so the main
      folder of the QEMU sources slowly gets quite overcrowded with the
      target-xxx folders.
      To disburden the main folder a little bit, let's move the target-xxx
      folders into a dedicated target/ folder, so that target-xxx/ simply
      becomes target/xxx/ instead.
      
      Acked-by: Laurent Vivier <laurent@vivier.eu> [m68k part]
      Acked-by: Bastian Koppelmann <kbastian@mail.uni-paderborn.de> [tricore part]
      Acked-by: Michael Walle <michael@walle.cc> [lm32 part]
      Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com> [s390x part]
      Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com> [s390x part]
      Acked-by: Eduardo Habkost <ehabkost@redhat.com> [i386 part]
      Acked-by: Artyom Tarasenko <atar4qemu@gmail.com> [sparc part]
      Acked-by: Richard Henderson <rth@twiddle.net> [alpha part]
      Acked-by: Max Filippov <jcmvbkbc@gmail.com> [xtensa part]
      Reviewed-by: David Gibson <david@gibson.dropbear.id.au> [ppc part]
      Acked-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com> [cris&microblaze part]
      Acked-by: Guan Xuetao <gxt@mprc.pku.edu.cn> [unicore32 part]
      Signed-off-by: NThomas Huth <thuth@redhat.com>
      fcf5ef2a
  10. 25 10月, 2016 1 次提交
  11. 24 6月, 2016 1 次提交
    • A
      softfloat: Implement run-time-configurable meaning of signaling NaN bit · af39bc8c
      Aleksandar Markovic 提交于
      This patch modifies SoftFloat library so that it can be configured in
      run-time in relation to the meaning of signaling NaN bit, while, at the
      same time, strictly preserving its behavior on all existing platforms.
      
      Background:
      
      In floating-point calculations, there is a need for denoting undefined or
      unrepresentable values. This is achieved by defining certain floating-point
      numerical values to be NaNs (which stands for "not a number"). For additional
      reasons, virtually all modern floating-point unit implementations use two
      kinds of NaNs: quiet and signaling. The binary representations of these two
      kinds of NaNs, as a rule, differ only in one bit (that bit is, traditionally,
      the first bit of mantissa).
      
      Up to 2008, standards for floating-point did not specify all details about
      binary representation of NaNs. More specifically, the meaning of the bit
      that is used for distinguishing between signaling and quiet NaNs was not
      strictly prescribed. (IEEE 754-2008 was the first floating-point standard
      that defined that meaning clearly, see [1], p. 35) As a result, different
      platforms took different approaches, and that presented considerable
      challenge for multi-platform emulators like QEMU.
      
      Mips platform represents the most complex case among QEMU-supported
      platforms regarding signaling NaN bit. Up to the Release 6 of Mips
      architecture, "1" in signaling NaN bit denoted signaling NaN, which is
      opposite to IEEE 754-2008 standard. From Release 6 on, Mips architecture
      adopted IEEE standard prescription, and "0" denotes signaling NaN. On top of
      that, Mips architecture for SIMD (also known as MSA, or vector instructions)
      also specifies signaling bit in accordance to IEEE standard. MSA unit can be
      implemented with both pre-Release 6 and Release 6 main processor units.
      
      QEMU uses SoftFloat library to implement various floating-point-related
      instructions on all platforms. The current QEMU implementation allows for
      defining meaning of signaling NaN bit during build time, and is implemented
      via preprocessor macro called SNAN_BIT_IS_ONE.
      
      On the other hand, the change in this patch enables SoftFloat library to be
      configured in run-time. This configuration is meant to occur during CPU
      initialization, at the moment when it is definitely known what desired
      behavior for particular CPU (or any additional FPUs) is.
      
      The change is implemented so that it is consistent with existing
      implementation of similar cases. This means that structure float_status is
      used for passing the information about desired signaling NaN bit on each
      invocation of SoftFloat functions. The additional field in float_status is
      called snan_bit_is_one, which supersedes macro SNAN_BIT_IS_ONE.
      
      IMPORTANT:
      
      This change is not meant to create any change in emulator behavior or
      functionality on any platform. It just provides the means for SoftFloat
      library to be used in a more flexible way - in other words, it will just
      prepare SoftFloat library for usage related to Mips platform and its
      specifics regarding signaling bit meaning, which is done in some of
      subsequent patches from this series.
      
      Further break down of changes:
      
        1) Added field snan_bit_is_one to the structure float_status, and
           correspondent setter function set_snan_bit_is_one().
      
        2) Constants <float16|float32|float64|floatx80|float128>_default_nan
           (used both internally and externally) converted to functions
           <float16|float32|float64|floatx80|float128>_default_nan(float_status*).
           This is necessary since they are dependent on signaling bit meaning.
           At the same time, for the sake of code cleanup and simplicity, constants
           <floatx80|float128>_default_nan_<low|high> (used only internally within
           SoftFloat library) are removed, as not needed.
      
        3) Added a float_status* argument to SoftFloat library functions
           XXX_is_quiet_nan(XXX a_), XXX_is_signaling_nan(XXX a_),
           XXX_maybe_silence_nan(XXX a_). This argument must be present in
           order to enable correct invocation of new version of functions
           XXX_default_nan(). (XXX is <float16|float32|float64|floatx80|float128>
           here)
      
        4) Updated code for all platforms to reflect changes in SoftFloat library.
           This change is twofolds: it includes modifications of SoftFloat library
           functions invocations, and an addition of invocation of function
           set_snan_bit_is_one() during CPU initialization, with arguments that
           are appropriate for each particular platform. It was established that
           all platforms zero their main CPU data structures, so snan_bit_is_one(0)
           in appropriate places is not added, as it is not needed.
      
      [1] "IEEE Standard for Floating-Point Arithmetic",
          IEEE Computer Society, August 29, 2008.
      Signed-off-by: NThomas Schwinge <thomas@codesourcery.com>
      Signed-off-by: NMaciej W. Rozycki <macro@codesourcery.com>
      Signed-off-by: NAleksandar Markovic <aleksandar.markovic@imgtec.com>
      Tested-by: NBastian Koppelmann <kbastian@mail.uni-paderborn.de>
      Reviewed-by: NLeon Alrae <leon.alrae@imgtec.com>
      Tested-by: NLeon Alrae <leon.alrae@imgtec.com>
      Reviewed-by: NPeter Maydell <peter.maydell@linaro.org>
      [leon.alrae@imgtec.com:
       * cherry-picked 2 chunks from patch #2 to fix compilation warnings]
      Signed-off-by: NLeon Alrae <leon.alrae@imgtec.com>
      af39bc8c
  12. 19 5月, 2016 1 次提交
  13. 23 3月, 2016 1 次提交
    • M
      include/qemu/osdep.h: Don't include qapi/error.h · da34e65c
      Markus Armbruster 提交于
      Commit 57cb38b3 included qapi/error.h into qemu/osdep.h to get the
      Error typedef.  Since then, we've moved to include qemu/osdep.h
      everywhere.  Its file comment explains: "To avoid getting into
      possible circular include dependencies, this file should not include
      any other QEMU headers, with the exceptions of config-host.h,
      compiler.h, os-posix.h and os-win32.h, all of which are doing a
      similar job to this file and are under similar constraints."
      qapi/error.h doesn't do a similar job, and it doesn't adhere to
      similar constraints: it includes qapi-types.h.  That's in excess of
      100KiB of crap most .c files don't actually need.
      
      Add the typedef to qemu/typedefs.h, and include that instead of
      qapi/error.h.  Include qapi/error.h in .c files that need it and don't
      get it now.  Include qapi-types.h in qom/object.h for uint16List.
      
      Update scripts/clean-includes accordingly.  Update it further to match
      reality: replace config.h by config-target.h, add sysemu/os-posix.h,
      sysemu/os-win32.h.  Update the list of includes in the qemu/osdep.h
      comment quoted above similarly.
      
      This reduces the number of objects depending on qapi/error.h from "all
      of them" to less than a third.  Unfortunately, the number depending on
      qapi-types.h shrinks only a little.  More work is needed for that one.
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      [Fix compilation without the spice devel packages. - Paolo]
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      da34e65c
  14. 29 1月, 2016 1 次提交
    • P
      sh4: Clean up includes · 9d4c9946
      Peter Maydell 提交于
      Clean up includes so that osdep.h is included first and headers
      which it implies are not included manually.
      
      This commit was created with scripts/clean-includes.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Message-id: 1453832250-766-28-git-send-email-peter.maydell@linaro.org
      9d4c9946
  15. 22 10月, 2015 1 次提交
  16. 09 10月, 2015 1 次提交
    • M
      qdev: Protect device-list-properties against broken devices · 4c315c27
      Markus Armbruster 提交于
      Several devices don't survive object_unref(object_new(T)): they crash
      or hang during cleanup, or they leave dangling pointers behind.
      
      This breaks at least device-list-properties, because
      qmp_device_list_properties() needs to create a device to find its
      properties.  Broken in commit f4eb32b5 "qmp: show QOM properties in
      device-list-properties", v2.1.  Example reproducer:
      
          $ qemu-system-aarch64 -nodefaults -display none -machine none -S -qmp stdio
          {"QMP": {"version": {"qemu": {"micro": 50, "minor": 4, "major": 2}, "package": ""}, "capabilities": []}}
          { "execute": "qmp_capabilities" }
          {"return": {}}
          { "execute": "device-list-properties", "arguments": { "typename": "pxa2xx-pcmcia" } }
          qemu-system-aarch64: /home/armbru/work/qemu/memory.c:1307: memory_region_finalize: Assertion `((&mr->subregions)->tqh_first == ((void *)0))' failed.
          Aborted (core dumped)
          [Exit 134 (SIGABRT)]
      
      Unfortunately, I can't fix the problems in these devices right now.
      Instead, add DeviceClass member cannot_destroy_with_object_finalize_yet
      to mark them:
      
      * Hang during cleanup (didn't debug, so I can't say why):
        "realview_pci", "versatile_pci".
      
      * Dangling pointer in cpus: most CPUs, plus "allwinner-a10", "digic",
        "fsl,imx25", "fsl,imx31", "xlnx,zynqmp", because they create such
        CPUs
      
      * Assert kvm_enabled(): "host-x86_64-cpu", host-i386-cpu",
        "host-powerpc64-cpu", "host-embedded-powerpc-cpu",
        "host-powerpc-cpu" (the powerpc ones can't currently reach the
        assertion, because the CPUs are only registered when KVM is enabled,
        but the assertion is arguably in the wrong place all the same)
      
      Make qmp_device_list_properties() fail cleanly when the device is so
      marked.  This improves device-list-properties from "crashes, hangs or
      leaves dangling pointers behind" to "fails".  Not a complete fix, just
      a better-than-nothing work-around.  In the above reproducer,
      device-list-properties now fails with "Can't list properties of device
      'pxa2xx-pcmcia'".
      
      This also protects -device FOO,help, which uses the same machinery
      since commit ef523587 "qdev-monitor: include QOM properties in -device
      FOO, help output", v2.2.  Example reproducer:
      
          $ qemu-system-aarch64 -machine none -device pxa2xx-pcmcia,help
      
      Before:
      
          qemu-system-aarch64: .../memory.c:1307: memory_region_finalize: Assertion `((&mr->subregions)->tqh_first == ((void *)0))' failed.
      
      After:
      
          Can't list properties of device 'pxa2xx-pcmcia'
      
      Cc: "Andreas Färber" <afaerber@suse.de>
      Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
      Cc: Alexander Graf <agraf@suse.de>
      Cc: Anthony Green <green@moxielogic.com>
      Cc: Aurelien Jarno <aurelien@aurel32.net>
      Cc: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
      Cc: Blue Swirl <blauwirbel@gmail.com>
      Cc: Eduardo Habkost <ehabkost@redhat.com>
      Cc: Guan Xuetao <gxt@mprc.pku.edu.cn>
      Cc: Jia Liu <proljc@gmail.com>
      Cc: Leon Alrae <leon.alrae@imgtec.com>
      Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
      Cc: Max Filippov <jcmvbkbc@gmail.com>
      Cc: Michael Walle <michael@walle.cc>
      Cc: Paolo Bonzini <pbonzini@redhat.com>
      Cc: Peter Maydell <peter.maydell@linaro.org>
      Cc: Richard Henderson <rth@twiddle.net>
      Cc: qemu-ppc@nongnu.org
      Cc: qemu-stable@nongnu.org
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: NEduardo Habkost <ehabkost@redhat.com>
      Message-Id: <1443689999-12182-10-git-send-email-armbru@redhat.com>
      4c315c27
  17. 09 7月, 2015 2 次提交
  18. 12 6月, 2015 1 次提交
  19. 26 9月, 2014 1 次提交
  20. 14 3月, 2014 5 次提交
  21. 07 10月, 2013 1 次提交
  22. 29 7月, 2013 1 次提交
    • A
      cpu: Partially revert "cpu: Change qemu_init_vcpu() argument to CPUState" · 14a10fc3
      Andreas Färber 提交于
      Commit c643bed9 moved qemu_init_vcpu() calls to common CPUState code.
      This causes x86 cpu-add to fail with "KVM: setting VAPIC address failed".
      
      The reason for the failure is that CPUClass::kvm_fd is not yet
      initialized in the following call graph:
      ->x86_cpu_realizefn
       ->x86_cpu_apic_realize
        ->qdev_init
         ->device_set_realized
          ->device_reset (hotplugged == 1)
           ->apic_reset_common
            ->vapic_base_update
             ->kvm_apic_vapic_base_update
      This causes attempted KVM vCPU ioctls to fail.
      
      By contrast, in the non-hotplug case the APIC is reset much later, when
      the vCPU is already initialized.
      
      As a quick and safe solution, move the qemu_init_vcpu() call back into
      the targets' realize functions.
      Reported-by: NChen Fan <chen.fan.fnst@cn.fujitsu.com>
      Acked-by: Igor Mammedov <imammedo@redhat.com> (for i386)
      Tested-by: Jia Liu <proljc@gmail.com> (for openrisc)
      Signed-off-by: NAndreas Färber <afaerber@suse.de>
      14a10fc3
  23. 27 7月, 2013 2 次提交
  24. 23 7月, 2013 3 次提交
  25. 10 7月, 2013 2 次提交
  26. 28 6月, 2013 2 次提交
  27. 12 3月, 2013 2 次提交