Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi@etezian.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v3] drm/i915/gt: move remaining debugfs interfaces into gt
Date: Tue, 31 Mar 2020 20:13:09 +0300	[thread overview]
Message-ID: <20200331171309.GC26946@jack.zhora.eu> (raw)
In-Reply-To: <158567361246.5852.4972436644557691162@build.alporthouse.com>

Hi Chris,

On Tue, Mar 31, 2020 at 05:53:32PM +0100, Chris Wilson wrote:
> Quoting Andi Shyti (2020-03-31 17:45:08)
> > +static void intel_sseu_copy_subslices(const struct sseu_dev_info *sseu,
> > +                                     int slice, u8 *to_mask)
> > +{
> > +       int offset = slice * sseu->ss_stride;
> > +
> > +       memcpy(&to_mask[offset], &sseu->subslice_mask[offset], sseu->ss_stride);
> > +}
> 
> Worth moving all the sseu into their file? There's quite a few of them
> and each quite chunky.
> 
> > +static int interrupt_info_show(struct seq_file *m, void *data)
> 
> And if we start there, we might end up with debugfs_gt_irq.c as well?
> (Not that I see any use for this debugfs info :)

add a debufs_gt_sseu.c and debugfs_gt_irq.c, isn't it a bit
excessive? I also do agree that everything in one file looks a
bit stuffed.

> > +static int reset_get(void *data, u64 *val)
> > +{
> > +       struct intel_gt *gt = data;
> > +       int ret = intel_gt_terminally_wedged(gt);
> > +
> > +       switch (ret) {
> > +       case -EIO:
> > +               *val = 1;
> > +               return 0;
> > +       case 0:
> > +               *val = 0;
> > +               return 0;
> > +       default:
> > +               return ret;
> > +       }
> 
> reset_get? Ok if you document it as reporting wedged status :)
> 
> > +}
> > +
> > +static int reset_set(void *data, u64 val)
> > +{
> > +       struct intel_gt *gt = data;
> > +
> > +       /* Flush any previous reset before applying for a new one */
> > +       wait_event(gt->reset.queue,
> > +                  !test_bit(I915_RESET_BACKOFF, &gt->reset.flags));
> > +
> > +       intel_gt_handle_error(gt, val, I915_ERROR_CAPTURE,
> > +                             "Manually set wedged engine mask = %llx", val);
> 
> No hint of i915_wedged any more. Just "Manual reset engine mask %llx",
> or somesuch will do.

OK, I will try to improve the transition freom "wedged" to
"reset". Thanks.

Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-03-31 17:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31 16:45 [Intel-gfx] [PATCH v3] drm/i915/gt: move remaining debugfs interfaces into gt Andi Shyti
2020-03-31 16:53 ` Chris Wilson
2020-03-31 17:13   ` Andi Shyti [this message]
2020-03-31 17:16     ` Chris Wilson
  -- strict thread matches above, loose matches on Subject: below --
2021-10-08 11:27 Andi Shyti
2021-10-08 16:42 ` Ville Syrjälä
2021-10-08 20:46   ` Andi Shyti

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=20200331171309.GC26946@jack.zhora.eu \
    --to=andi@etezian.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    /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