From: David Hildenbrand <david@redhat.com>
To: "zhaowei1102@thundersoft.com" <zhaowei1102@thundersoft.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
kerneldev <kerneldev@karsmulder.nl>,
Arvind Sankar <nivedita@alum.mit.edu>,
Joe Perches <joe@perches.com>, gpiccoli <gpiccoli@canonical.com>,
aquini <aquini@redhat.com>, gustavoars <gustavoars@kernel.org>,
ojeda <ojeda@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
guohanjun <guohanjun@huawei.com>,
mchehab+huawei <mchehab+huawei@kernel.org>
Subject: Re: [PATCH v2 0/2] Make it possible to reserve memory on 64bit platform
Date: Mon, 18 Jan 2021 10:50:26 +0100 [thread overview]
Message-ID: <15269a61-3b16-4c07-2486-6940c559261e@redhat.com> (raw)
In-Reply-To: <202101181151049299923@thundersoft.com>
On 18.01.21 04:51, zhaowei1102@thundersoft.com wrote:
> On Sat, Jan 16, 2021 at 2:43 AM Wesley Zhao
> <zhaowei1102@thundersoft.com> wrote:
> >>
> >> I was trying to reserve some memory to save logs incase that
> Android panic or hang and then
> >> I can read the logs from QNX side from the memory reserved before
> on the Qualcomm 8155 hypervisor platform,
> >> and I find the "reserve=" parameter only support 32bit,so I made
> some change and send these patches.
> >
> >See Documentation/admin-guide/kernel-parameters.txt
> >
> > memmap=nn[KMG]$ss[KMG]
> > [KNL,ACPI] Mark specific memory as reserved.
> > Region of memory to be reserved is from ss
> to ss+nn.
> > Example: Exclude memory from
> 0x18690000-0x1869ffff
> > memmap=64K$0x18690000
> > or
> > memmap=0x10000$0x18690000
> > Some bootloaders may need an escape character
> >before '$',
> > like Grub2, otherwise '$' and the following
> number
> > will be eaten.
> Sorry,what is your point:
> static int __init reserve_setup(char *str)
> static struct resource reserve[MAXRESERVE];
> for (;;) {
> unsigned int io_start, io_num;* // these code is not compatible
> with 64bit,i start from here*
>
Dan's point is that you should look into using "memmap=" instead of
"reserve=".
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-01-18 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 10:41 [PATCH v2 0/2] Make it possible to reserve memory on 64bit platform Wesley Zhao
2021-01-16 10:41 ` [PATCH v2 1/2] lib/cmdline: add new function get_option_ull() Wesley Zhao
2021-01-17 19:02 ` [PATCH v2 0/2] Make it possible to reserve memory on 64bit platform Dan Williams
[not found] ` <202101181151049299923@thundersoft.com>
2021-01-18 9:50 ` David Hildenbrand [this message]
[not found] ` <202101221536190259795@thundersoft.com>
2021-01-22 10:21 ` Andy Shevchenko
2021-01-18 10:42 ` Andy Shevchenko
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=15269a61-3b16-4c07-2486-6940c559261e@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aquini@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=gpiccoli@canonical.com \
--cc=guohanjun@huawei.com \
--cc=gustavoars@kernel.org \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=kerneldev@karsmulder.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=nivedita@alum.mit.edu \
--cc=ojeda@kernel.org \
--cc=tglx@linutronix.de \
--cc=zhaowei1102@thundersoft.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;
as well as URLs for NNTP newsgroup(s).