1. 29 10月, 2018 1 次提交
  2. 19 10月, 2018 1 次提交
  3. 23 1月, 2017 1 次提交
  4. 23 9月, 2016 1 次提交
  5. 21 9月, 2016 1 次提交
    • P
      linux-user: Use correct target SHMLBA in shmat() · ee8e7614
      Peter Maydell 提交于
      The shmat() handling needs to do target-specific handling
      of the attach address for shmat():
       * if the SHM_RND flag is passed, the address is rounded
         down to a SHMLBA boundary
       * if SHM_RND is not passed, then the call is failed EINVAL
         if the address is not a multiple of SHMLBA
      
      Since SHMLBA is target-specific, we need to do this
      checking and rounding in QEMU and can't leave it up to the
      host syscall.
      
      Allow targets to define TARGET_FORCE_SHMLBA and provide
      a target_shmlba() function if appropriate, and update
      do_shmat() to honour them.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Signed-off-by: NRiku Voipio <riku.voipio@linaro.org>
      ee8e7614
  6. 12 7月, 2016 1 次提交
    • M
      linux-user: Clean up target_syscall.h header guards · 3622634b
      Markus Armbruster 提交于
      Some of them use guard symbol TARGET_SYSCALL_H, but we also have
      CRIS_SYSCALL_H, MICROBLAZE_SYSCALLS_H, TILEGX_SYSCALLS_H and
      __UC32_SYSCALL_H__.  They all upset scripts/clean-header-guards.pl.
      
      Reuse of the same guard symbol TARGET_SYSCALL_H in multiple headers is
      okay as long as they cannot be included together.  The script can't
      tell, so it warns.
      
      The script dislikes the other guard symbols, too.  They don't match
      their file name (they should, to make guard collisions less likely),
      and __UC32_SYSCALL_H__ is a reserved identifier.
      
      Clean them all up: use guard symbol $target_TARGET_SYSCALL_H for
      linux-user/$target/target_sycall.h.
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      Reviewed-by: NRichard Henderson <rth@twiddle.net>
      3622634b
  7. 27 5月, 2016 1 次提交
  8. 24 2月, 2016 1 次提交
  9. 22 8月, 2014 2 次提交
  10. 10 3月, 2014 1 次提交
  11. 23 7月, 2013 1 次提交
    • P
      linux-user: Clean up handling of clone() argument order · 4ce6243d
      Peter Maydell 提交于
      Linux manages to have three separate orderings of the arguments to
      the clone() syscall on different architectures. In the kernel these
      are selected via CONFIG_CLONE_BACKWARDS and CONFIG_CLONE_BACKWARDS2.
      Clean up our implementation of this to use similar #define names
      rather than a TARGET_* ifdef ladder.
      
      This includes behaviour changes fixing bugs on cris, x86-64, m68k,
      openrisc and unicore32.  cris had explicit but wrong handling; the
      others were just incorrectly using QEMU's default, which happened
      to be the equivalent of CONFIG_CLONE_BACKWARDS. (unicore32 appears
      to be broken in the mainline kernel in that it tries to use arg3 for
      both parent_tidptr and newtls simultaneously -- we don't attempt
      to emulate this bug...)
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Signed-off-by: NRiku Voipio <riku.voipio@linaro.org>
      4ce6243d
  12. 05 3月, 2013 1 次提交
  13. 02 2月, 2012 1 次提交
  14. 15 10月, 2007 1 次提交
  15. 30 9月, 2007 1 次提交
  16. 01 6月, 2007 1 次提交
  17. 27 11月, 2005 1 次提交