rnel.org
> Subject: Re: [PATCH] x86/mce: Always save severity in machine_check_poll
>
>
> Just forget the work scheduling - it is only a marginal implementation thing -
> you only want to say that we want to log the severity since we already have
> it.
> And the most impor
> -Original Message-
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Monday, June 19, 2017 12:49 PM
> To: Ghannam, Yazen
> Cc: linux-e...@vger.kernel.org; Tony Luck ;
> x...@kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] x86/mce:
On Fri, Jun 16, 2017 at 02:49:58PM +, Ghannam, Yazen wrote:
> The code block being removed here was added in the following commit to decide
> whether or not to schedule work.
>
> fa92c58 x86, mce: Support memory error recovery for both UCNA and Deferred
> error in machine_check_poll
Are you
On Fri, Jun 16, 2017 at 02:49:58PM +, Ghannam, Yazen wrote:
> The code block being removed here was added in the following commit to decide
> whether or not to schedule work.
>
> fa92c58 x86, mce: Support memory error recovery for both UCNA and Deferred
> error in machine_check_poll
Are you
l.org; Tony Luck <tony.l...@intel.com>;
> x...@kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] x86/mce: Always save severity in machine_check_poll
>
> On Mon, Jun 12, 2017 at 11:54:06AM -0500, Yazen Ghannam wrote:
> > From: Yazen Ghannam <yazen.ghan...@amd.com&g
nel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] x86/mce: Always save severity in machine_check_poll
>
> On Mon, Jun 12, 2017 at 11:54:06AM -0500, Yazen Ghannam wrote:
> > From: Yazen Ghannam
> >
> > Remove code that was used to decide whether to schedule work. T
On Mon, Jun 12, 2017 at 11:54:06AM -0500, Yazen Ghannam wrote:
> From: Yazen Ghannam
>
> Remove code that was used to decide whether to schedule work. The decision
???
I'm missing a *lot* of background in order to understand what that sentence
means.
--
Regards/Gruss,
On Mon, Jun 12, 2017 at 11:54:06AM -0500, Yazen Ghannam wrote:
> From: Yazen Ghannam
>
> Remove code that was used to decide whether to schedule work. The decision
???
I'm missing a *lot* of background in order to understand what that sentence
means.
--
Regards/Gruss,
Boris.
Good
tkov <b...@suse.de>;
> x...@kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] x86/mce: Always save severity in machine_check_poll
>
> On Mon, Jun 12, 2017 at 11:54:06AM -0500, Yazen Ghannam wrote:
> > - severity = mce_severity(, mca_cfg.tolerant,
ernel@vger.kernel.org
> Subject: Re: [PATCH] x86/mce: Always save severity in machine_check_poll
>
> On Mon, Jun 12, 2017 at 11:54:06AM -0500, Yazen Ghannam wrote:
> > - severity = mce_severity(, mca_cfg.tolerant, NULL, false);
> > -
> > -
On Mon, Jun 12, 2017 at 11:54:06AM -0500, Yazen Ghannam wrote:
> - severity = mce_severity(, mca_cfg.tolerant, NULL, false);
> -
> - if (severity == MCE_DEFERRED_SEVERITY &&
> mce_is_memory_error())
> - if (m.status & MCI_STATUS_ADDRV)
> -
On Mon, Jun 12, 2017 at 11:54:06AM -0500, Yazen Ghannam wrote:
> - severity = mce_severity(, mca_cfg.tolerant, NULL, false);
> -
> - if (severity == MCE_DEFERRED_SEVERITY &&
> mce_is_memory_error())
> - if (m.status & MCI_STATUS_ADDRV)
> -
From: Yazen Ghannam
Remove code that was used to decide whether to schedule work. The decision
to schedule work is made later, so this code is now only deciding if we
should save the error severity.
Save the severity since we have it, and let the notifier blocks decide if
From: Yazen Ghannam
Remove code that was used to decide whether to schedule work. The decision
to schedule work is made later, so this code is now only deciding if we
should save the error severity.
Save the severity since we have it, and let the notifier blocks decide if
they want to do
14 matches
Mail list logo