From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Arnd Bergmann <arnd@arndb.de>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
linux-kernel@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-mm@kvack.org
Cc: Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Jason A . Donenfeld" <Jason@zx2c4.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Naveen N Rao <naveen@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Theodore Ts'o <tytso@mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH v3 1/2] drm: Fix fault format
Date: Mon, 7 Oct 2024 08:10:36 +0200 [thread overview]
Message-ID: <0a419a1d-6124-411c-bcae-a8dac87f73d0@csgroup.eu> (raw)
In-Reply-To: <5b52dfcf-7b4c-4715-b1b2-6e41062302bd@app.fastmail.com>
Le 04/10/2024 à 15:21, Arnd Bergmann a écrit :
> On Thu, Oct 3, 2024, at 15:29, Vincenzo Frascino wrote:
>> diff --git a/drivers/gpu/drm/i915/gt/intel_gt.c
>> b/drivers/gpu/drm/i915/gt/intel_gt.c
>> index a6c69a706fd7..352ef5e1c615 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_gt.c
>> +++ b/drivers/gpu/drm/i915/gt/intel_gt.c
>> @@ -308,7 +308,7 @@ static void gen6_check_faults(struct intel_gt *gt)
>> fault = GEN6_RING_FAULT_REG_READ(engine);
>> if (fault & RING_FAULT_VALID) {
>> gt_dbg(gt, "Unexpected fault\n"
>> - "\tAddr: 0x%08lx\n"
>> + "\tAddr: 0x%08x\n"
>> "\tAddress space: %s\n"
>> "\tSource ID: %d\n"
>> "\tType: %d\n",
>
> Isn't the type of PAGE_MASK still architecture dependent?
Indeed when I commented that PAGE_MASK was type agnostic I was thinking
about the powerpc PAGE_MASK:
#define PAGE_MASK (~((1 << PAGE_SHIFT) - 1))
It should probably be possible to generalise it to all architectures.
But if you keep some PAGE_MASK with forced UL type just like:
#define PAGE_SIZE (_AC(1, UL) << PAGE_SHIFT)
#define PAGE_MASK (~(PAGE_SIZE-1))
Then that version of PAGE_MASK isn't agnostic and ANDing an int with
that mask makes a long result.
> I think you need a cast to either 'int' or 'long' here to
> make the corresponding format string work across all
> architectures. With the current version of your patch 2/2,
> it looks like it has to be %x for architectures with
> 64-bit phys_addr_t, but %lx for the other ones.
>
> Changing the 'u32 fault' variable to 'unsigned long'
> would also work here.
>
> Arnd
next prev parent reply other threads:[~2024-10-07 6:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 15:29 [PATCH v3 0/2] vdso: Use only headers from the vdso/ namespace Vincenzo Frascino
2024-10-03 15:29 ` [PATCH v3 1/2] drm: Fix fault format Vincenzo Frascino
2024-10-04 13:21 ` Arnd Bergmann
2024-10-07 6:10 ` Christophe Leroy [this message]
2024-10-03 15:29 ` [PATCH v3 2/2] vdso: Introduce vdso/page.h Vincenzo Frascino
2024-10-04 9:07 ` Geert Uytterhoeven
2024-10-04 13:13 ` Arnd Bergmann
2024-10-07 11:01 ` Vincenzo Frascino
2024-10-07 11:06 ` Arnd Bergmann
2024-10-07 11:20 ` Vincenzo Frascino
2024-10-07 16:05 ` H. Peter Anvin
2024-10-07 16:23 ` Thomas Gleixner
2024-10-08 13:11 ` Arnd Bergmann
2024-10-08 14:20 ` Vincenzo Frascino
2024-10-09 9:53 ` Thomas Gleixner
2024-10-09 10:04 ` Thomas Gleixner
2024-10-09 23:58 ` Michael Ellerman
2024-10-10 12:37 ` Vincenzo Frascino
2024-10-10 12:36 ` Vincenzo Frascino
2024-10-10 12:35 ` Vincenzo Frascino
2024-10-03 16:25 ` [PATCH v3 0/2] vdso: Use only headers from the vdso/ namespace Jason A. Donenfeld
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=0a419a1d-6124-411c-bcae-a8dac87f73d0@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=vincenzo.frascino@arm.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;
as well as URLs for NNTP newsgroup(s).