mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tiwei Bie" <tiwei.btw@antgroup.com>
To: Benjamin Berg <benjamin@sipsolutions.net>,
	Johannes Berg <johannes@sipsolutions.net>,
	richard@nod.at, anton.ivanov@cambridgegreys.com
Cc: linux-um@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] um: Remove 3-level page table support on i386
Date: Thu, 19 Sep 2024 15:47:42 +0800	[thread overview]
Message-ID: <75b42537-e895-4c3a-85b5-3c9beab3e149@antgroup.com> (raw)
In-Reply-To: <627bd11a7fe69fed02719c2ecf5370b59328e80d.camel@sipsolutions.net>

On 2024/9/19 15:22, Benjamin Berg wrote:
> On Thu, 2024-09-19 at 08:54 +0200, Johannes Berg wrote:
>> On Wed, 2024-09-18 at 14:17 +0800, Tiwei Bie wrote:
>>> The highmem support has been removed by commit a98a6d864d3b ("um:
>>> Remove broken highmem support"). The 2-level page table is
>>> sufficient
>>> on UML/i386 now. Remove the 3-level page table support on UML/i386
>>> which is still marked as experimental.
>>>
>>
>> No real objection, but with the 4-level page table work on 64-bit
>> pending as well (which likely conflicts), I wonder if we should just
>> remove 3-level *entirely*?

Fine with me in either way. Keeping only one page table implementation
on UML/x86_64 may require smaller maintenance effort.

> 
> Fine with me. There is only the tiny advantage of saving a few pages of
> memory for each process. I just erred on the side of keeping it in case
> anyone is cares to the option …
> 
> I'll resubmit the patchset without 3-level support then, possibly on
> top of this patch.

Thanks! :)

Regards,
Tiwei

> On the assumption that no one actually cares about
> 3-level page tables on x86_64.
> 
> Benjamin


      reply	other threads:[~2024-09-19  7:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18  6:17 Tiwei Bie
2024-09-19  6:54 ` Johannes Berg
2024-09-19  7:22   ` Benjamin Berg
2024-09-19  7:47     ` Tiwei Bie [this message]

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=75b42537-e895-4c3a-85b5-3c9beab3e149@antgroup.com \
    --to=tiwei.btw@antgroup.com \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=benjamin@sipsolutions.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-um@lists.infradead.org \
    --cc=richard@nod.at \
    /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

all inboxes | Powered by JetHome®