From: Richard Weinberger <richard@nod.at>
To: torvalds <torvalds@linux-foundation.org>
Cc: linux-um <linux-um@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] UML fixes for v6.14-rc3
Date: Sat, 15 Feb 2025 23:21:03 +0100 (CET) [thread overview]
Message-ID: <153400218.11019314.1739658063786.JavaMail.zimbra@nod.at> (raw)
Linus,
The following changes since commit a64dcfb451e254085a7daee5fe51bf22959d52d3:
Linux 6.14-rc2 (2025-02-09 12:45:03 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/uml/linux.git tags/uml-for-linus-6.14-rc3
for you to fetch changes up to 96178631c3f53398044ed437010f7632ad764bf8:
um: convert irq_lock to raw spinlock (2025-02-12 23:40:59 +0100)
----------------------------------------------------------------
This pull request contains the following bug fixes for UML:
- Align signal stack correctly
- Convert to raw spinlocks where needed (irq and virtio)
- FPU related fixes
----------------------------------------------------------------
Benjamin Berg (4):
um: add back support for FXSAVE registers
um: avoid copying FP state from init_task
um: properly align signal stack on x86_64
um: fix execve stub execution on old host OSs
Johannes Berg (3):
um: virt-pci: don't use kmalloc()
um: virtio_uml: use raw spinlock
um: convert irq_lock to raw spinlock
arch/um/drivers/virt-pci.c | 198 ++++++++++++++++++++-------------------
arch/um/drivers/virtio_uml.c | 8 +-
arch/um/kernel/irq.c | 79 +++++++++-------
arch/um/kernel/process.c | 10 +-
arch/um/os-Linux/skas/process.c | 16 +++-
arch/x86/um/os-Linux/registers.c | 21 ++++-
arch/x86/um/signal.c | 13 ++-
7 files changed, 203 insertions(+), 142 deletions(-)
next reply other threads:[~2025-02-15 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 22:21 Richard Weinberger [this message]
2025-02-16 1:31 ` [GIT PULL] UML fixes for v6.14-rc3 pr-tracker-bot
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=153400218.11019314.1739658063786.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=torvalds@linux-foundation.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).