The first thing that pops into my head is "aid in debugging". There
have
been several times where I've had related processes that should be in
the same pag and have the same credentials not be, and with some of
the
weirdness we've encountered it would be nice to have the actual pag
number so I could say "yes, both things are in the same pag[1],
something
else is going on" or "no, they are not in the same pag, find out what
caused that".
And as someone else has pointed out, I'm sure someone will think of
some reason to want the number. Why not have the interface return
the number?
uint32_t is too small to be temporal unique in a sane way, ie you get
to keep a list of them.
Representing pags as a number its a bad idea since that limit
implementation options. What is the OS have native support for PAGs
(or something kind of like it) but they are all internal and the
consumer cant know anything about them ?
Returning a number that might be unique is ok with me, but it should
not be the PAG number.
Love
