[powerpc:fixes-test] BUILD SUCCESS dfb5f8cbd5992d5769edfd3e059fad9e0b8bdafb

2023-09-30 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git 
fixes-test
branch HEAD: dfb5f8cbd5992d5769edfd3e059fad9e0b8bdafb  powerpc/pseries: Remove 
unused r0 in the hcall tracing code

elapsed time: 818m

configs tested: 129
configs skipped: 2

The following configs have been built successfully.
More configs may be tested in the coming days.

tested configs:
alpha allnoconfig   gcc  
alphaallyesconfig   gcc  
alpha   defconfig   gcc  
arc  allmodconfig   gcc  
arc   allnoconfig   gcc  
arc  allyesconfig   gcc  
arc defconfig   gcc  
archsdk_defconfig   gcc  
arc   randconfig-001-20230930   gcc  
arc   randconfig-001-20231001   gcc  
arm  allmodconfig   gcc  
arm   allnoconfig   gcc  
arm  allyesconfig   gcc  
arm defconfig   gcc  
arm  footbridge_defconfig   gcc  
arm   milbeaut_m10v_defconfig   clang
arm   randconfig-001-20231001   gcc  
arm64allmodconfig   gcc  
arm64 allnoconfig   gcc  
arm64allyesconfig   gcc  
arm64   defconfig   gcc  
csky allmodconfig   gcc  
csky  allnoconfig   gcc  
csky allyesconfig   gcc  
cskydefconfig   gcc  
i386 allmodconfig   gcc  
i386  allnoconfig   gcc  
i386 allyesconfig   gcc  
i386 buildonly-randconfig-001-20230930   gcc  
i386 buildonly-randconfig-001-20231001   gcc  
i386 buildonly-randconfig-002-20230930   gcc  
i386 buildonly-randconfig-002-20231001   gcc  
i386 buildonly-randconfig-003-20230930   gcc  
i386 buildonly-randconfig-003-20231001   gcc  
i386 buildonly-randconfig-004-20230930   gcc  
i386 buildonly-randconfig-004-20231001   gcc  
i386 buildonly-randconfig-005-20230930   gcc  
i386 buildonly-randconfig-005-20231001   gcc  
i386 buildonly-randconfig-006-20230930   gcc  
i386 buildonly-randconfig-006-20231001   gcc  
i386  debian-10.3   gcc  
i386defconfig   gcc  
i386  randconfig-001-20230930   gcc  
i386  randconfig-001-20231001   gcc  
i386  randconfig-002-20230930   gcc  
i386  randconfig-002-20231001   gcc  
i386  randconfig-003-20230930   gcc  
i386  randconfig-003-20231001   gcc  
i386  randconfig-004-20230930   gcc  
i386  randconfig-004-20231001   gcc  
i386  randconfig-005-20230930   gcc  
i386  randconfig-005-20231001   gcc  
i386  randconfig-006-20230930   gcc  
i386  randconfig-006-20231001   gcc  
loongarchallmodconfig   gcc  
loongarch allnoconfig   gcc  
loongarchallyesconfig   gcc  
loongarch   defconfig   gcc  
loongarch randconfig-001-20230930   gcc  
loongarch randconfig-001-20231001   gcc  
m68k allmodconfig   gcc  
m68k  allnoconfig   gcc  
m68k allyesconfig   gcc  
m68kdefconfig   gcc  
microblaze   allmodconfig   gcc  
microblazeallnoconfig   gcc  
microblaze   allyesconfig   gcc  
microblaze  defconfig   gcc  
mips allmodconfig   gcc  
mips  allnoconfig   gcc  
mips allyesconfig   gcc  
nios2allmodconfig   gcc  
nios2 allnoconfig   gcc  
nios2allyesconfig   gcc  
nios2   defconfig   gcc  
openrisc allmodconfig   gcc  
openrisc  allnoconfig   gcc  
openrisc allyesconfig   gcc  
openriscdefconfig   gcc  
parisc   allmodconfig   gcc  
pariscallnoconfig   gcc  
parisc   allyesconfig   gcc  
parisc  defconfig   gcc  
parisc64defconfig   gcc  
powerpc  allmodconfig   gcc  
powerpc

