From: Borislav Petkov <bp@alien8.de>
To: Chen Yucong <slaoub@gmail.com>
Cc: Tony Luck <tony.luck@gmail.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86, MCE, AMD: move invariant code out from loop body
Date: Mon, 6 Oct 2014 23:27:07 +0200 [thread overview]
Message-ID: <20141006212707.GH20739@pd.tnic> (raw)
In-Reply-To: <1412263212.8085.6.camel@debian>
On Thu, Oct 02, 2014 at 11:20:12PM +0800, Chen Yucong wrote:
> From: Chen Yucong <slaoub@gmail.com>
> Subject: [PATCH] x86, MCE, AMD: move invariant code out from loop body
>
> "mce_threshold_vector = amd_threshold_interrupt;" is loop invariant code
> in mce_amd_feature_init(). So it should be moved out from loop body.
>
> Signed-off-by: Chen Yucong <slaoub@gmail.com>
> ---
> arch/x86/kernel/cpu/mcheck/mce_amd.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/cpu/mcheck/mce_amd.c b/arch/x86/kernel/cpu/mcheck/mce_amd.c
> index 5d4999f..f727701 100644
> --- a/arch/x86/kernel/cpu/mcheck/mce_amd.c
> +++ b/arch/x86/kernel/cpu/mcheck/mce_amd.c
> @@ -253,9 +253,10 @@ void mce_amd_feature_init(struct cpuinfo_x86 *c)
> }
>
> mce_threshold_block_init(&b, offset);
> - mce_threshold_vector = amd_threshold_interrupt;
> }
> }
> +
> + mce_threshold_vector = amd_threshold_interrupt;
Looking at this more, it is theoretically possible that we break out
of the both loops without *any* thresholding registers detected and to
still assign a thresholding interrupt vector which would be clearly
wrong.
Thus I think something like below should be much safer (I tried it with
a label and goto already but it is uglier):
diff --git a/arch/x86/kernel/cpu/mcheck/mce_amd.c b/arch/x86/kernel/cpu/mcheck/mce_amd.c
index 9ce64955559d..9af7bd74828b 100644
--- a/arch/x86/kernel/cpu/mcheck/mce_amd.c
+++ b/arch/x86/kernel/cpu/mcheck/mce_amd.c
@@ -253,7 +253,9 @@ void mce_amd_feature_init(struct cpuinfo_x86 *c)
}
mce_threshold_block_init(&b, offset);
- mce_threshold_vector = amd_threshold_interrupt;
+
+ if (mce_threshold_vector != amd_threshold_interrupt)
+ mce_threshold_vector = amd_threshold_interrupt;
}
}
}
Looking at the asm, we still go and fetch those addresses so not really
a win:
cmpq $amd_threshold_interrupt, mce_threshold_vector(%rip) #, mce_threshold_vector
je .L235 #,
incl %r13d # block
movq $amd_threshold_interrupt, mce_threshold_vector(%rip) #, mce_threshold_vector
cmpl $9, %r13d #, block
but this way the code is relatively clean. Unless you can come up with
a nicer, cleaner version to handle the breaking out in the success and
failure case...
Hmmm.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-10-06 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1411377812.1917.112.camel@cyc>
[not found] ` <20140922191100.GC4709@pd.tnic>
[not found] ` <20141002143819.GE16452@pd.tnic>
2014-10-02 15:20 ` [PATCH] x86, MCE, AMD: move invariant code out from loop body Chen Yucong
2014-10-06 21:27 ` Borislav Petkov [this message]
2014-10-07 6:08 ` Chen Yucong
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=20141006212707.GH20739@pd.tnic \
--to=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slaoub@gmail.com \
--cc=tony.luck@gmail.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