Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1290963
| From | Ingo Molnar <mingo@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCHV2 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks |
| Date | 2015-12-14 09:40 +0100 |
| Message-ID | <qFwPN-3DO-43@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <qEEmm-21X-25@gated-at.bofh.it> <qEEw1-261-3@gated-at.bofh.it> <qEEw1-261-1@gated-at.bofh.it> <qEEFI-29G-23@gated-at.bofh.it> <qEEPo-2db-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
* Andy Lutomirski <luto@amacapital.net> wrote: > I still think it would be better if you get rid of BIT(63) and use a > pair of landing pads, though. They could be as simple as: > > .Lpage_fault_goes_here: > xorq %rax, %rax > jmp .Lbad > > .Lmce_goes_here: > /* set high bit of rax or whatever */ > /* fall through */ > > .Lbad: > /* deal with it */ > > That way the magic is isolated to the function that needs the magic. Seconded - this is the usual pattern we use in all assembly functions. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCHV2 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks Ingo Molnar <mingo@kernel.org> - 2015-12-14 09:40 +0100
Re: [PATCHV2 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks "Luck, Tony" <tony.luck@intel.com> - 2015-12-14 20:50 +0100
Re: [PATCHV2 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks Andy Lutomirski <luto@amacapital.net> - 2015-12-14 21:20 +0100
csiph-web