vchi: rename bitset macros to avoid collision with bitset(9)

[scottph]

Summary

An upcoming change to include bitset(9) macros from vm_page.h
causes a macro name collision with vchi's custom bitset macros.

This change was performed mechanically by:

sed -i .orig s/BITSET/VCHI_BITSET/g $(grep -rl BITSET sys/contrib/vchiq)

MFC after: 1 week
Sponsored by: Ampere Computing, Inc.

[emaste]

I wonder if we can upstream this too

[scottph]

In D26177#586533, @emaste wrote:

I wonder if we can upstream this too

It looks like upstream has moved pretty far in the years since this code was imported. I believe the diff is on the order of:

3702 insertions(+), 7735 deletions(-)

(Where the sys/contrib/vchi has around 14k lines). So I think unless someone plans to feed and water the import, getting the change upstream won't really be of any benefit to us.

[emaste]

In D26177#586700, @scottph wrote:

In D26177#586533, @emaste wrote:

I wonder if we can upstream this too

It looks like upstream has moved pretty far in the years since this code was imported. I believe the diff is on the order of:

3702 insertions(+), 7735 deletions(-)

(Where the sys/contrib/vchi has around 14k lines). So I think unless someone plans to feed and water the import, getting the change upstream won't really be of any benefit to us.

Sure. I mean it shouldn't hold up this change in our tree, just that it probably makes sense to do on general principle.