From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mika Kuoppala <mika.kuoppala@intel.com>
Subject: Re: [PATCH] x86: Silence 32bit compiler warning in intel_graphics_stolen()
Date: Mon, 9 May 2016 16:12:42 +0300 [thread overview]
Message-ID: <20160509131242.GM4329@intel.com> (raw)
In-Reply-To: <1462799071.5343.5.camel@linux.intel.com>
On Mon, May 09, 2016 at 04:04:31PM +0300, Joonas Lahtinen wrote:
> On pe, 2016-05-06 at 13:57 +0300, Ville Syrjälä wrote:
> > On Thu, May 05, 2016 at 05:15:17PM +0100, Chris Wilson wrote:
> > >
> > > arch/x86/kernel/early-quirks.c: In function ‘intel_graphics_stolen’:
> > > arch/x86/kernel/early-quirks.c:539:9: warning: format ‘%llx’ expects
> > > argument of type ‘long long unsigned int’, but argument 2 has type ‘phys_addr_t’ [-Wformat=]
> > > "0x%llx-0x%llx\n", base, base + size - 1);
> > > ^
> > > arch/x86/kernel/early-quirks.c:539:9: warning: format ‘%llx’ expects
> > > argument of type ‘long long unsigned int’, but argument 3 has type ‘phys_addr_t’ [-Wformat=]
> > This also makes the actual printk output crap. On my non-PAE machine
> > I saw somehting resembling this:
> > Reserving Intel graphics memory at 0x37ffffff3ffffffff-0x200000000
> >
> > Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > >
> > >
> > > Fixes: ee0629cfd3c16 (drm/i915: Function per early graphics quirk)
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > > Cc: Mika Kuoppala <mika.kuoppala@intel.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > > Cc: Thomas Gleixner <tglx@linutronix.de>
> > > Cc: Ingo Molnar <mingo@redhat.com>
> > > Cc: "H. Peter Anvin" <hpa@zytor.com>
> > > ---
> > > arch/x86/kernel/early-quirks.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/arch/x86/kernel/early-quirks.c b/arch/x86/kernel/early-quirks.c
> > > index d2f75b4..068ab3f 100644
> > > --- a/arch/x86/kernel/early-quirks.c
> > > +++ b/arch/x86/kernel/early-quirks.c
> > > @@ -535,8 +535,8 @@ intel_graphics_stolen(int num, int slot, int func,
> > > if (!size || !base)
> > > return;
> > >
> > > - printk(KERN_INFO "Reserving Intel graphics stolen memory at "
> > > - "0x%llx-0x%llx\n", base, base + size - 1);
> > > + printk(KERN_INFO "Reserving Intel graphics memory at 0x%llx-0x%llx\n",
> > > + (long long)base, (long long)(base + size - 1));
>
> Any reason not to make this %pa and %zx while at it?
>
> printk(KERN_INFO "Reserving Intel graphics memory at %pa (size 0x%zx)\n", &base, size);
The start-end style matches better with the e820 dump and whatnot.
IIRC that was the reason I made it look like it does.
>
> Regards, Joonas
>
> > >
> > > /* Mark this space as reserved */
> > > e820_add_region(base, size, E820_RESERVED);
> > > --
> > > 2.8.1
> --
> Joonas Lahtinen
> Open Source Technology Center
> Intel Corporation
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-09 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 16:15 [PATCH] x86: Silence 32bit compiler warning in intel_graphics_stolen() Chris Wilson
2016-05-05 16:43 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-05-06 10:57 ` [PATCH] " Ville Syrjälä
2016-05-09 13:04 ` Joonas Lahtinen
2016-05-09 13:12 ` Ville Syrjälä [this message]
2016-05-09 16:39 ` [PATCH v2] " Chris Wilson
2016-05-10 6:14 ` Joonas Lahtinen
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=20160509131242.GM4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=mika.kuoppala@intel.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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