On Mon, Jun 11, 2018 at 7:56 AM, Michal Hocko <mhocko@xxxxxxxxxx> wrote: > On Mon 11-06-18 07:44:39, Dan Williams wrote: > [...] >> I'm still trying to understand the next level of detail on where you >> think the design should go next? Is it just the HWPoison page flag? >> Are you concerned about supporting greater than PAGE_SIZE poison? > > I simply do not want to check for HWPoison at zillion of places and have > each type of page to have some special handling which can get wrong very > easily. I am not clear on details here, this is something for users of > hwpoison to define what is the reasonable scenarios when the feature is > useful and turn that into a feature list that can be actually turned > into a design document. See the different from let's put some more on > top approach... > So you want me to pay the toll of writing a design document justifying all the existing use cases of HWPoison before we fix the DAX bugs, and the design document may or may not result in any substantive change to these patches? Naoya or Andi, can you chime in here?