[PATCH] soc: fsl: fix kernel-doc warnings and typos

2023-09-30 Thread Randy Dunlap
Correct spelling of "list".

Fix a kernel-doc warning by describing the nested structure completely:

include/soc/fsl/dpaa2-fd.h:52: warning: Function parameter or member 'simple' 
not described in 'dpaa2_fd'

Signed-off-by: Randy Dunlap 
Cc: Li Yang 
Cc: linuxppc-dev@lists.ozlabs.org
Cc: linux-arm-ker...@lists.infradead.org
---
 include/soc/fsl/dpaa2-fd.h |   19 ++-
 1 file changed, 10 insertions(+), 9 deletions(-)

diff -- a/include/soc/fsl/dpaa2-fd.h b/include/soc/fsl/dpaa2-fd.h
--- a/include/soc/fsl/dpaa2-fd.h
+++ b/include/soc/fsl/dpaa2-fd.h
@@ -25,14 +25,15 @@
 
 /**
  * struct dpaa2_fd - Struct describing FDs
- * @words: for easier/faster copying the whole FD structure
- * @addr:  address in the FD
- * @len:   length in the FD
- * @bpid:  buffer pool ID
- * @format_offset: format, offset, and short-length fields
- * @frc:   frame context
- * @ctrl:  control bits...including dd, sc, va, err, etc
- * @flc:   flow context address
+ * @words:for easier/faster copying the whole FD structure
+ * @simple:   struct for the FD fields
+ * @simple.addr:  address in the FD
+ * @simple.len:   length in the FD
+ * @simple.bpid:  buffer pool ID
+ * @simple.format_offset: format, offset, and short-length fields
+ * @simple.frc:   frame context
+ * @simple.ctrl:  control bits...including dd, sc, va, err, etc
+ * @simple.flc:   flow context address
  *
  * This structure represents the basic Frame Descriptor used in the system.
  */
