From: Tony Luck <tony.luck@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Borislav Petkov <bp@alien8.de>,
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: Thu, 31 Dec 2015 12:30:42 -0800 [thread overview]
Message-ID: <CA+8MBb+MaZUK1vMPNwUchZJed0Fi3vh9_vFP2OoPZsUMoDO=ZQ@mail.gmail.com> (raw)
In-Reply-To: <CA+8MBbK842Ov74ZSU_fmxoZNw_72J+3hg3KQ4C5aBjd_cDYfAA@mail.gmail.com>
On Wed, Dec 30, 2015 at 3:32 PM, Tony Luck <tony.luck@gmail.com> wrote:
> Fifth is just a hack because I clearly didn't understand what I was
> doing in parts 2&3 because my new class shows up as '3' not '1'!
>
> Andy: Can you explain the assembler/linker arithmetic for the class?
Never mind ... figured it out.
The fixup entry in the extable is:
label - . + 0x2000000 - BIAS
The "label - ." part evaluates to a smallish negative value (because
the .fixup section is bundled in towards the end of .text, and the
ex_table section comes right after.
Then you add 0x20000000 to get a positive number, then *subtract*
the BIAS. I'd picked BIAS = 0x40000000 thinking that would show
up directly in class bits. But 0x1ffff000 - 0x40000000 is 0xdffff000
so bits 31 & 31 are both set, and this is class3
I switched to BIAS 0xC0000000 ... and now I get class 1 entries
(bit31=0, bit30=1).
New patch series coming soon.
-Tony
--
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:[~2015-12-31 20:30 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
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 [this message]
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='CA+8MBb+MaZUK1vMPNwUchZJed0Fi3vh9_vFP2OoPZsUMoDO=ZQ@mail.gmail.com' \
--to=tony.luck@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--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=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).