When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected,
cpu_max_bits_warn() generates a runtime warning similar as below while
we show /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)
instead of NR_CPUS to iterate CPUs.
[3.052463] [ cut here ]
When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected,
cpu_max_bits_warn() generates a runtime warning similar as below while
we show /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)
instead of NR_CPUS to iterate CPUs.
[3.052463] [ cut here ]
When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected,
cpu_max_bits_warn() generates a runtime warning similar as below while
we show /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)
instead of NR_CPUS to iterate CPUs.
[3.052463] [ cut here ]
When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected,
cpu_max_bits_warn() generates a runtime warning similar as below while
we show /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)
instead of NR_CPUS to iterate CPUs.
[3.052463] [ cut here ]
When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected,
cpu_max_bits_warn() generates a runtime warning similar as below while
we show /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)
instead of NR_CPUS to iterate CPUs.
[3.052463] [ cut here ]
When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected,
cpu_max_bits_warn() generates a runtime warning similar as below while
we show /proc/cpuinfo. Fix this by using nr_cpu_ids (the runtime limit)
instead of NR_CPUS to iterate CPUs.
[3.052463] [ cut here ]
Hi Huacai,
Thanks for your patch!
On Tue, Jul 12, 2022 at 9:53 AM Huacai Chen wrote:
> When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected,
DEBUG_PER_CPU_MAPS depends on SMP, which is not supported on m68k,
and thus cannot be enabled.
> cpu_max_bits_warn() generates a runtim
Hi, Geert,
On Tue, Jul 12, 2022 at 4:33 PM Geert Uytterhoeven wrote:
>
> Hi Huacai,
>
> Thanks for your patch!
>
> On Tue, Jul 12, 2022 at 9:53 AM Huacai Chen wrote:
> > When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected,
>
> DEBUG_PER_CPU_MAPS depends on SMP, which is not su
Hi Huacai,
On Tue, Jul 12, 2022 at 10:53 AM Huacai Chen wrote:
> On Tue, Jul 12, 2022 at 4:33 PM Geert Uytterhoeven
> wrote:
> > On Tue, Jul 12, 2022 at 9:53 AM Huacai Chen wrote:
> > > When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS is selected,
> >
> > DEBUG_PER_CPU_MAPS depends o
Hi, Geert,
On Tue, Jul 12, 2022 at 5:01 PM Geert Uytterhoeven wrote:
>
> Hi Huacai,
>
> On Tue, Jul 12, 2022 at 10:53 AM Huacai Chen wrote:
> > On Tue, Jul 12, 2022 at 4:33 PM Geert Uytterhoeven
> > wrote:
> > > On Tue, Jul 12, 2022 at 9:53 AM Huacai Chen
> > > wrote:
> > > > When CONFIG_CPU
Hi Huacai,
On Tue, Jul 12, 2022 at 11:08 AM Huacai Chen wrote:
> On Tue, Jul 12, 2022 at 5:01 PM Geert Uytterhoeven
> wrote:
> > On Tue, Jul 12, 2022 at 10:53 AM Huacai Chen wrote:
> > > On Tue, Jul 12, 2022 at 4:33 PM Geert Uytterhoeven
> > > wrote:
> > > > On Tue, Jul 12, 2022 at 9:53 AM H
Hi Geert and Huacai,
On 2022/7/12 17:13, Geert Uytterhoeven wrote:
Hi Huacai,
On Tue, Jul 12, 2022 at 11:08 AM Huacai Chen wrote:
On Tue, Jul 12, 2022 at 5:01 PM Geert Uytterhoeven wrote:
On Tue, Jul 12, 2022 at 10:53 AM Huacai Chen wrote:
On Tue, Jul 12, 2022 at 4:33 PM Geert Uytterhoeve
On Fri, Jul 1, 2022 at 11:16 AM David Gow wrote:
>
> From: Patricia Alfonso
>
> Make KASAN run on User Mode Linux on x86_64.
>
> The UML-specific KASAN initializer uses mmap to map the ~16TB of shadow
> memory to the location defined by KASAN_SHADOW_OFFSET. kasan_init()
> utilizes constructors t
13 matches
Mail list logo
