On Mon, May 14, 2018 at 07:40:21AM +, Masaki Tachibana wrote:
> Hi Thadeu,
>
> So sorry for the late reply.
> I will merge the patch into V1.6.4 with the following modifying
> because I have already accepted "Always use bigger SECTION_MAP_MASK" patch.
>
> 63,68c63,64
> < if
Hi Thadeu,
So sorry for the late reply.
I will merge the patch into V1.6.4 with the following modifying
because I have already accepted "Always use bigger SECTION_MAP_MASK" patch.
63,68c63,64
< if (info->kernel_version < KERNEL_VERSION(4, 13, 0))
< - map &=
Hi Thadeu,
Sorry for the late reply.
"handle mem_section as either a pointer or an array" patch and
"Always use bigger SECTION_MAP_MASK" patch modify the same line.
I would like to reply about both patches by the end of the next week.
Thanks
Tachibana
> -Original Message-
> From:
Any comments or reviews on the patch below?
Thanks.
Cascardo.
On Mon, Feb 19, 2018 at 05:04:59PM -0300, Thadeu Lima de Souza Cascardo wrote:
> Some kernel versions that have been recently shipped have mem_section point to
> a pointer to the array, instead of pointing directly to the array. That
Some kernel versions that have been recently shipped have mem_section point to
a pointer to the array, instead of pointing directly to the array. That only
happens on SPARSEMEM_EXTREME configurations.
As dwarf information might not be present that would have allowed us to detect
which type it is,