Date: Tue, 30 Apr 2019 09:24:25 -0600 From: Warner Losh <imp@bsdimp.com> To: Hans Petter Selasky <hps@selasky.org> Cc: Niclas Zeising <zeising@freebsd.org>, src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org> Subject: Re: svn commit: r346958 - head/sys/compat/linuxkpi/common/src Message-ID: <CANCZdfqV5BPcQx0iC7wpvttmvxwyfEkb7XQVrRMPp2Jk_bqYTQ@mail.gmail.com> In-Reply-To: <2f77d9f2-833d-f614-e193-a369086c01cf@selasky.org> References: <201904301041.x3UAfLvj054368@repo.freebsd.org> <8f360678-2df1-fe7b-cb83-f47923534826@freebsd.org> <2f77d9f2-833d-f614-e193-a369086c01cf@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 30, 2019 at 9:17 AM Hans Petter Selasky <hps@selasky.org> wrote: > On 4/30/19 3:10 PM, Niclas Zeising wrote: > > On 2019-04-30 12:41, Hans Petter Selasky wrote: > >> Author: hselasky > >> Date: Tue Apr 30 10:41:20 2019 > >> New Revision: 346958 > >> URL: https://svnweb.freebsd.org/changeset/base/346958 > >> > >> Log: > >> Reduce the number of mutexes after r346645 in the LinuxKPI. > >> Make function macro wrappers for locking and unlocking to ease > >> readability. > >> No functional change. > >> Discussed with: kib@, tychon@ and zeising@ > > > > I was not part of any discussion regarding this. If this is related to > > https://reviews.freebsd.org/D20097 I explicitly asked you on gitter to > > hold of for a bit, while we try to figure out why we are seeing > > regressions in graphics with the latest dmar changes. > > > > Can you please revert this since it colludes the dmar graphics issue, > > and it makes the suggested patch not apply cleanly, which makes it > > harder to get people to help test. > > Thank you! > > Regards > > In response to your request I've collected fixes for all the known > LinuxKPI+DMA issues at: > https://reviews.freebsd.org/D20097 > > It is based on top of the latest -current. > Hopefully this will solve the problem. Do you have any idea of when we might see resolution of this issue? I'd like to see it fixed by Friday either with fixes or a revert. Do you think that's a reasonable time frame? If not, what do you think a reasonable time frame will be? I know we have a number of unknowns to factor in, so my queries are based on our best guesses. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqV5BPcQx0iC7wpvttmvxwyfEkb7XQVrRMPp2Jk_bqYTQ>