All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: "Hansen, Dave" <dave.hansen@intel.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
	"Kleen, Andi" <andi.kleen@intel.com>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"linux-drivers-review@eclists.intel.com" 
	<linux-drivers-review@eclists.intel.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [linux-drivers-review] [PATCH] x86/mm: Fix boot with some memory above MAXMEM
Date: Mon, 11 May 2020 18:10:12 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7F61FEF4@ORSMSX115.amr.corp.intel.com> (raw)
In-Reply-To: <5f95e4c2-66fe-42a0-f09f-cb902cd6db9a@intel.com>

> +		pr_err("%lldMB of physical memory is not addressable in the paging mode\n",
> +		       not_addressable >> 20);

Is "MB" the right unit for this. The problem seems to happen for systems with >64TB ... I doubt
the unaddressable memory is just a couple of MBbytes

-Tony

  reply	other threads:[~2020-05-11 18:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 16:37 [PATCH] x86/mm: Fix boot with some memory above MAXMEM Kirill A. Shutemov
2020-05-11 16:43 ` Dave Hansen
2020-05-11 17:04   ` [linux-drivers-review] " Kirill A. Shutemov
2020-05-11 17:09     ` Dave Hansen
2020-05-11 18:10       ` Luck, Tony [this message]
2020-05-11 18:43         ` Kirill A. Shutemov
2020-05-11 18:58           ` Luck, Tony
2020-05-11 21:19             ` Andy Shevchenko
2020-05-12  0:50               ` Luck, Tony
2020-05-12 10:05                 ` Kirill A. Shutemov
2020-05-11 17:07 ` Kirill A. Shutemov

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=3908561D78D1C84285E8C5FCA982C28F7F61FEF4@ORSMSX115.amr.corp.intel.com \
    --to=tony.luck@intel.com \
    --cc=andi.kleen@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-drivers-review@eclists.intel.com \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.