mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: lizhe.67@bytedance.com, tglx@linutronix.de, mingo@redhat.com,
	bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
	hpa@zytor.com
Cc: lizefan.x@bytedance.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC v2] memmap: introduce cmdline parameter "memmap=nn[KMG]$" without start addr
Date: Tue, 28 Jun 2022 08:52:00 -0700	[thread overview]
Message-ID: <2eff7546-5ab5-d4cd-43f6-d66b6490d725@intel.com> (raw)
In-Reply-To: <20220628124529.15431-1-lizhe.67@bytedance.com>

On 6/28/22 05:45, lizhe.67@bytedance.com wrote:
> From: Li Zhe <lizhe.67@bytedance.com>
> 
> In current kernel we can use memmap=nn[KMG]$ss[KMG] to reserve an
> area of memory for userspace usage through /dev/mem. We have to
> determine the start addr and length. In our scenario, we need
> reserve or alloc large continuous physical memory at least 256M in
> 512G's machine, and need reserve more memory in larger machine, at
> just boot phase for a userspace program. And these memories will not
> be freed to system before system reboot. The userspace program can
> use the memory through /dev/mem to store some data. Besides, a
> hardware will need the data stored by the userspace program to do
> it's job. Why we need continuous memory is that the hardware can
> only access memory without mmu.

That's still a rather anemic description.

I don't think we want this code in the kernel with that description, sorry.

If you'd like to come back with an actual description, naming the exact
hardware that you have *AND* explaining sane reasons for why the
hardware doesn't have a normal kernel driver (or interface) like every
other piece of hardware, then we can talk.  But, otherwise, this isn't
something that can go upstream.

      reply	other threads:[~2022-06-28 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 12:45 lizhe.67
2022-06-28 15:52 ` Dave Hansen [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=2eff7546-5ab5-d4cd-43f6-d66b6490d725@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan.x@bytedance.com \
    --cc=lizhe.67@bytedance.com \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®