Re: [PATCH v2] x86/mce/AMD: Use saved threshold block info in interrupt handler

2017-06-01 Thread Borislav Petkov
On Wed, May 31, 2017 at 09:11:55AM -0500, Yazen Ghannam wrote: > From: Yazen Ghannam > > In the amd_threshold_interrupt() handler, we loop through every possible > block in each bank and rediscover the block's address and if it's valid, > e.g. valid, counter present and

Re: [PATCH v2] x86/mce/AMD: Use saved threshold block info in interrupt handler

2017-06-01 Thread Borislav Petkov
On Wed, May 31, 2017 at 09:11:55AM -0500, Yazen Ghannam wrote: > From: Yazen Ghannam > > In the amd_threshold_interrupt() handler, we loop through every possible > block in each bank and rediscover the block's address and if it's valid, > e.g. valid, counter present and not locked. However, we

[PATCH v2] x86/mce/AMD: Use saved threshold block info in interrupt handler

2017-05-31 Thread Yazen Ghannam
From: Yazen Ghannam In the amd_threshold_interrupt() handler, we loop through every possible block in each bank and rediscover the block's address and if it's valid, e.g. valid, counter present and not locked. However, we already have the address saved in the threshold

[PATCH v2] x86/mce/AMD: Use saved threshold block info in interrupt handler

2017-05-31 Thread Yazen Ghannam
From: Yazen Ghannam In the amd_threshold_interrupt() handler, we loop through every possible block in each bank and rediscover the block's address and if it's valid, e.g. valid, counter present and not locked. However, we already have the address saved in the threshold blocks list for each CPU