All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-edac <linux-edac@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] EDAC, mce_amd_inj: Set MISCV on injection
Date: Wed, 10 Jun 2015 11:30:42 -0500	[thread overview]
Message-ID: <55786632.9020701@amd.com> (raw)
In-Reply-To: <1433950426-10084-3-git-send-email-bp@alien8.de>

On 6/10/2015 10:33 AM, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
>
> When during injection we populate MCi_MISC by writing into misc, we need
> to set the MiscV bit in the corresponding MCi_STATUS register which
> denotes that there's valid info in the MCi_MISC register.
>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> ---
>   drivers/edac/mce_amd_inj.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/drivers/edac/mce_amd_inj.c b/drivers/edac/mce_amd_inj.c
> index 5001d166f54f..021f256b7f11 100644
> --- a/drivers/edac/mce_amd_inj.c
> +++ b/drivers/edac/mce_amd_inj.c
> @@ -248,6 +248,9 @@ static void do_inject(void)
>   	unsigned int cpu = i_mce.extcpu;
>   	u8 b = i_mce.bank;
>   
> +	if (i_mce.misc)
> +		i_mce.status |= MCI_STATUS_MISCV;
> +
>   	if (inj_type == SW_INJ) {
>   		amd_decode_mce(NULL, 0, &i_mce);
>   		return;


Thanks for the catch here and on Patch 2:)

Looks good to me. So you can slap a <Reviewed-by>  on them if needed..

Thanks,
-Aravind.

  reply	other threads:[~2015-06-10 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10 15:33 [PATCH 1/3] EDAC, mce_amd_inj: Cleanup and simplify README Borislav Petkov
2015-06-10 15:33 ` [PATCH 2/3] EDAC, mce_amd_inj: Move bit preparations before the injection Borislav Petkov
2015-06-10 15:33 ` [PATCH 3/3] EDAC, mce_amd_inj: Set MISCV on injection Borislav Petkov
2015-06-10 16:30   ` Aravind Gopalakrishnan [this message]
2015-06-10 16:51     ` Borislav Petkov
2015-06-13 14:11       ` 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=55786632.9020701@amd.com \
    --to=aravind.gopalakrishnan@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.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 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.