From: Hajime Tazaki <thehajime@gmail.com>
To: benjamin@sipsolutions.net
Cc: linux-um@lists.infradead.org, ricarkol@google.com,
Liam.Howlett@oracle.com
Subject: Re: [PATCH v7 10/13] x86/um: nommu: signal handling
Date: Thu, 19 Jun 2025 21:55:42 +0900 [thread overview]
Message-ID: <m27c176gc1.wl-thehajime@gmail.com> (raw)
In-Reply-To: <a81b27bdf40fba54b28325bdb28f697c48a005d6.camel@sipsolutions.net>
Thanks,
# this is a thread of my older series, v7 (current one is v9), tho
your comment is still valid so, thanks !
On Thu, 19 Jun 2025 20:43:06 +0900,
Benjamin Berg wrote:
>
> Hi,
>
> I am not sure that fxsaveq/fxrstorq is guaranteed to be sufficient. I
> don't think that catches some of the newer AVX registers for example.
I've added fxsaveq/fxrstorq parts with your suggestion,
test-signal-restore.c. I think I may not know all of userspace
situations with register usage so, my current approach is to address
each issue when we faced real issue with a concrete test case.
> At the same time, dealing with all that properly could be rather
> annoying. I don't really have a solution for that, normal UM does not
> need to deal with many of those details …
thanks for the input.
I'm also/always trying to study a lot from existing code base.
-- Hajime
next prev parent reply other threads:[~2025-06-19 15:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 6:00 [PATCH v7 00/13] nommu UML Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 01/13] x86/um: clean up elf specific definitions Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 02/13] x86/um: nommu: elf loader for fdpic Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 03/13] um: decouple MMU specific code from the common part Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 04/13] um: nommu: memory handling Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 05/13] x86/um: nommu: syscall handling Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 06/13] um: nommu: seccomp syscalls hook Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 07/13] x86/um: nommu: process/thread handling Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 08/13] um: nommu: configure fs register on host syscall invocation Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 09/13] x86/um/vdso: nommu: vdso memory update Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 10/13] x86/um: nommu: signal handling Hajime Tazaki
2025-06-19 11:43 ` Benjamin Berg
2025-06-19 12:55 ` Hajime Tazaki [this message]
2025-01-20 6:00 ` [PATCH v7 11/13] um: change machine name for uname output Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 12/13] um: nommu: add documentation of nommu UML Hajime Tazaki
2025-01-20 6:00 ` [PATCH v7 13/13] um: nommu: plug nommu code into build system Hajime Tazaki
2025-02-04 12:26 ` [PATCH v7 00/13] nommu UML Hajime Tazaki
2025-04-25 13:49 ` Lorenzo Stoakes
2025-04-27 3:49 ` Hajime Tazaki
2025-04-29 13:23 ` Lorenzo Stoakes
2025-04-30 9:51 ` Johannes Berg
2025-05-01 10:40 ` Lorenzo Stoakes
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=m27c176gc1.wl-thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=benjamin@sipsolutions.net \
--cc=linux-um@lists.infradead.org \
--cc=ricarkol@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.