From: Matthew Brost <matthew.brost@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: <intel-xe@lists.freedesktop.org>, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] drm/xe: Fix build error in xe_ggtt.c
Date: Mon, 26 Feb 2024 15:40:24 +0000 [thread overview]
Message-ID: <Zdyw6OT/SDir+3Op@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <98e9c8ea0f51cb308f02a1cf2ce61d06fd5bbc0a.camel@linux.intel.com>
On Mon, Feb 26, 2024 at 10:05:58AM +0100, Thomas Hellström wrote:
> On Sat, 2024-02-24 at 16:14 -0800, Matthew Brost wrote:
> > Need to include io-64-nonatomic-lo-hi.h for writeq function.
>
> As I understand it, the choice of header here determines the dword
> write order on 32-bit systems that don't have an atomic writeq(),
>
> So is writing the low dword first the correct order in this case?
> Perhaps add a motivation in the commit message?
>
"Cleanup some layering in GGTT" removed xe_mmio.h from xe_gt.c and that
file includes linux/io-64-nonatomic-lo-hi.h. Perhaps it is better just
to include xe_mmio.h again in xe_gt.c?
Matt
> /Thomas
>
>
> >
> > Fixes: 3121fed0c51b drm/xe: ("Cleanup some layering in GGTT")
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes:
> > https://lore.kernel.org/oe-kbuild-all/202402241903.R5J8hKVI-lkp@intel.com/
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_ggtt.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_ggtt.c
> > b/drivers/gpu/drm/xe/xe_ggtt.c
> > index 5d46958e3144..717d0e76277a 100644
> > --- a/drivers/gpu/drm/xe/xe_ggtt.c
> > +++ b/drivers/gpu/drm/xe/xe_ggtt.c
> > @@ -5,6 +5,7 @@
> >
> > #include "xe_ggtt.h"
> >
> > +#include <linux/io-64-nonatomic-lo-hi.h>
> > #include <linux/sizes.h>
> >
> > #include <drm/drm_managed.h>
>
next prev parent reply other threads:[~2024-02-26 15:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 0:14 [PATCH] drm/xe: Fix build error in xe_ggtt.c Matthew Brost
2024-02-25 0:19 ` ✓ CI.Patch_applied: success for " Patchwork
2024-02-25 0:20 ` ✗ CI.checkpatch: warning " Patchwork
2024-02-25 0:20 ` ✓ CI.KUnit: success " Patchwork
2024-02-25 0:31 ` ✓ CI.Build: " Patchwork
2024-02-25 0:32 ` ✓ CI.Hooks: " Patchwork
2024-02-25 0:33 ` ✓ CI.checksparse: " Patchwork
2024-02-25 0:53 ` ✓ CI.BAT: " Patchwork
2024-02-26 9:05 ` [PATCH] " Thomas Hellström
2024-02-26 15:40 ` Matthew Brost [this message]
2024-02-28 14:47 ` Thomas Hellström
2024-02-28 18:49 ` Lucas De Marchi
2024-02-29 0:52 ` Matthew Brost
2024-03-01 4:23 ` Lucas De Marchi
2024-02-26 12:10 ` 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=Zdyw6OT/SDir+3Op@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lkp@intel.com \
--cc=thomas.hellstrom@linux.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