Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe/pmu: Remove PMU from Xe till uapi is finalized
Date: Mon, 11 Dec 2023 20:05:30 -0800	[thread overview]
Message-ID: <87sf489ib9.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <ZXd_WnOovW9ot4SD@fdugast-desk.home>

On Mon, 11 Dec 2023 13:30:02 -0800, Francois Dugast wrote:

Hi Francois,

>
> On Mon, Dec 11, 2023 at 10:25:09AM -0800, Umesh Nerlige Ramappa wrote:
> > On Sat, Dec 09, 2023 at 02:43:52PM -0800, Ashutosh Dixit wrote:
> > > PMU uapi is likely to change in the future. Till the uapi is finalized,
> > > remove PMU from Xe. PMU can be re-added after uapi is finalized.
> > >
> > > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> >
> > I guess partial removal was messy. This is fine.
> >
> > Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>
> It seems this patch cannot be used as it is, I am getting the same error
> as the one reported by CI:
>
>     ../drivers/gpu/drm/xe/tests/xe_dma_buf.c:125:47: error: \
>     ‘DRM_XE_GEM_CPU_CACHING_WC’ undeclared (first use in this function)
>       125 |  bo = xe_bo_create_user(xe, NULL, NULL, size, DRM_XE_GEM_CPU_CACHING_WC,
>
> drivers/gpu/drm/xe/tests/xe_dma_buf.c appears to be missing a:
>
>     #include <drm/xe_drm.h>

I had a missing CONFIG_KUNIT, added this line and posted this:

https://patchwork.freedesktop.org/series/127598/#rev3

Actually posted another version here with a separate 'fixup' to
drivers/gpu/drm/xe/tests/xe_dma_buf.c:

https://patchwork.freedesktop.org/series/127664/

Both should be fine. Please pick one.

Thanks.
--
Ashutosh

  reply	other threads:[~2023-12-12  4:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-09 22:43 [PATCH] drm/xe/pmu: Remove PMU from Xe till uapi is finalized Ashutosh Dixit
2023-12-09 22:46 ` ✓ CI.Patch_applied: success for drm/xe/pmu: Remove PMU from Xe till uapi is finalized (rev2) Patchwork
2023-12-09 22:46 ` ✗ CI.checkpatch: warning " Patchwork
2023-12-09 22:46 ` ✗ CI.KUnit: failure " Patchwork
2023-12-09 22:52 ` [PATCH] drm/xe/pmu: Remove PMU from Xe till uapi is finalized Dixit, Ashutosh
2023-12-11  6:04   ` Aravind Iddamsetty
2023-12-11  6:35     ` Dixit, Ashutosh
2023-12-11  7:03       ` Aravind Iddamsetty
2023-12-11 16:29 ` Lucas De Marchi
2023-12-11 18:25 ` Umesh Nerlige Ramappa
2023-12-11 21:30   ` Francois Dugast
2023-12-12  4:05     ` Dixit, Ashutosh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-12  3:41 Ashutosh Dixit
2023-12-09 22:43 Ashutosh Dixit

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=87sf489ib9.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=francois.dugast@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=rodrigo.vivi@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