> On Nov 18, 2018, at 11:00 AM, Martin Husemann <mar...@duskware.de> wrote: > > On Sun, Nov 18, 2018 at 04:19:50PM +0530, Cherry G.Mathew wrote: >> Typo: >> https://mail-index.netbsd.org/source-changes/2018/11/18/msg100702.html > > Ugh - can't you just modify > > CLKF_USERMODE(frame) > CLKF_PC(frame) > CLKF_INTR(frame) > > for xen making them ignore their frame argument and use the per-cpu cached > (but more minimal) data instead? +1 In addition to "we shouldn't even have this hardclock() interrupt anyway", it also makes the signature of hardclock() "not like a regular interrupt handler". -- thorpej
- Time accounting on statclock() Cherry G. Mathew
- Re: Time accounting on statclock() Cherry G. Mathew
- re: Time accounting on statclock() matthew green
- Re: Time accounting on statclock() Cherry G . Mathew
- Re: Time accounting on statclock() Mathew, Cherry G.
- API change request. Was => Re: Time accounti... Cherry G . Mathew
- Re: API change request. Was => Re: Time ... Cherry G . Mathew
- Re: API change request. Was => Re: T... Cherry G . Mathew
- Re: API change request. Was => ... Martin Husemann
- Re: API change request. Was =&... Cherry G . Mathew
- Re: API change request. Was =&... Jason Thorpe
- Re: API change request. Wa... Cherry G . Mathew
- Re: API change request. Was =&... Cherry G . Mathew