Rafael Herrera wrote:
>
> Mark Mokryn wrote:
> > Is it possible to build an SMP module on a machine running a UP kernel
> > (or vice versa)? We of course get unresolved symbols during module load
> > due to the smp prefix on the ksyms, and haven't seen how to get around
&
Hi,
Is it possible to build an SMP module on a machine running a UP kernel
(or vice versa)? We of course get unresolved symbols during module load
due to the smp prefix on the ksyms, and haven't seen how to get around
it. (Defining __SMP__ does not cut it, though I believe this used to
work a
Hi,
Is it possible to build an SMP module on a machine running a UP kernel
(or vice versa)? We of course get unresolved symbols during module load
due to the smp prefix on the ksyms, and haven't seen how to get around
it. (Defining __SMP__ does not cut it, though I believe this used to
work a
Rafael Herrera wrote:
Mark Mokryn wrote:
Is it possible to build an SMP module on a machine running a UP kernel
(or vice versa)? We of course get unresolved symbols during module load
due to the smp prefix on the ksyms, and haven't seen how to get around
it. (Defining __SMP__ does
ioremap_nocache does the following:
return __ioremap(offset, size, _PAGE_PCD);
However, in drivers/char/mem.c (2.4.0), we see the following:
/* On PPro and successors, PCD alone doesn't always mean
uncached because of interactions with the MTRRs. PCD | PWT
5 matches
Mail list logo