From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-nvdimm <linux-nvdimm@lists.01.org>,
Linux MM <linux-mm@kvack.org>,
Dave Hansen <dave.hansen@intel.com>,
"Luck, Tony" <tony.luck@intel.com>
Subject: Re: [GIT PULL] device-dax for 5.1: PMEM as RAM
Date: Sun, 10 Mar 2019 17:21:56 -0700 [thread overview]
Message-ID: <CAHk-=wiTM93XKaFqUOR7q7133wvzNS8Kj777EZ9E8S99NbZhAA@mail.gmail.com> (raw)
In-Reply-To: <CAPcyv4hafLUr2rKdLG+3SHXyWaa0d_2g8AKKZRf2mKPW+3DUSA@mail.gmail.com>
On Sun, Mar 10, 2019 at 4:54 PM Dan Williams <dan.j.williams@intel.com> wrote:
>
> Unfortunately this particular b0rkage is not constrained to nvmem.
> I.e. there's nothing specific about nvmem requiring mc-safe memory
> copy, it's a cpu problem consuming any poison regardless of
> source-media-type with "rep; movs".
So why is it sold and used for the nvdimm pmem driver?
People told me it was a big deal and machines died.
You can't suddenly change the story just because you want to expose it
to user space.
You can't have it both ways. Either nvdimms have more likelihood of,
and problems with, machine checks, or it doesn't.
The end result is the same: if intel believes the kernel needs to
treat nvdimms specially, then we're sure as hell not exposing those
snowflakes to user space.
And if intel *doesn't* believe that, then we're removing the mcsafe_* functions.
There's no "oh, it's safe to show to user space, but the kernel is
magical" middle ground here that makes sense to me.
Linus
next prev parent reply other threads:[~2019-03-11 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 19:54 [GIT PULL] device-dax for 5.1: PMEM as RAM Dan Williams
2019-03-10 20:01 ` Linus Torvalds
2019-03-10 23:54 ` Dan Williams
2019-03-11 0:21 ` Linus Torvalds [this message]
2019-03-11 15:37 ` Dan Williams
2019-03-12 0:07 ` Linus Torvalds
2019-03-12 0:30 ` Dan Williams
2019-03-15 17:33 ` Dan Williams
2019-05-15 20:26 ` Dan Williams
2019-03-16 21:25 ` pr-tracker-bot
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='CAHk-=wiTM93XKaFqUOR7q7133wvzNS8Kj777EZ9E8S99NbZhAA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=tony.luck@intel.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).