dyndbg: try DEFINE_DYNAMIC_DEBUG_TABLE

Test DEFINE_DYNAMIC_DEBUG_TABLE, in i915.ko, by adding an invocation
into i915_drv.c, the 1st object built in the Makefile.  This does
manually what can perhaps be done transparently in headers (hopefully).

DEFINE_DYNAMIC_DEBUG_TABLE is based on DEFINE_DYNAMIC_DEBUG_METADATA;
just like its model, it creates a pair of structs: _ddebug &
_ddebug_callsite, and inits them with format="0000", lineno=0.

This:
- identifies it clearly in control output
- appears to place it 1st in the section(s)
  it works here, at least for modprobed module
  1st-to-build might be the real reason for the sort.

drivers/gpu/drm/i915/i915_drv.c:0 [i915](null) =_ "0000"
drivers/gpu/drm/i915/gvt/gvt.c:437 [i915]intel_gvt_register_hypervisor =_ "gvt: core: Running with hypervisor %s
drivers/gpu/drm/i915/gvt/gvt.c:378 [i915]intel_gvt_init_device =_ "gvt: core: gvt device initialization is done\0

other big diff between DEFINE_DYNAMIC_DEBUG_TABLE/_METADATA:
- not static decls.
  removing static made the line appear in control output (below).
  (cuz it might be reffd elsewhere, so its linked).
  we want this.

  it also needs to be visible where DEFINE_DYNAMIC_DEBUG_METADATA is
  used, so it can be used to initialize .module_index, ie in many other
  objects where pr_debugs are coded.

A peek inside i915_drv.o looks about right; i915_site is expected at least.

Relocation section '.rela__dyndbg' at offset 0x6f48 contains 2 entries:
  Offset          Info           Type           Sym. Value    Sym. Name + Addend
000000000010  014c00000001 R_X86_64_64       0000000000000000 i915_site + 0
000000000018  001a00000001 R_X86_64_64       0000000000000000 .rodata.str1.1 + 548

Relocation section '.rela__dyndbg_callsites' at offset 0x6f90 contains 2 entries:
  Offset          Info           Type           Sym. Value    Sym. Name + Addend
000000000000  001a00000001 R_X86_64_64       0000000000000000 .rodata.str1.1 + d8
000000000008  000a00000001 R_X86_64_64       0000000000000000 .rodata.str1.8 + 110

Signed-off-by: Jim Cromie <jim.cromie@gmail.com>

drivers/gpu/drm/i915/i915_drv.c

@@ -88,6 +88,9 @@
 
 static struct drm_driver driver;
 
+DEFINE_DYNAMIC_DEBUG_TABLE(i915);
+// DEFINE_DYNAMIC_DEBUG_TABLE(THIS_MODULE);  // one alternative form
+
 static int i915_get_bridge_dev(struct drm_i915_private *dev_priv)
 {
 	int domain = pci_domain_nr(dev_priv->drm.pdev->bus);

include/linux/dynamic_debug.h

@@ -102,6 +102,36 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor,
 			 const struct ib_device *ibdev,
 			 const char *fmt, ...);
 
+/** DEFINE_DYNAMIC_DEBUG_TABLE(module)
+ *
+ * This is an analogue to DEFINE_DYNAMIC_DEBUG_METADATA()
+
+ * It's just a "callsite" whose primary purpose is to create or
+ * reserve the 0th element pair in our sub-vectors of __dyndbg[] &
+ * __dyndbg_callsites[].  The format & lineno are set to sort 1st,
+ * though I suspect our good order is more about linkage.  Either way,
+ * the TABLE is appearing 1st in control's i915 output.
+
+ * We want to use it to initialize .module_index, but I was unable to
+ * ref &module##_base by any construct I thought to try;
+ * KBUILD_MODNAME in particular didnt work.
+
+ */
+
+#define DEFINE_DYNAMIC_DEBUG_TABLE(module)		       	\
+	struct _ddebug_callsite  __aligned(8)		\
+	__section("__dyndbg_callsites") module##_site = {	\
+		.modname = KBUILD_MODNAME,			\
+		.filename = __FILE__,				\
+		.function = NULL,				\
+	};							\
+	struct _ddebug  __aligned(8)			\
+	__section("__dyndbg") module##_base = {			\
+		.site = &module##_site,				\
+		.format = "0000",			       	\
+		.lineno = 0, /* sort on mod, line */		\
+	}
+
 #define DEFINE_DYNAMIC_DEBUG_METADATA(name, fmt)		\
 	static struct _ddebug_callsite  __aligned(8)		\
 	__section("__dyndbg_callsites") name##_site = {		\
@@ -115,23 +145,10 @@ void __dynamic_ibdev_dbg(struct _ddebug *descriptor,
 		.format = (fmt),				\
 		.lineno = __LINE__,				\
 		.flags = _DPRINTK_FLAGS_DEFAULT,		\
-		_DPRINTK_KEY_INIT				\
+		_DPRINTK_KEY_INIT,				\
+		.module_index = 0 /* want offset from _base */	\
 	}
 
-/** DEFINE_DYNAMIC_DEBUG_TABLE(module) 
-
- * It's just a "callsite" we expect not to use, except as a 0th
- * element we can use to initialize each ddebug.module_index.
- * 
- * Later, this will be adapted to initialize a pair of alternate
- * structures; analogous to structs _ddebug & _ddebug_callsite, and
- * implemented as structs unionized with them.  This pair of
- * alt-structs could supplant most or all of the function and purpose
- * of the linked list of ddebug_tables built by ddebug_add_module.
- */
-#define DEFINE_DYNAMIC_DEBUG_TABLE(module) \
-	DEFINE_DYNAMIC_DEBUG_METADATA(module, "00-1st-in-subsection")
-
 #ifdef CONFIG_JUMP_LABEL
 
 #ifdef DEBUG