> Martin Pieuchot schreef op 2017-12-01 15:36:
> > sparc64 uses a different name of storing the CPU number. I'd like to
> > use `ci_cpuid' to be able to use it in MI code without adding another
> > abstraction layer.
> >
> > Diff below is just a rename, ok?
>
> ok kettenis@
OK with me also. Wh
> sparc64 uses a different name of storing the CPU number. I'd like to
> use `ci_cpuid' to be able to use it in MI code without adding another
> abstraction layer.
Isn't that what CPU_INFO_UNIT() is for?
Martin Pieuchot schreef op 2017-12-01 15:36:
sparc64 uses a different name of storing the CPU number. I'd like to
use `ci_cpuid' to be able to use it in MI code without adding another
abstraction layer.
Diff below is just a rename, ok?
ok kettenis@
Index: include/cpu.h
=
sparc64 uses a different name of storing the CPU number. I'd like to
use `ci_cpuid' to be able to use it in MI code without adding another
abstraction layer.
Diff below is just a rename, ok?
Index: include/cpu.h
===
RCS file: /cvs/s