From: "Luck, Tony" <tony.luck@intel.com> To: Andy Lutomirski <luto@amacapital.net> Cc: Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>, "Andrew Morton" <akpm@linux-foundation.org>, Andy Lutomirski <luto@kernel.org>, "Williams, Dan J" <dan.j.williams@intel.com>, Robert <elliott@hpe.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-mm@kvack.org" <linux-mm@kvack.org>, linux-nvdimm <linux-nvdimm@ml01.01.org>, X86 ML <x86@kernel.org> Subject: RE: [PATCHV3 1/3] x86, ras: Add new infrastructure for machine check fixup tables Date: Wed, 16 Dec 2015 22:51:04 +0000 [thread overview] Message-ID: <3908561D78D1C84285E8C5FCA982C28F39F87180@ORSMSX114.amr.corp.intel.com> (raw) In-Reply-To: <CALCETrVHqi9ixUQbeN82T14CVom1N6QegSNR+r=jtjRgcfC0kg@mail.gmail.com> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="utf-8", Size: 912 bytes --] > Looks generally good. > > Reviewed-by: Andy Lutomirski <luto@kernel.org> You say that to part 1/3 ... what happens when you get to part 3/3 and you read my attempts at writing x86 assembly code? >> +#ifdef CONFIG_MCE_KERNEL_RECOVERY >> +int fixup_mcexception(struct pt_regs *regs) >> +{ >> + const struct exception_table_entry *fixup; >> + unsigned long new_ip; >> + >> + fixup = search_mcexception_tables(regs->ip); >> + if (fixup) { >> + new_ip = ex_fixup_addr(fixup); >> + >> + regs->ip = new_ip; > > You could very easily save a line of code here :) Two lines (the declaration of the variable can go away as well). Will include if we need a V4 when everyone else gets to commenting. -Tony ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
WARNING: multiple messages have this Message-ID (diff)
From: "Luck, Tony" <tony.luck@intel.com> To: Andy Lutomirski <luto@amacapital.net> Cc: Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>, Andrew Morton <akpm@linux-foundation.org>, Andy Lutomirski <luto@kernel.org>, "Williams, Dan J" <dan.j.williams@intel.com>, Robert <elliott@hpe.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "linux-mm@kvack.org" <linux-mm@kvack.org>, linux-nvdimm <linux-nvdimm@ml01.01.org>, X86 ML <x86@kernel.org> Subject: RE: [PATCHV3 1/3] x86, ras: Add new infrastructure for machine check fixup tables Date: Wed, 16 Dec 2015 22:51:04 +0000 [thread overview] Message-ID: <3908561D78D1C84285E8C5FCA982C28F39F87180@ORSMSX114.amr.corp.intel.com> (raw) In-Reply-To: <CALCETrVHqi9ixUQbeN82T14CVom1N6QegSNR+r=jtjRgcfC0kg@mail.gmail.com> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain; charset="utf-8", Size: 876 bytes --] > Looks generally good. > > Reviewed-by: Andy Lutomirski <luto@kernel.org> You say that to part 1/3 ... what happens when you get to part 3/3 and you read my attempts at writing x86 assembly code? >> +#ifdef CONFIG_MCE_KERNEL_RECOVERY >> +int fixup_mcexception(struct pt_regs *regs) >> +{ >> + const struct exception_table_entry *fixup; >> + unsigned long new_ip; >> + >> + fixup = search_mcexception_tables(regs->ip); >> + if (fixup) { >> + new_ip = ex_fixup_addr(fixup); >> + >> + regs->ip = new_ip; > > You could very easily save a line of code here :) Two lines (the declaration of the variable can go away as well). Will include if we need a V4 when everyone else gets to commenting. -Tony N§²æìr¸zǧu©²Æ {\béì¹»\x1c®&Þ)îÆi¢Ø^nr¶Ý¢j$½§$¢¸\x05¢¹¨è§~'.)îÄÃ,yèm¶ÿÃ\f%{±j+ðèצj)Z·
next prev parent reply other threads:[~2015-12-16 22:51 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-12-16 16:39 [PATCHV3 0/3] Machine check recovery when kernel accesses poison Tony Luck 2015-12-16 16:39 ` Tony Luck 2015-12-16 1:29 ` [PATCHV3 1/3] x86, ras: Add new infrastructure for machine check fixup tables Tony Luck 2015-12-16 1:29 ` Tony Luck 2015-12-16 17:55 ` Andy Lutomirski 2015-12-16 17:55 ` Andy Lutomirski 2015-12-16 22:51 ` Luck, Tony [this message] 2015-12-16 22:51 ` Luck, Tony 2015-12-17 16:22 ` Andy Lutomirski 2015-12-17 16:22 ` Andy Lutomirski 2015-12-21 18:18 ` Borislav Petkov 2015-12-21 18:18 ` Borislav Petkov 2015-12-21 19:16 ` Dan Williams 2015-12-21 19:16 ` Dan Williams 2015-12-21 20:15 ` Borislav Petkov 2015-12-21 20:15 ` Borislav Petkov 2015-12-22 11:13 ` Borislav Petkov 2015-12-22 11:13 ` Borislav Petkov 2015-12-16 1:29 ` [PATCHV3 2/3] x86, ras: Extend machine check recovery code to annotated ring0 areas Tony Luck 2015-12-16 1:29 ` Tony Luck 2015-12-22 11:14 ` Borislav Petkov 2015-12-22 11:14 ` Borislav Petkov 2015-12-16 1:30 ` [PATCHV3 3/3] x86, ras: Add mcsafe_memcpy() function to recover from machine checks Tony Luck 2015-12-16 1:30 ` Tony Luck 2015-12-22 11:13 ` Borislav Petkov 2015-12-22 11:13 ` Borislav Petkov 2015-12-22 19:38 ` Tony Luck 2015-12-22 19:38 ` Tony Luck 2015-12-23 12:58 ` Borislav Petkov 2015-12-23 12:58 ` Borislav Petkov 2015-12-23 19:31 ` Dan Williams 2015-12-23 19:31 ` Dan Williams 2015-12-23 20:46 ` Tony Luck 2015-12-23 20:46 ` Tony Luck 2015-12-24 13:37 ` Borislav Petkov 2015-12-24 13:37 ` Borislav Petkov
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=3908561D78D1C84285E8C5FCA982C28F39F87180@ORSMSX114.amr.corp.intel.com \ --to=tony.luck@intel.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=luto@kernel.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.