qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: [PULL 00/10] Linux user for 7.0 patches
Date: Thu, 24 Mar 2022 09:20:06 +0100	[thread overview]
Message-ID: <20220324082016.3463521-1-laurent@vivier.eu> (raw)

The following changes since commit 48fb0a826eea2e7b0135f49e7fa63e7efe2b7677:

  Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into staging (2022-03-21 21:27:14 +0000)

are available in the Git repository at:

  https://gitlab.com/laurent_vivier/qemu.git tags/linux-user-for-7.0-pull-request

for you to fetch changes up to 330ea9d1d819680ac7501457220b8cd1c29f9d2f:

  linux-user/arm: Implement __kernel_cmpxchg64 with host atomics (2022-03-23 16:53:17 +0100)

----------------------------------------------------------------
linux-user pull request 20220324

Fix MIPS n32
Fix ppoll, epoll_wait, pselect
Fix error message in elfload.c
Implement ARM __kernel_memory_barrier/__kernel_cmpxchg/__kernel_cmpxchg64

----------------------------------------------------------------

Fergus Henderson (1):
  linux-user: Fix missing space in error message

Richard Henderson (8):
  linux-user/alpha: Fix sigsuspend for big-endian hosts
  linux-user: Split out helpers for sigsuspend
  linux-user: Properly handle sigset arg to pselect
  linux-user: Properly handle sigset arg to epoll_pwait
  linux-user: Properly handle sigset arg to ppoll
  linux-user/arm: Implement __kernel_memory_barrier
  linux-user/arm: Implement __kernel_cmpxchg with host atomics
  linux-user/arm: Implement __kernel_cmpxchg64 with host atomics

WANG Xuerui (1):
  linux-user: Fix syscall parameter handling for MIPS n32

 linux-user/arm/cpu_loop.c   | 164 ++++++++++++++++++++++--------------
 linux-user/elfload.c        |   2 +-
 linux-user/signal-common.h  |  26 ++++++
 linux-user/signal.c         |  23 +++++
 linux-user/syscall.c        | 119 ++++++++++----------------
 linux-user/user-internals.h |   6 +-
 6 files changed, 195 insertions(+), 145 deletions(-)

-- 
2.35.1



             reply	other threads:[~2022-03-24  8:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24  8:20 Laurent Vivier [this message]
2022-03-24  8:20 ` [PULL 01/10] linux-user: Fix syscall parameter handling for MIPS n32 Laurent Vivier
2022-03-24  8:20 ` [PULL 02/10] linux-user/alpha: Fix sigsuspend for big-endian hosts Laurent Vivier
2022-03-24  8:20 ` [PULL 03/10] linux-user: Split out helpers for sigsuspend Laurent Vivier
2022-03-24  8:20 ` [PULL 04/10] linux-user: Properly handle sigset arg to pselect Laurent Vivier
2022-03-24  8:20 ` [PULL 05/10] linux-user: Properly handle sigset arg to epoll_pwait Laurent Vivier
2022-03-24  8:20 ` [PULL 06/10] linux-user: Properly handle sigset arg to ppoll Laurent Vivier
2022-03-24  8:20 ` [PULL 07/10] linux-user: Fix missing space in error message Laurent Vivier
2022-03-24  8:20 ` [PULL 08/10] linux-user/arm: Implement __kernel_memory_barrier Laurent Vivier
2022-03-24  8:20 ` [PULL 09/10] linux-user/arm: Implement __kernel_cmpxchg with host atomics Laurent Vivier
2022-03-24  8:20 ` [PULL 10/10] linux-user/arm: Implement __kernel_cmpxchg64 " Laurent Vivier
2022-03-24 20:08 ` [PULL 00/10] Linux user for 7.0 patches Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220324082016.3463521-1-laurent@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).