From: Hajime Tazaki <thehajime@gmail.com>
To: johannes@sipsolutions.net
Cc: linux-um@lists.infradead.org, liam@infradead.org, ljs@kernel.org,
ricarkol@google.com
Subject: Re: [PATCH v2 04/10] um: change machine name for uname output
Date: Fri, 24 Jul 2026 15:50:15 +0900 [thread overview]
Message-ID: <m1ecgs9908.wl-thehajime@gmail.com> (raw)
In-Reply-To: <20260723113633.bcaf234695c5.I226381aaaf6dd46c559b0e694b29370d0102ce3f@changeid>
On Thu, 23 Jul 2026 18:35:45 +0900,
Johannes Berg wrote:
>
> From: Hajime Tazaki <thehajime@gmail.com>
>
> This commit tries to display MMU/!MMU mode from the output of uname(2)
> so that users can distinguish which mode of UML is running right now.
>
> Signed-off-by: Hajime Tazaki <thehajime@gmail.com>
> [remove / to fix regression with systemd userspace]
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> v2: regression fix
I'd like to know what kind of regression did you see.
> ---
> arch/um/Makefile | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/um/Makefile b/arch/um/Makefile
> index 937639edc295..1f85b73d4abb 100644
> --- a/arch/um/Makefile
> +++ b/arch/um/Makefile
> @@ -148,6 +148,12 @@ export CFLAGS_vmlinux := $(LINK-y) $(LINK_WRAPS) $(LD_FLAGS_CMDLINE) $(CC_FLAGS_
> CLEAN_FILES += linux x.i gmon.out
> MRPROPER_FILES += $(HOST_DIR)/include/generated
>
> +ifeq ($(CONFIG_MMU),y)
> +UTS_MACHINE := "um"
> +else
> +UTS_MACHINE := "um\(nommu\)"
> +endif
> +
with only this diff, there is no visible changes with uname command on
UML (both mmu/nommu), as setup_machinename() overwrite this.
maybe we could drop this patch if we cannot put a name 'um' in the
machine name ?
-- Hajime
next prev parent reply other threads:[~2026-07-24 6:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 9:35 [PATCH v2 00/10] simplified UML/NOMMU approach Johannes Berg
2026-07-23 9:35 ` [PATCH v2 01/10] x86/um: nommu: elf loader for fdpic Johannes Berg
2026-07-23 9:35 ` [PATCH v2 02/10] um: decouple MMU specific code from the common part Johannes Berg
2026-07-23 9:35 ` [PATCH v2 03/10] um: nommu: memory handling Johannes Berg
2026-07-23 9:35 ` [PATCH v2 04/10] um: change machine name for uname output Johannes Berg
2026-07-24 6:50 ` Hajime Tazaki [this message]
2026-07-24 6:54 ` Johannes Berg
2026-07-24 7:16 ` Hajime Tazaki
2026-07-24 7:18 ` Hajime Tazaki
2026-07-24 7:18 ` Johannes Berg
2026-07-23 9:35 ` [PATCH v2 05/10] x86/um/vdso: nommu: vdso memory update Johannes Berg
2026-07-23 9:35 ` [PATCH v2 06/10] um: further decouple MMU related code Johannes Berg
2026-07-23 9:35 ` [PATCH v2 07/10] um: nommu: add SMP futex operations Johannes Berg
2026-07-23 9:35 ` [PATCH v2 08/10] um: nommu: add userspace runner processes Johannes Berg
2026-07-23 13:59 ` Johannes Berg
2026-07-23 9:35 ` [PATCH v2 09/10] um: allow deselecting CONFIG_MMU Johannes Berg
2026-07-23 9:35 ` [PATCH v2 10/10] Documentation: um: document nommu UML Johannes Berg
2026-07-24 6:20 ` Hajime Tazaki
2026-07-24 6:49 ` Johannes Berg
2026-07-24 6:53 ` Hajime Tazaki
2026-07-23 11:50 ` [PATCH v2 00/10] simplified UML/NOMMU approach Lorenzo Stoakes (ARM)
2026-07-23 12:22 ` Johannes Berg
2026-07-23 15:11 ` Lorenzo Stoakes (ARM)
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=m1ecgs9908.wl-thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=liam@infradead.org \
--cc=linux-um@lists.infradead.org \
--cc=ljs@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox