Re: [PATCH] docs: Remove literal markup from Documentation/ paths

ile is being > referred. Also change the surrounding text when needed so it reads well > both in the source and the web page (eg. 'see file Doc...' -> 'see > Doc...'). > > Signed-off-by: Nícolas F. R. A. Prado Acked-by: SeongJae Park Thanks, SJ [...]

Re: [PATCH] um: add back support for FXSAVE registers

On Tue, 7 Jan 2025 13:07:58 -0800 SeongJae Park wrote: > Hello, > > On Wed, 4 Dec 2024 08:48:27 +0100 Benjamin Berg > wrote: > > > From: Benjamin Berg > > > > It was reported that qemu may not enable the XSTATE CPU extension, which > > is a req

Re: [PATCH] um: add back support for FXSAVE registers

> as supporting this would require more backward compatibility to build a > correct signal frame. > > Fixes: 3f17fed21491 ("um: switch to regset API and depend on XSTATE") > Reported-by: SeongJae Park > Closes: https://lore.kernel.org/r/20241203070218.240797-1...@kernel.or

Re: [PATCH v5] um: switch to regset API and depend on XSTATE

On Tue, 03 Dec 2024 18:07:36 +0100 Benjamin Berg wrote: > On Tue, 2024-12-03 at 07:56 -0800, SeongJae Park wrote: > > On Tue, 03 Dec 2024 07:01:09 SeongJae Park wrote: > > > > > On Tue, 03 Dec 2024 09:40:34 +0100 Benjamin Berg > > > wrote: > > >

Re: [PATCH v5] um: switch to regset API and depend on XSTATE

On Tue, 03 Dec 2024 07:01:09 SeongJae Park wrote: > On Tue, 03 Dec 2024 09:40:34 +0100 Benjamin Berg > wrote: > > > Hi, > > > > that probably means the size detection for the FPU state (i.e. > > PTRACE_GETREGSET for NT_X86_XSTATE is incorrect on a 32bit

Re: [PATCH v5] um: switch to regset API and depend on XSTATE

_64, sorry. Thanks, SJ > > Benjamin > > On Mon, 2024-12-02 at 23:02 -0800, SeongJae Park wrote: > > Hello, > > > > > > On Wed, 23 Oct 2024 11:41:20 +0200 Benjamin Berg > > wrote: > > > > > From: Benjamin Berg > > > > > > T

Re: [PATCH v5] um: switch to regset API and depend on XSTATE

Hello, On Wed, 23 Oct 2024 11:41:20 +0200 Benjamin Berg wrote: > From: Benjamin Berg > > The PTRACE_GETREGSET API has now existed since Linux 2.6.33. The XSAVE > CPU feature should also be sufficiently common to be able to rely on it. > > With this, define our internal FP state to be the ho

Re: [PATCH 1/1] arch/um: fix forward declaration for vmalloc

h, etc. > This is likely the reason why this forward declaration was introduced > in the first place. > > [1] https://lore.kernel.org/all/20240321163705.3067592-31-sur...@google.com/ > > Fixes: 576477564ede ("mm: vmalloc: enable memory allocation profiling") > Reported

Re: Cannot compile UML in Ubuntu 20.04.5 anymore

+# GCC versions < 11. See: > +# https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99652 > # > +ifeq ($(CONFIG_CC_IS_CLANG),y) > KBUILD_CFLAGS += -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx > KBUILD_RUSTFLAGS += > -Ctarget-feature=-sse,-sse2,-sse3,-ssse3,-sse4.1,-sse4.2,-avx,-av

Re: [PATCH] UML: define RUNTIME_DISCARD_EXIT

94398bde27 ("s390: define RUNTIME_DISCARD_EXIT to fix link error > with GNU ld < 2.36") > - c1c551bebf92 ("sh: define RUNTIME_DISCARD_EXIT") > > Fixes: 99cb0d917ffa ("arch: fix broken BuildID for arm64 and riscv") > Reported-by: SeongJae Park > Si