Date: Sat, 1 Oct 2011 12:51:20 +0530 From: "Jayachandran C." <jchandra@freebsd.org> To: Adrian Chadd <adrian@freebsd.org> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r225892 - head/sys/mips/mips Message-ID: <CA%2B7sy7D6h5a08Q6yNfX6xSqwabDLzE5GLu5aV3fCMYQKn_4AoQ@mail.gmail.com> In-Reply-To: <CAJ-VmokAsDpjJLt%2BVJ2gDGX%2BiMAwZvL2TPaaAD_LRm-Yyquxig@mail.gmail.com> References: <201110010556.p915uQH6003016@svn.freebsd.org> <CA%2B7sy7BiRvTB79H9=y%2BS4jQ=%2BboW1bcDJn%2BBULMmJU9KLLVJ5A@mail.gmail.com> <CAJ-VmokAsDpjJLt%2BVJ2gDGX%2BiMAwZvL2TPaaAD_LRm-Yyquxig@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Sat, Oct 1, 2011 at 12:39 PM, Adrian Chadd <adrian@freebsd.org> wrote: > Reverting it unfortunately doesn't help; it messes up the event timer stuff. I would like to understand this, reverting r216862 would take out the critical_enter() and cpu_idleclock() which would keep the timer interrupts coming is as usual, this should not affect the event timer. > I'd like to see a more permanent solution. What I suggest we do moving > forward is: > > * create a function pointer setup, like what i386 does > * override it per-platform and per-chipset, once we know what the > correct behaviour should be. > > Are you able to figure out how to achieve correct timer/interrupt/wait > handling on XLR? I'm not aware of any platforms which provide an equivalent of 'sti', so going for an implementation per platform may not help. JC.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B7sy7D6h5a08Q6yNfX6xSqwabDLzE5GLu5aV3fCMYQKn_4AoQ>