From nobody Wed Jun 29 18:27:21 2022 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id AD4F787CB64 for ; Wed, 29 Jun 2022 18:27:39 +0000 (UTC) (envelope-from jake@technologyfriends.net) Received: from mail-qv1-xf33.google.com (mail-qv1-xf33.google.com [IPv6:2607:f8b0:4864:20::f33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LY91R0bhgz4Zlh for ; Wed, 29 Jun 2022 18:27:39 +0000 (UTC) (envelope-from jake@technologyfriends.net) Received: by mail-qv1-xf33.google.com with SMTP id n15so26055056qvh.12 for ; Wed, 29 Jun 2022 11:27:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=technologyfriends.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PkF5lQ/zQRVeZF1PnQhMN7b3bjPSEHJh83NEWz1U1dc=; b=DR6xLZF5ViHJAhFxk53T2lh5cu7oKEnlEgx8qm/teo2/IRpf3bT4xlxhAbhDMy2xuK Zwxo5dGHU2fKFvyBYzDCewXsP/mr2HErFnRloM35kgO0qbUu6TlNwhwK7hg9R5juZnyl rd5FGo0NAO8rgvl2bOuNP82TtuNKmEJ1aUESKTm1ucTZBPp0BjKnh1f2e9KK8nFQw63u +8hyrv9OJLEPCyc7HctKpT1katzoB6xiE/fGE8+umNNc8ccU+xDQeJHV0sInWVihfrZT LOCb0GWOmg5/1eo2okUhinZjD3HVicgO0EIj+6f7sJwbq9AVo6tzSTV/OwZjn6KxmEb0 jBjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PkF5lQ/zQRVeZF1PnQhMN7b3bjPSEHJh83NEWz1U1dc=; b=2GVFKfLKBiDrNfEy9NnoIFzR/T6OnVoy4mKT9K1X65cg1HM2vR99N2MOVTvZNnPFM9 bMG9wYdI4QPC/Jnz9w44aStvOFnfMEe8vDsJ8btAr+JKZrPLZ1y2sk/e9+U9ZgIzEzRE dnGubKVZDo1yQWN09HeNZW054b07JLxTrnRiIcL54CwOHH9Bu/EOsvIJ/yyKdvFhtG/E smeu6jIvcVNynR9Z4oXcPkwCYZqx86C0pIB6ksPSSJqKnTzi7Egk3H/dL9HRf9OfZinp 97x8AoM5R4CEmL/+Cpm0mQXqwI2bOa9l2DI3QYg3J3O2hUDVoDvlL80SyC1Znz/XarPa BRUg== X-Gm-Message-State: AJIora8P8+uFTVEcCcvIMahPIB/BUbUnNczPA0w8ZI1sey/R/2MQyLI1 SKe/e7eaOVBQVfjqLVNxNqx3q/bLevNQ9JSggwgoXA== X-Google-Smtp-Source: AGRyM1sNFbmXewdvaZk30GnUlmJF1gSiuP/mvopVl2vNZZ6QJvSEBfhxGjJ+QQDKfjNzR9az/B79cRcf7gHauIpmLrw= X-Received: by 2002:a05:622a:180b:b0:31a:dd36:3c16 with SMTP id t11-20020a05622a180b00b0031add363c16mr3907645qtc.236.1656527251754; Wed, 29 Jun 2022 11:27:31 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Jake Freeland Date: Wed, 29 Jun 2022 13:27:21 -0500 Message-ID: Subject: Re: LinuxKPI debugfs Port To: Mark Johnston Cc: freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="00000000000066e56b05e29a4eb5" X-Rspamd-Queue-Id: 4LY91R0bhgz4Zlh X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none ("invalid DKIM record") header.d=technologyfriends.net header.s=google header.b=DR6xLZF5; dmarc=none; spf=none (mx1.freebsd.org: domain of jake@technologyfriends.net has no SPF policy when checking 2607:f8b0:4864:20::f33) smtp.mailfrom=jake@technologyfriends.net X-Spamd-Result: default: False [-3.10 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[jake]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; DMARC_NA(0.00)[technologyfriends.net]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[technologyfriends.net:~]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::f33:from]; NEURAL_HAM_SHORT(-1.00)[-1.000]; R_DKIM_PERMFAIL(0.00)[technologyfriends.net:s=google]; MLMMJ_DEST(0.00)[freebsd-hackers]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --00000000000066e56b05e29a4eb5 Content-Type: text/plain; charset="UTF-8" Mark, I was able to get Manu's attention and schedule a meeting with him to discuss this. I just finished and he was able to confirm that you're pointing me in the right direction. I greatly appreciate your guidance and help. I plan to finish this project and hopefully have enough knowledge, with the help of peers, to write informative LinuxKPI and lindebugfs man pages. Thank you again, Jake Freeland On Wed, Jun 29, 2022 at 8:51 AM Mark Johnston wrote: > On Tue, Jun 28, 2022 at 05:11:49PM -0500, Jake Freeland wrote: > > Mark, > > > > Your reply clears up a lot. I just forked drm-kmod, applied your Makefile > > patch, and added DEBUGFS to kconfig.mk. I am extremely excited to be > > back on track, especially now that I know how to proceed. > > > > Just to clarify, my job is to extend the current debugfs implementation > > (debugfs.h and lindebugfs.c) to include the missing functionality > required > > for i915kms to compile and run successfully? I would ask manu@, but > > he has not responded to me in weeks. > > I think so, yes. That's the shortest path to getting i915's debugfs > files available for consumption by the test suite. > > > I greatly appreciate your explanations about LinuxKPI and lindebugfs. > > Extensive documentation is what draws me to FreeBSD, but I struggled > > to find any information regarding lindebugfs or LinuxKPI. I plan to write > > some of my own when I am done with this project to help others in my > > position :). > > That'd be welcome. This area is definitely under-documented, though it > can be difficult to write useful documentation targeting kernel > developers. A man page for lindebugfs would be a great start, as would > an introductory page for the linuxkpi. > --00000000000066e56b05e29a4eb5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Mark,

I was able to get Manu's atte= ntion and schedule a meeting with
him to discuss=C2=A0this. I jus= t finished and he was able to confirm that
you're pointing=C2= =A0me in the right direction. I greatly appreciate your
guidance = and help.

I plan to finish this project and hopefu= lly=C2=A0have enough knowledge,
with the help of peers, to write = informative LinuxKPI and lindebugfs
man pages.

Thank you again,
Jake Freeland

On Wed, Jun 29, 2022= at 8:51 AM Mark Johnston <markj@fr= eebsd.org> wrote:
On Tue, Jun 28, 2022 at 05:11:49PM -0500, Jake Freeland wrote: > Mark,
>
> Your reply clears up a lot. I just forked drm-kmod, applied your Makef= ile
> patch, and added DEBUGFS to kconfig.mk. I am extremely excited to be
> back on track, especially now that I know how to proceed.
>
> Just to clarify, my job is to extend the current debugfs implementatio= n
> (debugfs.h and lindebugfs.c) to include the missing functionality requ= ired
> for i915kms to compile and run successfully? I would ask manu@, but > he has not responded to me in weeks.

I think so, yes.=C2=A0 That's the shortest path to getting i915's d= ebugfs
files available for consumption by the test suite.

> I greatly appreciate your explanations about LinuxKPI and lindebugfs.<= br> > Extensive documentation is what draws me to FreeBSD, but I struggled > to find any information regarding lindebugfs or LinuxKPI. I plan to wr= ite
> some of my own when I am done with this project to help others in my > position :).

That'd be welcome.=C2=A0 This area is definitely under-documented, thou= gh it
can be difficult to write useful documentation targeting kernel
developers.=C2=A0 A man page for lindebugfs would be a great start, as woul= d
an introductory page for the linuxkpi.
--00000000000066e56b05e29a4eb5--