From: Boris Petkov <bp@alien8.de>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Tony Luck <tony.luck@gmail.com>,
linux-nvdimm <linux-nvdimm@ml01.01.org>, X86 ML <x86@kernel.org>,
"elliott@hpe.com" <elliott@hpe.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
Ingo Molnar <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHV5 3/3] x86, ras: Add __mcsafe_copy() function to recover from machine checks
Date: Sun, 27 Dec 2015 14:17:37 +0100 [thread overview]
Message-ID: <6c0b3214-f120-47ee-b7fe-677b4f27f039@email.android.com> (raw)
In-Reply-To: <CALCETrUcSB8ix0HSPyTwXT46gMAE2iGVZ8V1kEbkQVxVqrQFiQ@mail.gmail.com>
Andy Lutomirski <luto@amacapital.net> wrote:
>You certainly can, but it doesn't scale well to multiple users of
>similar mechanisms. It also prevents you from using the same
>mechanism in anything that could be inlined, which is IMO kind of
>unfortunate.
Well, but the bit 31 game doesn't make it any better than the bit 63 fun IMO. Should the exception table entry maybe grow a u32 flags instead?
--
Sent from a small device: formatting sux and brevity is inevitable.
next prev parent reply other threads:[~2015-12-27 13:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 20:54 [PATCHV4 0/3] Machine check recovery when kernel accesses poison Tony Luck
2015-12-16 1:29 ` [PATCHV4 1/3] x86, ras: Add new infrastructure for machine check fixup tables Tony Luck
2015-12-16 1:29 ` [PATCHV4 2/3] x86, ras: Extend machine check recovery code to annotated ring0 areas Tony Luck
2015-12-16 1:30 ` [PATCHV4 3/3] x86, ras: Add __mcsafe_copy() function to recover from machine checks Tony Luck
2015-12-24 21:46 ` Borislav Petkov
2015-12-16 1:30 ` [PATCHV5 " Tony Luck
2015-12-25 11:49 ` Borislav Petkov
2015-12-25 20:05 ` Luck, Tony
2015-12-26 10:32 ` Borislav Petkov
2015-12-26 14:54 ` Andy Lutomirski
2015-12-27 2:08 ` Tony Luck
2015-12-27 2:15 ` Andy Lutomirski
2015-12-27 2:16 ` Andy Lutomirski
2015-12-27 6:57 ` Tony Luck
2015-12-27 10:09 ` Borislav Petkov
2015-12-27 12:19 ` Andy Lutomirski
2015-12-27 13:17 ` Boris Petkov [this message]
2015-12-27 13:25 ` Andy Lutomirski
2015-12-27 13:33 ` Borislav Petkov
2015-12-27 13:40 ` Andy Lutomirski
2015-12-27 19:04 ` Dan Williams
2015-12-27 12:18 ` Andy Lutomirski
2015-12-30 23:32 ` Tony Luck
2015-12-31 20:30 ` Tony Luck
2015-12-31 21:22 ` Andy Lutomirski
2016-01-01 22:19 ` Tony Luck
2016-01-03 3:40 ` Andy Lutomirski
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=6c0b3214-f120-47ee-b7fe-677b4f27f039@email.android.com \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=elliott@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=tony.luck@gmail.com \
--cc=x86@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 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).