@@ -497,7 +498,7 @@ static inline void dpaa2_fl_set_addr(str
  * dpaa2_fl_get_frc() - Get the frame context in the FLE
  * @fle: the given frame list entry
  *
- * Return the frame context field in the frame lsit entry.
+ * Return the frame context field in the frame list entry.
  */
 static inline u32 dpaa2_fl_get_frc(const struct dpaa2_fl_entry *fle)
 {


[PATCH] soc: fsl: dpio: fix kernel-doc typos

2023-09-30 Thread Randy Dunlap
Correct spelling of 2 words.

Signed-off-by: Randy Dunlap 
Cc: Li Yang 
Cc: linuxppc-dev@lists.ozlabs.org
Cc: linux-arm-ker...@lists.infradead.org
Cc: Roy Pledge 
---
 include/soc/fsl/dpaa2-io.h |4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff -- a/include/soc/fsl/dpaa2-io.h b/include/soc/fsl/dpaa2-io.h
--- a/include/soc/fsl/dpaa2-io.h
+++ b/include/soc/fsl/dpaa2-io.h
@@ -22,7 +22,7 @@ struct device;
  * DOC: DPIO Service
  *
  * The DPIO service provides APIs for users to interact with the datapath
- * by enqueueing and dequeing frame descriptors.
+ * by enqueueing and dequeueing frame descriptors.
  *
  * The following set of APIs can be used to enqueue and dequeue frames
  * as well as producing notification callbacks when data is available
@@ -33,7 +33,7 @@ struct device;
 
 /**
  * struct dpaa2_io_desc - The DPIO descriptor
- * @receives_notifications: Use notificaton mode. Non-zero if the DPIO
+ * @receives_notifications: Use notification mode. Non-zero if the DPIO
  *  has a channel.
  * @has_8prio:  Set to non-zero for channel with 8 priority WQs.  Ignored
  *  unless receives_notification is TRUE.


Re: [PATCH 86/87] fs: switch timespec64 fields in inode to discrete integers

2023-09-30 Thread Steve French
On Fri, Sep 29, 2023 at 3:06 AM David Howells via samba-technical
 wrote:
>
>
> Jeff Layton  wrote:
>
> > Correct. We'd lose some fidelity in currently stored timestamps, but as
> > Linus and Ted pointed out, anything below ~100ns granularity is
> > effectively just noise, as that's the floor overhead for calling into
> > the kernel. It's hard to argue that any application needs that sort of
> > timestamp resolution, at least with contemporary hardware.
>
> Albeit with the danger of making Steve French very happy;-), would it make
> sense to switch internally to Microsoft-style 64-bit timestamps with their
> 100ns granularity?

100ns granularity does seem to make sense and IIRC was used by various
DCE standards in the 90s and 2000s (not just used for SMB2/SMB3 protocol and
various Windows filesystems)


-- 
Thanks,

Steve


Re: [GIT PULL] Please pull powerpc/linux.git powerpc-6.6-3 tag

2023-09-30 Thread pr-tracker-bot
The pull request you sent on Sat, 30 Sep 2023 23:11:46 +1000:

> https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git 
> tags/powerpc-6.6-3

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1c9d83122196ac649dee1da5f48f16462ba5385f

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html


Re: [PATCH 01/15] cdrom: Remove now superfluous sentinel element from ctl_table array

2023-09-30 Thread Phillip Potter
On Fri, Sep 29, 2023 at 02:17:30PM +0200, Joel Granados wrote:
> On Thu, Sep 28, 2023 at 03:36:55PM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Sep 28, 2023 at 03:21:26PM +0200, Joel Granados via B4 Relay wrote:
> > > From: Joel Granados 
> > > 
> > > This commit comes at the tail end of a greater effort to remove the
> > > empty elements at the end of the ctl_table arrays (sentinels) which
> > > will reduce the overall build time size of the kernel and run time
> > > memory bloat by ~64 bytes per sentinel (further information Link :
> > > https://lore.kernel.org/all/zo5yx5jfoggi%2f...@bombadil.infradead.org/)
> > > 
> > > Remove sentinel element from cdrom_table
> > > 
> > > Signed-off-by: Joel Granados 
> > > ---
> > >  drivers/cdrom/cdrom.c | 3 +--
> > >  1 file changed, 1 insertion(+), 2 deletions(-)
> > > 
> > > diff --git a/drivers/cdrom/cdrom.c b/drivers/cdrom/cdrom.c
> > > index cc2839805983..451907ade389 100644
> > > --- a/drivers/cdrom/cdrom.c
> > > +++ b/drivers/cdrom/cdrom.c
> > > @@ -3654,8 +3654,7 @@ static struct ctl_table cdrom_table[] = {
> > >   .maxlen = sizeof(int),
> > >   .mode   = 0644,
> > >   .proc_handler   = cdrom_sysctl_handler
> > > - },
> > > - { }
> > > + }
> > 
> > You should have the final entry as "}," so as to make any future
> > additions to the list to only contain that entry, that's long been the
> > kernel style for lists like this.
> Will send a V2 with this included. Thx.
> 
> > 
> > So your patches will just remove one line, not 2 and add 1, making it a
> > smaller diff.
> indeed.
> 
> > 
> > thanks,
> > 
> > greg k-h
> 
> -- 
> 
> Joel Granados

Hi Joel,

Thank you for your patch. I look forward to seeing V2, and will be happy
to review it.

Regards,
Phil


Re: [PATCH v4] powerpc: Use shared font data

2023-09-30 Thread Dr. David Alan Gilbert
* li...@treblig.org (li...@treblig.org) wrote:
> From: "Dr. David Alan Gilbert" 
> 
> PowerPC has a 'btext' font used for the console which is almost identical
> to the shared font_sun8x16, so use it rather than duplicating the data.

Hi Michael,
  Are you going to pick this up for 6.7?

Dave

> They were actually identical until about a decade ago when
>commit bcfbeecea11c ("drivers: console: font_: Change a glyph from
> "broken bar" to "vertical line"")
> 
> which changed the | in the shared font to be a solid
> bar rather than a broken bar.  That's the only difference.
> 
> This was originally spotted by the PMF source code analyser, which
> noticed that sparc does the same thing with the same data, and they
> also share a bunch of functions to manipulate the data.  I've previously
> posted a near identical patch for sparc.
> 
> Tested very lightly with a boot without FS in qemu.
> 
> Signed-off-by: Dr. David Alan Gilbert 
> ---
> v4
>   Simplify lib/fonts/Kconfig entry (Michael's suggestion)
> 
> v3
>   Fixup lib/fonts/Kconfig to not require FRAMEBUFFER_CONSOLE
>   for BOOTX, and add a || PPC, no longer need to 'select FONTS'
>   Passes a bunch of randconfigs (as spotted by Randy)
> 
>  arch/powerpc/Kconfig.debug  |   2 +
>  arch/powerpc/kernel/btext.c | 360 +---
>  lib/fonts/Kconfig   |   2 +-
>  3 files changed, 9 insertions(+), 355 deletions(-)
> 
> diff --git a/arch/powerpc/Kconfig.debug b/arch/powerpc/Kconfig.debug
> index 2a54fadbeaf51..50ff3359cde93 100644
> --- a/arch/powerpc/Kconfig.debug
> +++ b/arch/powerpc/Kconfig.debug
> @@ -147,6 +147,8 @@ config BDI_SWITCH
>  config BOOTX_TEXT
>   bool "Support for early boot text console (BootX or OpenFirmware only)"
>   depends on PPC_BOOK3S
> + select FONT_SUN8x16
> + select FONT_SUPPORT
>   help
> Say Y here to see progress messages from the boot firmware in text
> mode. Requires either BootX or Open Firmware.
> diff --git a/arch/powerpc/kernel/btext.c b/arch/powerpc/kernel/btext.c
> index 19e46fd623b0d..7f63f1cdc6c39 100644
> --- a/arch/powerpc/kernel/btext.c
> +++ b/arch/powerpc/kernel/btext.c
> @@ -8,6 +8,7 @@
>  #include 
>  #include 
>  #include 
> +#include 
>  #include 
>  #include 
>  #include 
> @@ -41,10 +42,6 @@ static unsigned char *logicalDisplayBase __force_data;
>  
>  unsigned long disp_BAT[2] __initdata = {0, 0};
>  
> -#define cmapsz   (16*256)
> -
> -static unsigned char vga_font[cmapsz];
> -
>  static int boot_text_mapped __force_data;
>  
>  extern void rmci_on(void);
> @@ -407,7 +404,7 @@ static unsigned int expand_bits_16[4] = {
>  };
>  
>  
> -static void draw_byte_32(unsigned char *font, unsigned int *base, int rb)
> +static void draw_byte_32(const unsigned char *font, unsigned int *base, int 
> rb)
>  {
>   int l, bits;
>   int fg = 0xUL;
> @@ -428,7 +425,7 @@ static void draw_byte_32(unsigned char *font, unsigned 
> int *base, int rb)
>   }
>  }
>  
> -static inline void draw_byte_16(unsigned char *font, unsigned int *base, int 
> rb)
> +static inline void draw_byte_16(const unsigned char *font, unsigned int 
> *base, int rb)
>  {
>   int l, bits;
>   int fg = 0xUL;
> @@ -446,7 +443,7 @@ static inline void draw_byte_16(unsigned char *font, 
> unsigned int *base, int rb)
>   }
>  }
>  
> -static inline void draw_byte_8(unsigned char *font, unsigned int *base, int 
> rb)
> +static inline void draw_byte_8(const unsigned char *font, unsigned int 
> *base, int rb)
>  {
>   int l, bits;
>   int fg = 0x0F0F0F0FUL;
> @@ -465,7 +462,8 @@ static inline void draw_byte_8(unsigned char *font, 
> unsigned int *base, int rb)
>  static noinline void draw_byte(unsigned char c, long locX, long locY)
>  {
>   unsigned char *base = calc_base(locX << 3, locY << 4);
> - unsigned char *font = _font[((unsigned int)c) * 16];
> + unsigned int font_index = c * 16;
> + const unsigned char *font   = font_sun_8x16.data + font_index;
>   int rb  = dispDeviceRowBytes;
>  
>   rmci_maybe_on();
> @@ -583,349 +581,3 @@ void __init udbg_init_btext(void)
>*/
>   udbg_putc = btext_drawchar;
>  }
> -
> -static unsigned char vga_font[cmapsz] = {
> -0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> -0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x7e, 0x81, 0xa5, 0x81, 0x81, 0xbd,
> -0x99, 0x81, 0x81, 0x7e, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x7e, 0xff,
> -0xdb, 0xff, 0xff, 0xc3, 0xe7, 0xff, 0xff, 0x7e, 0x00, 0x00, 0x00, 0x00,
> -0x00, 0x00, 0x00, 0x00, 0x6c, 0xfe, 0xfe, 0xfe, 0xfe, 0x7c, 0x38, 0x10,
> -0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x38, 0x7c, 0xfe,
> -0x7c, 0x38, 0x10, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x18,
> -0x3c, 0x3c, 0xe7, 0xe7, 0xe7, 0x18, 0x18, 0x3c, 0x00, 0x00, 0x00, 0x00,
> -0x00, 0x00, 0x00, 0x18, 0x3c, 0x7e, 0xff, 0xff, 0x7e, 0x18, 0x18, 0x3c,
> -0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 

[GIT PULL] Please pull powerpc/linux.git powerpc-6.6-3 tag

2023-09-30 Thread Michael Ellerman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Linus,

Please pull some more powerpc fixes for 6.6:

The following changes since commit c3f4309693758b13fbb34b3741c2e2801ad28769:

  powerpc/dexcr: Move HASHCHK trap handler (2023-09-18 12:23:48 +1000)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git 
tags/powerpc-6.6-3

for you to fetch changes up to 58b33e78a31782ffe25d404d5eba9a45fe636e27:

  selftests/powerpc: Fix emit_tests to work with run_kselftest.sh (2023-09-22 
20:29:48 +1000)

- --
powerpc fixes for 6.6 #3

 - Fix arch_stack_walk_reliable(), used by live patching.

 - Fix powerpc selftests to work with run_kselftest.sh

Thanks to: Joe Lawrence, Petr Mladek.

- --
Michael Ellerman (2):
  powerpc/stacktrace: Fix arch_stack_walk_reliable()
  selftests/powerpc: Fix emit_tests to work with run_kselftest.sh


 arch/powerpc/kernel/stacktrace.c | 27 
 tools/testing/selftests/powerpc/Makefile |  7 +++--
 tools/testing/selftests/powerpc/pmu/Makefile | 11 
 3 files changed, 14 insertions(+), 31 deletions(-)
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmUYHX8ACgkQUevqPMjh
pYBvDBAAoCipzzNry+rTrf2bc9dOyCCyRsUhTsujXye+rGuxKMEiTalds8+t6F68
8LOJ1X2sFeGk25R5VSqjxbFqxRAyfcTMttnOJs5QTBomZAa4EWyQT/+JRAnj1sS3
XspFNjFpgENQ3qyDtRBCXBGZ55EGv45yXTrXmOS7mvHvrMEQyU2H4XZPyvuBf3kz
5/uz0rb+aZsYvq1Hq5PGX+3dWSa4VYeB9FYOwZeGTe9ycpwvw1nvYJ7sBTS+MBkh
oISlPrq0cUGFP/4cr0DBlekyyIrdgs6wHArX7uTflR0P6M59AQeArwzqDWwHMzY0
DdbpH4104YKkv9bE2nfywgvGveKkBIAiCd8aEG0yH/cc8emrAabbvgWem+TrN1Yf
ELehUuEjL442T3m5QpDJUxgrFeF9INFnuztYupgZuQIhEQxqmg1tXXcsLqAlgnL2
uU++CS7SfYKiLtGNxmxGtQB+zYA8qQZ8z+9mzDm7qNmjfm9Zfye1WKYIOJRpJP1N
wt/MYJVbOCI5ZXqIAdOHGZDFu7KkcSpGiRt7634epGgY5JHGQnmXIJq0g0Tir4uE
lrHCJOwrStUfbaKKEB0K9tvbS+Q/l3N3LBYVJFkyYU9lCzjT83OPE9BS5mY2LxZg
86PmrwTP/9DPWh5i/u6Fj+CAIt3SpD57Jmdtxnn7gGVPd2nGEbQ=
=uC7L
-END PGP SIGNATURE-


Re: [PATCH 0/3] Fix for shellcheck issues with version "0.6"

2023-09-30 Thread Athira Rajeev



> On 28-Sep-2023, at 9:24 AM, Namhyung Kim  wrote:
> 
> On Tue, Sep 26, 2023 at 9:29 PM Athira Rajeev
>  wrote:
>> 
>> 
>> 
>>> On 25-Sep-2023, at 1:34 PM, kajoljain  wrote:
>>> 
>>> 
>>> 
>>> On 9/7/23 22:45, Athira Rajeev wrote:
 From: root 
 
 shellcheck was run on perf tool shell scripts s a pre-requisite
 to include a build option for shellcheck discussed here:
 https://www.spinics.net/lists/linux-perf-users/msg25553.html
 
 And fixes were added for the coding/formatting issues in
 two patchsets:
 https://lore.kernel.org/linux-perf-users/20230613164145.50488-1-atraj...@linux.vnet.ibm.com/
 https://lore.kernel.org/linux-perf-users/20230709182800.53002-1-atraj...@linux.vnet.ibm.com/
 
 Three additional issues are observed with shellcheck "0.6" and
 this patchset covers those. With this patchset,
 
 # for F in $(find tests/shell/ -perm -o=x -name '*.sh'); do shellcheck -S 
 warning $F; done
 # echo $?
 0
 
>>> 
>>> Patchset looks good to me.
>>> 
>>> Reviewed-by: Kajol Jain 
>>> 
>>> Thanks,
>>> Kajol Jain
>>> 
>> 
>> Hi Namhyunbg,
>> 
>> Can you please check for this patchset also
> 
> Sure, it's applied to perf-tools-next, thanks!

Thanks Namhyung

Athira




Re: [PATCH V3] perf test: Fix parse-events tests to skip parametrized events

2023-09-30 Thread Athira Rajeev



> On 30-Sep-2023, at 11:23 AM, Namhyung Kim  wrote:
> 
> On Wed, Sep 27, 2023 at 11:17 AM Athira Rajeev
>  wrote:
>> 
>> Testcase "Parsing of all PMU events from sysfs" parse events for
>> all PMUs, and not just cpu. In case of powerpc, the PowerVM
>> environment supports events from hv_24x7 and hv_gpci PMU which
>> is of example format like below:
>> 
>> - hv_24x7/CPM_ADJUNCT_INST,domain=?,core=?/
>> - hv_gpci/event,partition_id=?/
>> 
>> The value for "?" needs to be filled in depending on system
>> configuration. It is better to skip these parametrized events
>> in this test as it is done in:
>> 'commit b50d691e50e6 ("perf test: Fix "all PMU test" to skip
>> parametrized events")' which handled a simialr instance with
>> "all PMU test".
>> 
>> Fix parse-events test to skip parametrized events since
>> it needs proper setup of the parameters.
>> 
>> Signed-off-by: Athira Rajeev 
>> Tested-by: Ian Rogers 
>> Tested-by: Sachin Sant 
>> Reviewed-by: Kajol Jain 
> 
> Applied to perf-tools-next, thanks!

Thanks Namhyung,

Athira