From: Andi Shyti <andi.shyti@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: MichalłWiniarski <michal.winiarski@intel.com>,
"Intel GFX" <intel-gfx@lists.freedesktop.org>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"DRI Devel" <dri-devel@lists.freedesktop.org>,
"Chris Wilson" <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH v4 1/2] drm/i915: Store backpointer to GT in uncore
Date: Wed, 1 Dec 2021 01:52:51 +0200 [thread overview]
Message-ID: <Yaa5U+bEEc4So2E8@intel.intel> (raw)
In-Reply-To: <20211128110926.2569-2-andi.shyti@linux.intel.com>
Hi,
ping! (Lucas?)
> We now support a per-gt uncore, yet we're not able to infer which GT
> we're operating upon. Let's store a backpointer for now.
>
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
can we merge this, meanwhile?
Andi
next prev parent reply other threads:[~2021-11-30 23:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 11:09 [Intel-gfx] [PATCH v4 0/2] More preparation for multi gt patches Andi Shyti
2021-11-28 11:09 ` [Intel-gfx] [PATCH v4 1/2] drm/i915: Store backpointer to GT in uncore Andi Shyti
2021-11-30 23:52 ` Andi Shyti [this message]
2021-11-28 11:09 ` [Intel-gfx] [PATCH v4 2/2] drm/i915: Use to_root_gt() to refer to the root tile Andi Shyti
2021-11-30 21:07 ` Lucas De Marchi
2021-11-30 22:41 ` Andi Shyti
2021-12-01 0:38 ` Lucas De Marchi
2021-12-01 9:44 ` Michal Wajdeczko
2021-12-01 12:58 ` Andi Shyti
2021-11-28 11:38 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for More preparation for multi gt patches (rev4) Patchwork
2021-11-28 12:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-28 13:58 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=Yaa5U+bEEc4So2E8@intel.intel \
--to=andi.shyti@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=michal.winiarski@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