On Thu, 07 Nov 2024 11:28:16 +0530, Sourabh Jain wrote:
> Memory for passing additional parameters to fadump capture kernel
> is allocated during subsys_initcall level, using memblock. But
> as slab is already available by this time, allocation happens via
> the buddy allocator. This may work for r
Hello Ritesh
On 12/11/24 12:33, Ritesh Harjani (IBM) wrote:
Sourabh Jain writes:
From: Hari Bathini
Memory for passing additional parameters to fadump capture kernel
is allocated during subsys_initcall level, using memblock. But
as slab is already available by this time, allocation happens
Sourabh Jain writes:
> From: Hari Bathini
>
> Memory for passing additional parameters to fadump capture kernel
> is allocated during subsys_initcall level, using memblock. But
> as slab is already available by this time, allocation happens via
> the buddy allocator. This may work for radix MMU
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
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
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:
From: Hari Bathini
Memory for passing additional parameters to fadump capture kernel
is allocated during subsys_initcall level, using memblock. But
as slab is already available by this time, allocation happens via
the buddy allocator. This may work for radix MMU but is likely to
fail in most case
