From: Borislav Petkov <bp@suse.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Dave Hansen <dave.hansen@intel.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
x86@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Yazen Ghannam <yazen.ghannam@amd.com>
Subject: Re: [PATCH] mm/hwpoison: Clear PRESENT bit for kernel 1:1 mappings of poison pages
Date: Thu, 22 Jun 2017 11:39:05 +0200 [thread overview]
Message-ID: <20170622093904.ajzoi43vlkejqgi3@pd.tnic> (raw)
In-Reply-To: <20170621174740.npbtg2e4o65tyrss@intel.com>
On Wed, Jun 21, 2017 at 10:47:40AM -0700, Luck, Tony wrote:
> I would if I could work out how to use it. From reading the manual
> page there seem to be a few options to this, but none of them appear
> to just drop a specific address (apart from my own). :-(
$ git send-email --to ... --cc ... --cc ... --suppress-cc=all ...
That should send only to the ones you have in --to and --cc and suppress
the rest.
Do a
$ git send-email -v --dry-run --to ... --cc ... --cc ... --suppress-cc=all ...
to see what it is going to do.
> I'd assume that other X86 implementations would face similar issues (unless
> they have extremely cautious pre-fetchers and/or no speculation).
>
> I'm also assuming that non-X86 architectures that do recovery may want this
> too ... hence hooking the arch_unmap_kpfn() function into the generic
> memory_failure() code.
Which means that you could move the function to generic
mm/memory_failure.c code after making the decoy_addr computation
generic.
I'd still like to hear some sort of confirmation from other
vendors/arches whether it makes sense for them too, though.
I mean, if they don't do speculative accesses, then it probably doesn't
matter even - the page is innacessible anyway but still...
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2017-06-22 9:39 UTC|newest]
Thread overview: 22+ 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)
2017-06-21 20:19 ` Luck, Tony
2017-06-22 9:39 ` Borislav Petkov [this message]
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 10:19 ` [tip:x86/mm] x86/mm, " tip-bot for Tony Luck
2017-08-17 22:09 ` [PATCH-resend] " 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=20170622093904.ajzoi43vlkejqgi3@pd.tnic \
--to=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=tony.luck@intel.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).