Re: kern/59165: vio9p(4): expose tag through sysctl or device properties

["Ryota Ozaki via gnats" <gnats-admin%NetBSD.org@localhost>]

The following reply was made to PR kern/59165; it has been noted by GNATS.

From: Ryota Ozaki <ozaki-r%netbsd.org@localhost>
To: Christoph Badura <bad%bsd.de@localhost>
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: kern/59165: vio9p(4): expose tag through sysctl or device properties
Date: Thu, 17 Apr 2025 12:40:58 +0900

 On Thu, Apr 10, 2025 at 2:38=E2=80=AFAM Christoph Badura <bad%bsd.de@localhost> wrote=
 :
 >
 > Darn, I wanted to reply earlier.
 >
 > On Tue, Mar 25, 2025 at 04:46:28PM +0900, Ryota Ozaki wrote:
 > > That reminds me of a RESTful API that requires listing up available end=
 points.
 >
 > I was reminded of SNMP.
 >
 > > I agree with the demand for discoverability, but in this case (sysctl
 > > MIBs) I don't
 > > desire it so much because, as you said, we can know the existing of sys=
 ctl MIBs
 > > by using grep, etc. The proposed MIB design may help to make scripts si=
 mple,
 > > but I'm not sure if it's essential for everyone.
 >
 > That's fine for scripts that run infrequently.  But it doesn't really wor=
 k
 > for stuff like systat or node_exporter which would query the MIB
 > frequently.
 >
 > But we can address that later if the need arrives.
 
 Okay, I've prepared another patch that adds intermediate node, hw.vio9p,
 so I think it allows us to do further work on it:
   https://www.netbsd.org/~ozaki-r/vio9p-tag-sysctl.v3.patch
 
 BTW, with the new patch, sysctl hw.vio9p iterates available nodes of
 vio9p devices:
   kvm# sysctl hw.vio9p
   hw.vio9p.vio9p0.tag =3D test
   hw.vio9p.vio9p1.tag =3D test2
 
 Does this behavior just satisfy your demand?
 
   ozaki-r