From: "Elliott, Robert (Persistent Memory)" <elliott@hpe.com>
To: "Luck, Tony" <tony.luck@intel.com>, Borislav Petkov <bp@suse.de>
Cc: Dave Hansen <dave.hansen@intel.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yazen Ghannam <yazen.ghannam@amd.com>,
"'dan.j.williams@intel.com'" <dan.j.williams@intel.com>,
"Kani, Toshimitsu" <toshi.kani@hpe.com>,
"Vaden, Tom (HPE Server OS Architecture)" <tom.vaden@hpe.com>
Subject: RE: [PATCH] mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison pages
Date: Wed, 21 Jun 2017 19:59:07 +0000 [thread overview]
Message-ID: <AT5PR84MB0082333B55A6823A73C28989ABDA0@AT5PR84MB0082.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20170621174740.npbtg2e4o65tyrss@intel.com>
> + decoy_addr = (pfn << PAGE_SHIFT) + (PAGE_OFFSET ^ BIT(63));
> +#else
> +#error "no unused virtual bit available"
> +#endif
> +
> + if (set_memory_np(decoy_addr, 1))
> + pr_warn("Could not invalidate pfn=0x%lx from 1:1 map \n", pfn);
Does this patch handle breaking up 512 GiB, 1 GiB or 2 MiB page mappings
if it's just trying to mark a 4 KiB page as bad?
Although the kernel doesn't use MTRRs itself anymore, what if the system
BIOS still uses them for some memory regions, and the bad address falls in
an MTRR region?
---
Robert Elliott, HPE Persistent Memory
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-06-21 19:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 19:02 [PATCH] mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison pages Luck, Tony
2017-06-19 18:01 ` Borislav Petkov
2017-06-21 17:47 ` Luck, Tony
2017-06-21 19:59 ` Elliott, Robert (Persistent Memory) [this message]
2017-06-21 20:19 ` Luck, Tony
2017-06-22 9:39 ` Borislav Petkov
2017-06-29 22:11 ` git send-email (w/o Cc: stable) Luck, Tony
2017-06-30 7:08 ` Borislav Petkov
2017-06-23 22:19 ` [PATCH] mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison pages Elliott, Robert (Persistent Memory)
2017-06-27 22:04 ` Luck, Tony
2017-06-27 22:09 ` Dan Williams
2017-08-16 17:18 ` [PATCH-resend] " Luck, Tony
2017-08-17 22:09 ` Andrew Morton
2017-08-17 22:29 ` Elliott, Robert (Persistent Memory)
2017-08-17 23:32 ` Luck, Tony
2017-06-21 2:12 ` [PATCH] " Naoya Horiguchi
2017-06-21 17:54 ` Luck, Tony
2017-06-21 19:47 ` Elliott, Robert (Persistent Memory)
2017-06-21 20:30 ` Luck, Tony
2017-06-23 5:07 ` Dan Williams
2017-06-23 20:59 ` Luck, Tony
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=AT5PR84MB0082333B55A6823A73C28989ABDA0@AT5PR84MB0082.NAMPRD84.PROD.OUTLOOK.COM \
--to=elliott@hpe.com \
--cc=bp@suse.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=tom.vaden@hpe.com \
--cc=tony.luck@intel.com \
--cc=toshi.kani@hpe.com \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.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).