Add the NXP (nee Freescale) e5500 and e6500 to the ISA versions
documentation.
Signed-off-by: Michael Ellerman
---
Documentation/powerpc/isa-versions.rst | 8
1 file changed, 8 insertions(+)
diff --git a/Documentation/powerpc/isa-versions.rst
b/Documentation/powerpc/isa-versions.rst
i
When building ppc64_book3e_allmodconfig the build fails with:
arch/powerpc/kexec/file_load_64.c:1063:14: error: implicit declaration of
function ‘firmware_has_feature’
1063 | if (!firmware_has_feature(FW_FEATURE_LPAR))
| ^~~~
Add a direct include
Christophe Leroy writes:
> Le 16/07/2022 à 18:50, shaom Deng a écrit :
>> [Vous ne recevez pas souvent de courriers de dengshao...@cdjrlc.com.
>> Découvrez pourquoi ceci est important à
>> https://aka.ms/LearnAboutSenderIdentification ]
>>
>> delete the repeated word "that" in comments
>>
>> S
successfully.
More configs may be tested in the coming days.
gcc tested configs:
um x86_64_defconfig
um i386_defconfig
arc randconfig-r043-20220802
x86_64 defconfig
x86_64 randconfig
i386 randconfig-a004-20220801
i386 randconfig-a006-20220801
hexagon randconfig-r045-20220801
hexagon randconfig-r045-20220802
s390 randconfig-r044-20220802
hexagon randconfig-r041-20220802
riscv
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
merge
branch HEAD: e538227647dc2a96ae640e25043e04cf5f735189 Automatic merge of
'master' into merge (2022-08-01 11:37)
elapsed time: 716m
configs tested: 61
configs skipped: 2
The following configs have been built s
Michael and Michal,
On Tue, 2022-08-02 at 12:59 +1000, Michael Ellerman wrote:
> I don't think "arch" is the right level of abstraction here.
>
> There isn't a standard way to get these variables across a given
> arch,
> they're not defined in the architecture specification etc.
>
> As demonst
On 7/27/22 2:37 AM, Zhuo Chen wrote:
>>
> Do you mean changing "if ((host->native_aer || pcie_ports_native) && aer)"
> into "if (pcie_aer_is_native(dev) && aer)" ?
> I thought changing into "if (pcie_aer_is_native(dev))" before.
>
> One another doubt. Not every pci device support aer. When dev
On Tuesday 02 August 2022 11:02:36 Christophe Leroy wrote:
> Commit 9401f4e46cf6 ("powerpc: Use lwarx/ldarx directly instead of
> PPC_LWARX/LDARX macros") properly handled the eh field of lwarx
> in asm/bitops.h but failed to clear it for PPC32 in
> asm/simple_spinlock.h
>
> So, do as in arch_atom
Hi!
On Tue, Aug 02, 2022 at 11:02:36AM +0200, Christophe Leroy wrote:
> Commit 9401f4e46cf6 ("powerpc: Use lwarx/ldarx directly instead of
> PPC_LWARX/LDARX macros") properly handled the eh field of lwarx
> in asm/bitops.h but failed to clear it for PPC32 in
> asm/simple_spinlock.h
>
> So, do as
On Tue, Aug 2, 2022 at 5:09 PM Miguel Ojeda
wrote:
>
> Yeah, patch 17, exactly (patch 11 is the `alloc` import). I have asked
> Konstantin privately about them.
The patches are showing up now in lore -- not sure if it was just a
delay (which would be consistent with the lack of bounce) or somebod
On Tue, Aug 2, 2022 at 4:01 PM Matthew Wilcox wrote:
>
> No objections to any of this. I love the idea of being able to write
> filesystems in Rust. I just think it would go more smoothly if
> linux-fsdevel were involved more closely so people at least have the
> option of being able to follow d
On Tue, Aug 2, 2022 at 3:48 PM Christoph Hellwig wrote:
>
> handwaiving and pointing to git trees is not how Linux development
> works. Please make sure all the patches go to the relevant lists
> and maintainers first, and actually do have ACKs.
Which hand-waving? In fact, we were requested to d
Le 16/07/2022 à 18:50, shaom Deng a écrit :
> [Vous ne recevez pas souvent de courriers de dengshao...@cdjrlc.com.
> Découvrez pourquoi ceci est important à
> https://aka.ms/LearnAboutSenderIdentification ]
>
> delete the repeated word "that" in comments
>
> Signed-off-by: shaom Deng
> ---
>
On Tue, Aug 02, 2022 at 03:45:50PM +0200, Miguel Ojeda wrote:
> Hi Willy,
>
> On Tue, Aug 2, 2022 at 2:26 PM Matthew Wilcox wrote:
> >
> > None of this (afaict) has been discussed on linux-fsdevel. And I may
> > have missed somethiing, but I don't see the fs module in this series
> > of patches.
Miguel,
handwaiving and pointing to git trees is not how Linux development
works. Please make sure all the patches go to the relevant lists
and maintainers first, and actually do have ACKs.
Hi Willy,
On Tue, Aug 2, 2022 at 2:26 PM Matthew Wilcox wrote:
>
> None of this (afaict) has been discussed on linux-fsdevel. And I may
> have missed somethiing, but I don't see the fs module in this series
> of patches. Could linux-fsdevel be cc'd on the development of Rust
> support for files
On Tue, Aug 02, 2022 at 03:49:47AM +0200, Miguel Ojeda wrote:
> Some of the improvements to the abstractions and example drivers are:
>
> - Filesystem support (`fs` module), including:
>
> + `INode` type (which wraps `struct inode`).
> + `DEntry` type (which wraps `struct dentry`).
On Tuesday 02 August 2022 20:57:23 Michael Ellerman wrote:
> The recent change to the PHB numbering logic has a logic error in the
> handling of "ibm,opal-phbid".
>
> When an "ibm,opal-phbid" property is present, &prop is written to and
> ret is set to zero.
>
> The following call to of_alias_get
Christophe Leroy writes:
> Commit 4d5c5bad5193 ("powerpc: Remove asm/prom.h from asm/mpc52xx.h
> and asm/pci.h") that cleans up powerpc's asm/prom.h leads to build
> errors in ppc4xx_edac.c due to missing header. Include required
> header directly to avoid the build failure.
>
> Reported-by: kerne
On Mon, 1 Aug 2022 21:37:46 +1000, Michael Ellerman wrote:
> GCC 12 thinks that `actual` might be used uninitialised. It's not, the
> use is guarded by `bad_mmcr2` which is only set to true at the same
> point where `actual` is initialised.
>
> cycles_with_mmcr2_test.c: In function ‘cycles_with_
On Sun, 5 Jun 2022 09:32:23 +0400, Miaoqian Lin wrote:
> of_find_node_by_path() returns a node pointer with
> refcount incremented, we should use of_node_put() on it when done.
> Add missing of_node_put() to avoid refcount leak.
>
>
Applied to powerpc/next.
[1/1] powerpc/xive: Fix refcount leak
On Tue, 26 Jul 2022 09:57:47 +0800, zhouzho...@gmail.com wrote:
> From: Zhouyi Zhou
>
> In ppc 64, invoke jump_label_init in setup_feature_keys is too late
> because static key will be used in subroutine of parse_early_param
> which is again subroutine of early_init_devtree.
>
> So we invoke jum
On Fri, 3 Jun 2022 16:15:42 +0400, Miaoqian Lin wrote:
> of_find_node_by_path() returns remote device nodepointer with
> refcount incremented, we should use of_node_put() on it when done.
> Add missing of_node_put() to avoid refcount leak.
>
>
Applied to powerpc/next.
[1/1] powerpc/spufs: Fix r
On Sun, 5 Jun 2022 10:51:29 +0400, Miaoqian Lin wrote:
> of_get_next_parent() returns a node pointer with refcount incremented,
> we should use of_node_put() on it when not need anymore.
> Add missing of_node_put() in the error path to avoid refcount leak.
>
>
Applied to powerpc/next.
[1/1] pow
On Thu, 28 Jul 2022 22:07:46 +0530, Athira Rajeev wrote:
> commit 6320e693d98c ("powerpc/perf: Add support for caps
> under sysfs in powerpc") added support for caps under sysfs
> in powerpc. This added caps directory to:
> /sys/bus/event_source/devices/cpu/ for power8, power9, power10
> and generi
On Mon, 11 Jul 2022 19:36:15 -0300, Murilo Opsfelder Araujo wrote:
> Minor cleanup to remove unused function and declarations.
>
> Murilo Opsfelder Araujo (2):
> KVM: PPC: Book3S HV: Remove kvmhv_p9_[set,restore]_lpcr declarations
> KVM: PPC: Book3s HV: Remove unused function kvmppc_bad_interr
On Mon, 11 Jul 2022 09:19:26 +0530, Kajol Jain wrote:
> File book3s_hv_p9_entry.c in powerpc/kvm folder consists of functions
> like freeze_pmu, switch_pmu_to_guest and switch_pmu_to_host which are
> specific to Performance Monitoring Unit(PMU) for power9 and later
> platforms.
>
> For better main
The recent change to the PHB numbering logic has a logic error in the
handling of "ibm,opal-phbid".
When an "ibm,opal-phbid" property is present, &prop is written to and
ret is set to zero.
The following call to of_alias_get_id() is skipped because ret == 0.
But then the if (ret >= 0) is true, a
Message transféré
Sujet : [PATCH v12 33/69] powerpc: remove mmap linked list walks
Date : Wed, 20 Jul 2022 02:17:54 +
De : Liam Howlett
Pour : maple-t...@lists.infradead.org ,
linux...@kvack.org , linux-ker...@vger.kernel.org
, Andrew Morton
, Hugh Dickins
Copie à : Yu
Le 20/07/2022 à 04:17, Liam Howlett a écrit :
> From: "Matthew Wilcox (Oracle)"
>
> Use the VMA iterator instead.
Can you please copy powerpc maintainers/reviewers when sending such a
patch ?
Thanks
Christophe
>
> Link:
> https://lkml.kernel.org/r/20220504011345.662299-18-liam.howl...@ora
Message transféré
Sujet : [linux-next:master 2767/10347] powerpc-linux-ld: warning: orphan
section `.init.plt' from `drivers/hid/hid-uclogic-rdesc.o' being placed
in section `.init.plt'
Date : Thu, 14 Jul 2022 03:41:45 +0800
De : kernel test robot
Pour : José Expósito
Copie
Commit 4d5c5bad5193 ("powerpc: Remove asm/prom.h from asm/mpc52xx.h
and asm/pci.h") that cleans up powerpc's asm/prom.h leads to build
errors in ppc4xx_edac.c due to missing header. Include required
header directly to avoid the build failure.
Reported-by: kernel test robot
Fixes: 4d5c5bad5193 ("p
Commit 9401f4e46cf6 ("powerpc: Use lwarx/ldarx directly instead of
PPC_LWARX/LDARX macros") properly handled the eh field of lwarx
in asm/bitops.h but failed to clear it for PPC32 in
asm/simple_spinlock.h
So, do as in arch_atomic_try_cmpxchg_lock(), set it to 1 if PPC64
but set it to 0 if PPC32. F
The eh field must remain 0 for PPC32 and is only used
by PPC64.
Don't hide that behind a macro, just leave the responsibility
to the user.
At the time being, the only users of PPC_RAW_L{WDQ}ARX are
setting the eh field to 0, so the special handling of __PPC_EH
is useless. Just take the value give
Just like first patch of this series, define a local 'eh'
in order to make the code clearer.
And IS_ENABLED() returns either 1 or 0 so no need to
do IS_ENABLED(CONFIG_PPC64) ? 1 : 0.
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/atomic.h | 3 ++-
1 file changed, 2 insertions(+),
On Tue, Aug 2, 2022 at 8:47 AM Christophe Leroy
wrote:
> Le 26/07/2022 à 15:44, Segher Boessenkool a écrit :
> > Whoops :-) We need fixes for processor implementation bugs all the
> > time of course, but this is a massive *design* bug. I'm surprised this
> > CPU still works as well as it does!
>
37 matches
Mail list logo
