search for: raisins

On Tue, Sep 18, 2018 at 12:41:57PM +0200, Thomas Gleixner wrote: > On Tue, 18 Sep 2018, Thomas Gleixner wrote: > > On Tue, 18 Sep 2018, Thomas Gleixner wrote: > > > On Tue, 18 Sep 2018, Peter Zijlstra wrote: > > > > > Your memory serves you right. That's indeed observable on CPUs which > > > > > lack TSC_ADJUST. > > > > > >

On Tue, Sep 18, 2018 at 12:41:57PM +0200, Thomas Gleixner wrote: > On Tue, 18 Sep 2018, Thomas Gleixner wrote: > > On Tue, 18 Sep 2018, Thomas Gleixner wrote: > > > On Tue, 18 Sep 2018, Peter Zijlstra wrote: > > > > > Your memory serves you right. That's indeed observable on CPUs which > > > > > lack TSC_ADJUST. > > > > > >

...but only if there's actual interest in integrating things... I'm also a bit confused about RTDyldObjectLinkingLayer's notify integration. NotifyLoadedFtor is a class template parameter, but NotifyFinalizedFtor is just a std::function defaulting to empty? Is that just for historical raisins, or is there a deeper reason? To be able to use existing JITEventListeners - it'd surely be a shame to have to rewrite them anew - in custom stacks it also appears that there's no easy way to call JITEventListener->NotifyFreeingObject() - the to-be-freed objects aren't readily avai...

On Tue, 18 Sep 2018, Thomas Gleixner wrote: > So if the TSC on CPU1 is slightly behind the TSC on CPU0 then now1 can be > smaller than cycle_last. The TSC sync stuff does not catch the small delta > for unknown raisins. I'll go and find that machine and test that again. Of course it does not trigger anymore. We accumulated code between the point in timekeeping_advance() where the TSC is read and the update of the VDSO data. I'll might have to get an 2.6ish kernel booted on that machine and try with that...

Again no apparent explanation for the split except hysterical raisins. Merging them also makes it a bit more obviuos what's going on wrt the runtime pm refdancing. Cc: Ben Skeggs <bskeggs at redhat.com> Cc: nouveau at lists.freedesktop.org Signed-off-by: Daniel Vetter <daniel.vetter at intel.com> --- drivers/gpu/drm/nouveau/nouveau_drm.c | 9 +------...

Again no apparent explanation for the split except hysterical raisins. Merging them also makes it a bit more obviuos what's going on wrt the runtime pm refdancing. Cc: Ben Skeggs <bskeggs at redhat.com> Cc: nouveau at lists.freedesktop.org Reviewed-by: Sean Paul <seanpaul at chromium.org> Reviewed-by: Liviu Dudau <Liviu.Dudau at arm.com> Signed...

...gtod->seq++; gtod->cycle_last = tk->cycle_last; ... gtod->seq++; seq_begin(gtod->seq); now1 = rdtsc_ordered(); So if the TSC on CPU1 is slightly behind the TSC on CPU0 then now1 can be smaller than cycle_last. The TSC sync stuff does not catch the small delta for unknown raisins. I'll go and find that machine and test that again. Thanks, tglx

Well, we're figure the board's got problems, but I installed OpenIPMI a couple weeks ago, and fired it up as a service, then added a cron job. That all ran well until last evening; we came in to find 5 zillion emails complaining Unable to open SDR for reading I worked my way through logs, and googling, and then trying to run ipmitool by hand, and it complains there's no such device as

On Wed, April 19, 2017 16:22, Chris Murphy wrote: > > Apple has had massively disruptive changes on OS X and iOS. Windows > has had a fairly disruptive set of changes in Windows 10. About the > only things that don't change are industrial OS's. > I have no idea how this reference applies to my earlier post. We do not use Apple or Windows servers and the desktop

...ile I honestly wanted to see it turn 20, it was time (power supply glitches caused by overheating of the power supply; worst-case for hard disk death in my experience). Yeah, 24x7 operation for 19 years with minimal downtime. I'm going to personally put it back into service for hysterical raisins, since the VA-503+ board doesn't need re-cap and it runs very well for what it is. I'm not sure what I'm going to run on it yet. (It will be in service for the same reasons I'm going to put a Reh CPU280 running UZI280 into service.....). > And that?s why I use *all* the m...