On Wed, Sep 4, 2019 at 7:14 PM Davidlohr Bueso <dave@xxxxxxxxxxxx> wrote: > On Wed, 04 Sep 2019, Daniel Vetter wrote: > >I'm also not sure whether we have a real problem here, it's just debug > >noise that we're fighting here? > > It is non stop debug noise as the memory range in question is being added + > deleted over and over. I doubt we want to be burning cycles like this. Yeah the proper fix is setting up an io_mapping in ttm (or drivers) so the pat tracking is cached, and then using the right pte wrangling functions. But that's a lot more involved fix, and from all the testing we've done the pte rewriting itself doesn't seem to be the biggest issue with mgag200 being slow ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
