On Fri, Mar 29, 2024 at 11:22:32AM -0700, Dan Williams wrote: > Alison Schofield wrote: > [..] > > Upon receipt of that new poison list, call memory_failture_queue() > > on *any* poison in a mapped space. Is that OK? Can we call > > memory_failure_queue() on any and every poison report that is in > > HPA space regardless of whether it first came to us through a GMER? > > I'm actually wondering if that is going to be the next ask anyway - > > ie report all poison. > > memory_failure_queue() should be called on poison creation events. Leave > the MF_ACTION_REQUIRED flag not set so that memory_failure() performs > "action optional" handling. So I would expect memory_failure_queue() > notification for GMER events, but not on poison list events.
Seems I totally missed the point of this patch set. Is it's only purpose to make sure that poison that is injected gets reported to memory_failure? So this single patch only: 1. Poison inject leads to this GMER/CXL_EVENT_TRANSACTION_INJECT_POISON 2. Driver sees GMER/CXL_EVENT_TRANSACTION_INJECT_POISON and reads poison list to get accurate length. 3. Driver reports that to memory_failure_queue() Still expect there's some code sharing opportunities and I still wonder about what is next in this area. --Alison
