Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Francois Dugast <francois.dugast@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Cc: "Roper, Matthew D" <matthew.d.roper@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH] drm/xe/uapi: Remove MMIO ioctl
Date: Thu, 14 Sep 2023 11:43:47 +0300	[thread overview]
Message-ID: <87edj1w3ek.fsf@intel.com> (raw)
In-Reply-To: <ZQG_erefoFhzg6sd@fdugast-desk.home>

On Wed, 13 Sep 2023, Francois Dugast <francois.dugast@intel.com> wrote:
> On Tue, Sep 12, 2023 at 09:42:41AM -0500, Lucas De Marchi wrote:
>> On Tue, Sep 12, 2023 at 03:43:06AM -0500, Ofir Bitton wrote:
>> > Hey Matt, I totally undesrstand your concern, I might have another
>> > suggestion. We can create another FD in debugfs and move this ioctl
>> > there (I can take ownership on this), This way ABI is not an issue.
>> 
>> an interface in debugfs would be better than keeping the ioctl.

A regular debugfs interface, or an ioctl on a debugfs file? [1]

[1] https://lore.kernel.org/r/87h6nxw3rl.fsf@intel.com

>> We seem to have some consensus now to go ahead and remove this.
>> 
>> 	Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
>> 
>> Please record the Acked-by from UMD when you get them and before
>> merging.  And we will also need to change IGT ahead of merging this.
>
> Sure, do we rely on intel_reg only or do we also keep xe_reg?

xe_reg?! TIL.

A long time ago we used to have 10+ tools in IGT to access registers. It
was horrible and unmaintainable. Please let's focus on having *one* tool
for this:


commit dfda0b6aeccef464cc6f1af60d8ea16c11fb13f7
Author: Jani Nikula <jani.nikula@intel.com>
Date:   Wed Dec 10 14:27:07 2014 +0200

    intel_reg: introduce one intel_reg tool to rule them all
    
            Three Tools for the Elven-kings under the sky,
            Seven for the Dwarf-lords in their halls of stone,
            Nine for Mortal Men doomed to die,
            One for the Dark Lord on his dark throne
            In the Land of Mordor where the Shadows lie.
            One Tool to rule them all, One Tool to find them,
            One Tool to bring them all and in the darkness bind them
            In the Land of Mordor where the Shadows lie.
    
                    J.R.R. Tolkien's epigraph to The Lord of The Tools
                     | sed 's/Ring/Tool/g'
    
    Introduce intel_reg as the one Intel graphics register multitool to
    replace intel_reg_read, intel_reg_write, intel_iosf_sb_read,
    intel_iosf_sb_write, intel_vga_read, intel_vga_write, intel_reg_dumper,
    intel_reg_snapshot, and quick_dump.py.
    
    Signed-off-by: Jani Nikula <jani.nikula@intel.com>


BR,
Jani.


-- 
Jani Nikula, Intel

  reply	other threads:[~2023-09-14  8:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 19:35 [Intel-xe] [PATCH] drm/xe/uapi: Remove MMIO ioctl Francois Dugast
2023-09-07 19:44 ` Souza, Jose
2023-09-08  1:16 ` [Intel-xe] ✓ CI.Patch_applied: success for " Patchwork
2023-09-08  1:17 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-08  1:18 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-08  1:25 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-08  1:25 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-08  1:27 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-08  2:02 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-09-10 16:34 ` [Intel-xe] [PATCH] " Ofir Bitton
2023-09-11  3:45   ` Lucas De Marchi
2023-09-11  4:21     ` Ofir Bitton
2023-09-12  0:25       ` Matt Roper
2023-09-12  8:43         ` Ofir Bitton
2023-09-12 11:11           ` Jani Nikula
2023-09-12 18:33             ` Ofir Bitton
2023-09-14  8:35               ` Jani Nikula
2023-09-14 14:20                 ` Ofir Bitton
2023-09-14 20:47                   ` Daniel Vetter
2023-09-18  6:40                     ` Ofir Bitton
2023-09-18  9:54                       ` Jani Nikula
2023-09-12 14:42           ` Lucas De Marchi
2023-09-13 13:56             ` Francois Dugast
2023-09-14  8:43               ` Jani Nikula [this message]
2023-09-11  3:47 ` Lucas De Marchi
2023-09-11 11:53   ` Jani Nikula

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87edj1w3ek.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox