-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Linus,
Please pull a powerpc fix for 6.12:
The following changes since commit cf8989d20d64ad702a6210c11a0347ebf3852aa7:
powerpc/powernv: Free name on error in opal_event_init() (2024-10-16 09:26:50
+1100)
are available in the git repository
Hello Venkat,
Thanks for testing the patch series.
- Sourabh Jain
On 07/11/24 19:25, Venkat Rao Bagalkote wrote:
Applied the below patch to 6.12.0-rc6-next20241106 and issue is not
seen. Results look good to me.
[root@ltcden8-lp5 ~]# uname -r
6.12.0-rc6-next-20241106-2-gf374fbb4ee1a
[ro
> On 7 Nov 2024, at 7:26 PM, Leo Yan wrote:
>
> Hi Athira,
>
> On Wed, Nov 06, 2024 at 03:04:57PM +0530, Athira Rajeev wrote:
>
> [...]
>
>>> Hi Athira,
>>>
>>> sorry for the breakage and thank you for the detailed explanation. As
>>> the code will run on AMD I think your change will break
Christophe Leroy writes:
> Le 07/11/2024 à 12:29, Michael Ellerman a écrit :
>> Yang Li writes:
>>> The header files linux/mem_encrypt.h is included twice in svm.c,
>>> so one inclusion of each can be removed.
>>>
>>> Reported-by: Abaci Robot
>>> Closes: https://bugzilla.openanolis.cn/show_bug.c
Gautam Menghani writes:
> On Thu, Nov 07, 2024 at 10:54:29PM +1100, Michael Ellerman wrote:
>> Gautam Menghani writes:
>> > As per the kernel documentation[1], hardlockup detector should be
>> > disabled in KVM guests as it may give false positives. On PPC, hardlockup
>> > detector is broken insi
On Wed, Nov 06, 2024 at 02:19:38PM -0800, Matthew Maurer wrote:
> >
> > > If booted against an old kernel, it will
> > > behave as though there is no modversions information.
> >
> > Huh? This I don't get. If you have the new libkmod and boot
> > an old kernel, that should just not break becauase w
Hi Athira,
On Wed, Nov 06, 2024 at 03:04:57PM +0530, Athira Rajeev wrote:
[...]
> > Hi Athira,
> >
> > sorry for the breakage and thank you for the detailed explanation. As
> > the code will run on AMD I think your change will break that - . It is
> > probably safest to keep the ".. else { .." f
Applied the below patch to 6.12.0-rc6-next20241106 and issue is not seen.
Results look good to me.
[root@ltcden8-lp5 ~]# uname -r
6.12.0-rc6-next-20241106-2-gf374fbb4ee1a
[root@ltcden8-lp5 ~]#
Please add below tag.
> Tested-by: Venkat Rao Bagalkote
> On 7 Nov 2024, at 11:28 AM, Sou
On 2024-11-07 2:03 p.m., Colton Lewis wrote:
> Previously any PMU overflow interrupt that fired while a VCPU was
> loaded was recorded as a guest event whether it truly was or not. This
> resulted in nonsense perf recordings that did not honor
> perf_event_attr.exclude_guest and recorded guest I
On 2024-11-07 2:03 p.m., Colton Lewis wrote:
> Break the assignment logic for misc flags into their own respective
> functions to reduce the complexity of the nested logic.
>
> Signed-off-by: Colton Lewis
> Reviewed-by: Oliver Upton
> ---
Acked-by: Kan Liang
Thanks,
Kan
> arch/x86/events/
Adding Lucas DeMarchi to the thread after voicing an interest in the
modpost patch.
On Thu, Oct 31, 2024 at 12:49 AM Luis Chamberlain wrote:
>
> On Wed, Oct 30, 2024 at 10:06:12PM -0700, Matthew Maurer wrote:
> > On Wed, Oct 30, 2024 at 9:37 PM Luis Chamberlain wrote:
> > >
> > > On Thu, Oct 31,
On 2024-11-07 2:03 p.m., Colton Lewis wrote:
> For clarity, rename the arch-specific definitions of these functions
> to perf_arch_* to denote they are arch-specifc. Define the
> generic-named functions in one place where they can call the
> arch-specific ones as needed.
>
> Signed-off-by: Colt
On Wed, Nov 6, 2024 at 10:27 PM Lucas De Marchi
wrote:
>
> On Wed, Nov 06, 2024 at 02:19:38PM -0800, Matthew Maurer wrote:
> >>
> >> > If booted against an old kernel, it will
> >> > behave as though there is no modversions information.
> >>
> >> Huh? This I don't get. If you have the new libkmod
On Thu, Nov 07, 2024 at 10:26:46PM +1100, Michael Ellerman wrote:
> From: Arnd Bergmann
>
> Unlike all other arches, powerpc doesn't allow the user to override CPP,
> because it sets it unconditionally in the arch Makefile. This can lead
> to strange build failures.
>
> Instead add the required
Yang Li writes:
> The header files linux/mem_encrypt.h is included twice in svm.c,
> so one inclusion of each can be removed.
>
> Reported-by: Abaci Robot
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=11750
> Signed-off-by: Yang Li
> ---
> arch/powerpc/platforms/pseries/svm.c | 1 -
>
For clarity, rename the arch-specific definitions of these functions
to perf_arch_* to denote they are arch-specifc. Define the
generic-named functions in one place where they can call the
arch-specific ones as needed.
Signed-off-by: Colton Lewis
Acked-by: Thomas Richter
Acked-by: Mark Rutland
Break the assignment logic for misc flags into their own respective
functions to reduce the complexity of the nested logic.
Signed-off-by: Colton Lewis
Reviewed-by: Oliver Upton
---
arch/x86/events/core.c| 32 +++
arch/x86/include/asm/perf_event.h | 2 ++
For arm's implementation, perf_instruction_pointer() and
perf_misc_flags() are equivalent to the generic versions in
include/linux/perf_event.h so arch/arm doesn't need to provide its
own versions. Drop them here.
Signed-off-by: Colton Lewis
Acked-by: Will Deacon
Reviewed-by: Oliver Upton
---
Previously any PMU overflow interrupt that fired while a VCPU was
loaded was recorded as a guest event whether it truly was or not. This
resulted in nonsense perf recordings that did not honor
perf_event_attr.exclude_guest and recorded guest IPs where it should
have recorded host IPs.
Rework the s
v7:
* Refactor th misc_flags check in patch 4 and 5 for more clarity
v6:
https://lore.kernel.org/all/20241105195603.2317483-1-coltonle...@google.com/
v5:
https://lore.kernel.org/all/20240920174740.781614-1-coltonle...@google.com/
v4:
https://lore.kernel.org/kvm/20240919190750.4163977-1-coltonle.
Make sure powerpc uses the arch-specific function now that those have
been reorganized.
Signed-off-by: Colton Lewis
Acked-by: Madhavan Srinivasan
Reviewed-by: Oliver Upton
---
arch/powerpc/perf/callchain.c| 2 +-
arch/powerpc/perf/callchain_32.c | 2 +-
arch/powerpc/perf/callchain_64.c | 2
Hello Andrew,
On Thu, 7 Nov 2024 18:49:00 +0100
Andrew Lunn wrote:
> > + if (phydev)
> > + phy_ethtool_get_wol(phydev, wol);
> > +
> > if (qe_alive_during_sleep())
> > wol->supported |= WAKE_MAGIC;
>
> So get WoL will return whatever methods the PHY supports, plus
Hello Russell,
On Thu, 7 Nov 2024 17:51:05 +
"Russell King (Oracle)" wrote:
> On Thu, Nov 07, 2024 at 06:02:49PM +0100, Maxime Chevallier wrote:
> > Preparing the phylink conversion, split the adjust_link callbaclk, by
> > clearly separating the mac configuration, link_up and link_down phase
On Tue, Nov 05, 2024 at 07:55:58PM +, Colton Lewis wrote:
> For arm's implementation, perf_instruction_pointer() and
> perf_misc_flags() are equivalent to the generic versions in
> include/linux/perf_event.h so arch/arm doesn't need to provide its
> own versions. Drop them here.
>
> Signed-off
On Thu, Nov 07, 2024 at 06:02:49PM +0100, Maxime Chevallier wrote:
> Preparing the phylink conversion, split the adjust_link callbaclk, by
> clearly separating the mac configuration, link_up and link_down phases.
I'm not entirely sure what the point of this patch is, given that in
patch 7, all thi
On Thu, Nov 07, 2024 at 10:26:46PM +1100, Michael Ellerman wrote:
> From: Arnd Bergmann
>
> Unlike all other arches, powerpc doesn't allow the user to override CPP,
> because it sets it unconditionally in the arch Makefile. This can lead
> to strange build failures.
>
> Instead add the required
On Thu, Nov 07, 2024 at 06:02:53PM +0100, Maxime Chevallier wrote:
> The preamble length can be configured in ucc_geth, however it just
> ends-up always being configured to 7 bytes, as nothing ever changes the
> default value of 7.
>
> Make that value the default value when the MACCFG2 register ge
On Thu, Nov 07, 2024 at 06:02:52PM +0100, Maxime Chevallier wrote:
> The frame length check is configured when the phy interface is setup.
> However, it's configured according to an internal flag that is always
> false. So, just make so that we disable the relevant bit in the MACCFG2
> register upo
On Thu, Nov 07, 2024 at 06:02:51PM +0100, Maxime Chevallier wrote:
> The get/set_wol ethtool ops rely on querying the PHY for its WoL
> capabilities, checking for the presence of a PHY and a PHY interrupts
> isn't enough. Address that by cleaning up the WoL configuration
> sequence.
>
> Signed-off
On Thu, Nov 07, 2024 at 06:02:48PM +0100, Maxime Chevallier wrote:
> In april 2007, ucc_geth was converted to phylib with :
>
> commit 728de4c927a3 ("ucc_geth: migrate ucc_geth to phylib").
>
> In that commit, the device-tree property "interface", that could be used to
> retrieve the PHY interfac
On Thu, Nov 07, 2024 at 06:02:50PM +0100, Maxime Chevallier wrote:
> As this driver pre-dates phylib, it uses a private pointer to get a
> reference to the attached phy_device. Drop that pointer and use the
> netdev's pointer instead.
>
> Signed-off-by: Maxime Chevallier
Reviewed-by: Andrew Lunn
On Thu, Nov 07, 2024 at 06:02:49PM +0100, Maxime Chevallier wrote:
> Preparing the phylink conversion, split the adjust_link callbaclk, by
> clearly separating the mac configuration, link_up and link_down phases.
>
> Signed-off-by: Maxime Chevallier
Reviewed-by: Andrew Lunn
Andrew
On 10/30/24 13:54, Yicong Yang wrote:
From: Yicong Yang
For ACPI we'll build the topology from PPTT and we cannot directly
get the SMT number of each core. Instead using a temporary xarray
to record the heterogeneous information (from ACPI_PPTT_ACPI_IDENTICAL)
and SMT information of the firs
On 10/31/24 13:17, Yicong Yang wrote:
On 2024/10/30 22:55, Thomas Gleixner wrote:
On Wed, Oct 30 2024 at 20:54, Yicong Yang wrote:
+#ifndef topology_is_primary_thread
+#define topology_is_primary_thread topology_is_primary_thread
Please do not glue defines and functions together w/o a n
On Sun, Nov 03 2024, Thomas Weißschuh wrote:
> The is_bin_visible() callbacks should not modify the struct
> bin_attribute passed as argument.
> Enforce this by marking the argument as const.
>
> As there are not many callback implementers perform this change
> throughout the tree at once.
>
> Sig
Booting a KASAN=y kernel with the recently added ftrace out-of-line
support causes a warning at boot:
[ cut here ]
Stub index overflow (1729 > 1728)
WARNING: CPU: 0 PID: 0 at arch/powerpc/kernel/trace/ftrace.c:209
ftrace_init_nop+0x408/0x444
...
NIP ftrace_init_n
The preamble length can be configured in ucc_geth, however it just
ends-up always being configured to 7 bytes, as nothing ever changes the
default value of 7.
Make that value the default value when the MACCFG2 register gets
initialized, and remove the code to configure that value altogether.
Sign
As this driver pre-dates phylib, it uses a private pointer to get a
reference to the attached phy_device. Drop that pointer and use the
netdev's pointer instead.
Signed-off-by: Maxime Chevallier
---
drivers/net/ethernet/freescale/ucc_geth.c | 27 ---
drivers/net/ethernet/free
In april 2007, ucc_geth was converted to phylib with :
commit 728de4c927a3 ("ucc_geth: migrate ucc_geth to phylib").
In that commit, the device-tree property "interface", that could be used to
retrieve the PHY interface mode was deprecated.
DTS files that still used that property were converted
The get/set_wol ethtool ops rely on querying the PHY for its WoL
capabilities, checking for the presence of a PHY and a PHY interrupts
isn't enough. Address that by cleaning up the WoL configuration
sequence.
Signed-off-by: Maxime Chevallier
---
.../net/ethernet/freescale/ucc_geth_ethtool.c | 19
The frame length check is configured when the phy interface is setup.
However, it's configured according to an internal flag that is always
false. So, just make so that we disable the relevant bit in the MACCFG2
register upon accessing it for other MAC configuration operations.
Signed-off-by: Maxi
Hello everyone,
This series aims at converting ucc_geth to phylink, one one part for
better SFP handling, and on the other hand as a preparation for complex
topology support with multiple PHYs being attached, which could involve
phylink. Even without considering the multi-phy case, this series bri
ucc_geth is quite capable in terms of supported interfaces, and even
includes an externally controlled PCS (well, TBI). Port that driver to
phylink.
Signed-off-by: Maxime Chevallier
---
drivers/net/ethernet/freescale/Kconfig| 3 +-
drivers/net/ethernet/freescale/ucc_geth.c | 516 ++
Preparing the phylink conversion, split the adjust_link callbaclk, by
clearly separating the mac configuration, link_up and link_down phases.
Signed-off-by: Maxime Chevallier
---
drivers/net/ethernet/freescale/ucc_geth.c | 180 +++---
1 file changed, 93 insertions(+), 87 deletion
On Sun, Nov 03, 2024 at 05:03:32PM +, Thomas Weißschuh wrote:
> Stop abusing the is_bin_visible() callback to calculate the attribute
> size. Instead use the new, dedicated bin_size() one.
>
> Signed-off-by: Thomas Weißschuh
Acked-by: Bjorn Helgaas
Thanks for doing this!
> ---
> drivers/
From: Arnd Bergmann
Unlike all other arches, powerpc doesn't allow the user to override CPP,
because it sets it unconditionally in the arch Makefile. This can lead
to strange build failures.
Instead add the required flags to KBUILD_CPPFLAGS, which are passed
to CPP, CC and AS invocations by the
On Wed, Nov 06, 2024 at 11:11:23PM -0700, Abhinav Saxena wrote:
> Fix unintentional word repetitions in devicetree binding documentation:
> - usb.txt: Fix repeated "two"
> - mvebu-devbus.txt: Fix repeated "from"
> - gpio.txt: Fix repeated "Both"
> - pinctrl-bindings.txt: Fix repeated "device"
> - c
On Thu, Nov 07, 2024 at 12:07:46PM +0100, Krzysztof Kozlowski wrote:
> On Wed, Nov 06, 2024 at 11:11:24PM -0700, Abhinav Saxena wrote:
> > Remove trailing whitespace from devicetree binding documentation files:
> > - regulator/regulator-max77620.txt
> > - interrupt-controller/nvidia,tegra20-ictlr.t
Hello,
[...]
> > There exist the sysfs_update_groups(), but the BAR resource sysfs objects
> > are currently, at least not yet, added to any attribute group.
>
> then maybe they should be added to one :)
Yeah. There is work in progress that will take care of some of this.
Krzysztof
Michal Suchanek writes:
> A hwcap feature bit is passed to cpu_has_feature, resulting in testing
> for CPU_FTR_MMCRA instead of the 3.1 platform revision.
Ouch. Good find.
Notably all IBM Power CPUs have MMCRA set, so the feature test is
essentially a nop.
> Fixes: c954b252dee9 ("crypto: powerp
Le 07/11/2024 à 12:29, Michael Ellerman a écrit :
Yang Li writes:
The header files linux/mem_encrypt.h is included twice in svm.c,
so one inclusion of each can be removed.
Reported-by: Abaci Robot
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=11750
Signed-off-by: Yang Li
---
ar
On Thu, Nov 07, 2024 at 10:54:29PM +1100, Michael Ellerman wrote:
> Gautam Menghani writes:
> > As per the kernel documentation[1], hardlockup detector should be
> > disabled in KVM guests as it may give false positives. On PPC, hardlockup
> > detector is broken inside KVM guests because disable_h
Applied the below patch to 6.12.0-rc6-next20241106 and issue is not
seen. Results look good to me.
[root@ltcden8-lp5 ~]# uname -r
6.12.0-rc6-next-20241106-2-gf374fbb4ee1a
[root@ltcden8-lp5 ~]#
Please add below tag.
Tested-by: Venkat Rao Bagalkote
On 07/11/24 11:28 am, Sourabh Jain wrote:
Gautam Menghani writes:
> As per the kernel documentation[1], hardlockup detector should be
> disabled in KVM guests as it may give false positives. On PPC, hardlockup
> detector is broken inside KVM guests because disable_hardlockup_detector()
Isn't it the opposite? Inside KVM guests, the hardl
"Rob Herring (Arm)" writes:
> While OpenFirmware originally allowed walking parent nodes and default
> root values for #address-cells and #size-cells, FDT has long required
> explicit values. It's been a warning in dtc for the root node since the
> beginning (2005) and for any parent node since 20
On Wed, Nov 06, 2024 at 11:11:24PM -0700, Abhinav Saxena wrote:
> Remove trailing whitespace from devicetree binding documentation files:
> - regulator/regulator-max77620.txt
> - interrupt-controller/nvidia,tegra20-ictlr.txt
> - interrupt-controller/msi.txt
>
> No functional changes. Issues detect
On Wed, Nov 06, 2024 at 11:11:23PM -0700, Abhinav Saxena wrote:
> Fix unintentional word repetitions in devicetree binding documentation:
> - usb.txt: Fix repeated "two"
> - mvebu-devbus.txt: Fix repeated "from"
> - gpio.txt: Fix repeated "Both"
> - pinctrl-bindings.txt: Fix repeated "device"
> - c
On Thu, 10 Oct 2024 00:17:57 +0200, Christophe Leroy wrote:
> On powerpc64 as shown below by readelf, vDSO functions symbols have
> type NOTYPE.
>
> $ powerpc64-linux-gnu-readelf -a arch/powerpc/kernel/vdso/vdso64.so.dbg
> ELF Header:
> Magic: 7f 45 4c 46 02 02 01 00 00 00 00 00 00 00 00 00
>
On Wed, 09 Oct 2024 16:38:06 +1100, Michael Ellerman wrote:
> The help text refers to lilo, but the install script does not run lilo
> and never has. The reference to lilo seems to have come originally from
> arch/ppc/Makefile, but it was not true there either.
>
> Remove it.
>
>
> [...]
Applie
On Fri, 18 Oct 2024 21:47:55 +0530, Ritesh Harjani (IBM) wrote:
> We anyway don't use any return values from fadump_cma_init(). Since
> fadump_reserve_mem() from where fadump_cma_init() gets called today,
> already has the required checks.
> This patch makes this function return type as void. Let's
On Wed, 09 Oct 2024 16:17:00 +1100, Michael Ellerman wrote:
> The last use of IPI_PRIORITY in asm was removed in commit 37f55d30df2e
> ("KVM: PPC: Book3S HV: Convert kvmppc_read_intr to a C function").
>
>
Applied to powerpc/next.
[1/1] powerpc/64: Drop IPI_PRIORITY from asm-offsets
https
On Wed, 02 Oct 2024 10:39:28 +0200, Christophe Leroy wrote:
> The page containing VDSO time data is swapped with the one containing
> TIME namespace data when a process uses a non-root time namespace.
> For other data like powerpc specific data and RNG data, it means
> tracking whether time namespa
On Fri, 18 Oct 2024 22:59:41 +0530, Ritesh Harjani (IBM) wrote:
> v2 -> v3:
>
> 1. Addressed review comments from Christophe in patch-1: To check for
>is_kfence_address before doing search in exception tables.
>(Thanks for the review!)
>
> 2. Separate out patch-1, which will n
On Sun, 13 Oct 2024 21:29:57 +1100, Michael Ellerman wrote:
> The maple platform was added in 2004 [1], to support the "Maple" 970FX
> evaluation board.
>
> It was later used for IBM JS20/JS21 machines, as well as the Bimini
> machine, aka "Yellow Dog Powerstation".
>
> Sadly all those machines h
On Wed, 09 Oct 2024 12:26:07 -0700, Nathan Chancellor wrote:
> This series prepares the powerpc Kconfig and Kbuild files for clang's
> per-task stack protector support. clang requires
> '-mstack-protector-guard-offset' to always be passed with the other
> '-mstack-protector-guard' flags, which does
On Mon, 19 Aug 2024 22:24:01 +1000, Michael Ellerman wrote:
> The dtl_access_lock needs to be a rw_sempahore, a sleeping lock, because
> the code calls kmalloc() while holding it, which can sleep:
>
> # echo 1 > /proc/powerpc/vcpudispatch_stats
> BUG: sleeping function called from invalid cont
On Wed, 09 Oct 2024 16:18:25 +1100, Michael Ellerman wrote:
> Drop the include of seq_file.h in machdep.h, replace it with a forward
> declaration of struct seq_file, which is all that's required.
>
> Add direct includes of seq_file.h to some files that were getting
> seq_file.h via machdep.h.
>
67 matches
Mail list logo