Hi Wolfram,
On Wed, 16 Sept 2026 at 23:40, Wolfram Sang
<[email protected]> wrote:
> > > +static void *hwspin_lock_seq_next(struct seq_file *s, void *v, loff_t
> > > *ppos)
> > > +{
> > > + /* Increase ppos here to avoid endless loops. Don't use
> > > xa_find_after() */
> >
> > Do you mean xa_find_after() may loop forever?
>
> Ehrm, it's been a while, I need to look this up. Which means the comment
> is not explanationary enough :/
Yeah, I'd expect xa_find_after() to do exactly what you want...
> > > +static int hwspin_lock_seq_show(struct seq_file *s, void *v)
> > > +{
> > > + struct hwspinlock *hwlock = v;
> > > + bool unused = xa_get_mark(&hwspinlocks, s->index,
> > > HWSPINLOCK_UNUSED);
> > > +
> > > + seq_printf(s, "%4llu:\t%s\t%s\n", s->index, unused ? "free" : "in
> > > use",
> >
> > For easier parsing the output, you may want to use a string without
> > spaces, e.g. "busy", "active", ...
>
> I get the idea, but haven't found a nice word yet. "Busy" could be
> interpreted as "lock taken". I'll think some more about it.
"used", "bound", "unavailable", "occupied", "reserved", "in_use", "inuse", ...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
