sched_4bsd: rename runq to runq_global

[mchoo]

Summary

In upcoming changes, 'struct td_sched' will store CPU ID of the thread's
current runqueue instead of a pointer to the runqueue. This requires
functions to store pointer to the runqueue as a local variable. Although
the name 'runq' seams ideal for these local variables, it is already
taken by the global runqueue. Thus rename the global runqueue to
'runq_global' to hint the variable is the global runqueue and yield the
name 'runq' to local variables.

Suggested by: olce

[olce]

Looks much better like that. :-) "Suggested by: olce" appreciated.

Do you want me to commit that? Or can you with jhb@'s approval?

[mchoo]

Add Suggested by: olce

[mchoo]

In D58065#1331883, @olce wrote:

Do you want me to commit that? Or can you with jhb@'s approval?

Since I don't have commit bit yet, could you push it for me? Thanks:)

[olce]

In D58065#1332040, @minsoochoo0122_proton.me wrote:

Since I don't have commit bit yet, could you push it for me? Thanks:)

Sure. With the minsoo.io address I presume? Also, did you do some smoke test with this change (it is low risk, but still...)? I'll probably do some tomorrow before committing.

[mchoo]

In D58065#1332142, @olce wrote:

In D58065#1332040, @minsoochoo0122_proton.me wrote:

Since I don't have commit bit yet, could you push it for me? Thanks:)

Sure. With the minsoo.io address I presume?

Yes.

Also, did you do some smoke test with this change (it is low risk, but still...)? I'll probably do some tomorrow before committing.

My computer successfully booted and I can login with this patch and the D58000, but I haven't run any test suite. I would appreciate you a lot if you can do that for me.