Having done surgery in the past to the ASID management code, this sounds
a much more rational explanation of the observed problem. Your proposed mod
sounds like it might work, but local_flush_tlb_mm() is implemented in
drop_mmu_context(), which only does what you want if the CPU executing the
code is *not* one of the CPUs participating in the memory map. Otherwise,
instead of clearing the ASID in the table, it allocates a new one. I
have a concern
that this may re-randomize things in a way that will solve your problem
of the time, but not always.
Now that we have a better understanding of the failure, your initial notion
of *not* restarting the ASID sequence on a hotplug insertion doesn't seem
as crazy - it's certainly the zen "doing by doing nothing" way to go,
the iterative overhead of walking the full process table. But as we
it has the downside of requiring new state infrastructure for tracking
and we'd want to be sure that it's well behaved in the case where we have a
post-initial-boot hotplug event that brings a CPU online that has never been
initialized. To take that tack, we'd need a per-CPU-slot bit which says
a valid ASID sequence, thank you", which is checked in per_cpu_trap_init()
(or some other appropriate hook), and the ASID "cache" is initialized only
if it's needed, which *might* be on a hotplug.
On 11/29/10 17:35, Maksim Rayskiy wrote:
Thank you for your suggestions. I think I see where the conflict is
If a usermode process during its lifetime migrates between cpus (TPs
in my case) it has a non-zero value in cpu_context(cpu, mm) fields
(asid in mips case) for all cpus it has ever run on. Moving from one
cpu to another does not clear cpu_context. This is okay as long as all
cpus are running. When cpu hotplug occurs, cpu_context for this
threads running on cpu being stopped does not get cleared either. It
might have been cleared if local_flush_tlb_mm() is called for these
threads, but I do not see it happening.
As a result, after secondary cpu is brought online, some processes
already have stale asid values stored in their mm structures. One of
these processes in my case happens to be 'init' with asid=0x101, which
causes a conflict because next asid value selected by
get_new_mmu_context() is ASID_FIRST_VERSION+ASID_INC=0x101 as well.
Basically, at this point there is a discrepancy between global
(per-cpu) asid_cache value and some individual thread asid values
stored in mm->context.asid[cpu] fields.
Just adding a simple code to call drop_mmu_context() on every thread
which has ever run on the cpu getting offlined solves my problem. It
does not require distinguishing warm boot from cold as before.
Something like (called from hotplugged cpu)
struct task_struct *p;
I can generate a patch if you think it is a more viable solution.
On Thu, Nov 25, 2010 at 7:57 AM, Kevin D. Kissell<email@example.com> wrote:
This approach certainly makes per_cpu_trap_init() more readable and
maintainable, but it has the downside of creating state and infrastructure
that have footprints elsewhere that add to global cruft and complexity.
Note that your patch, as written, wouldn't solve your problem, because it
doesn't include the code that would actually set and clear the elements of
your cpu_warm_boot array. If we do need to pay attention to warm boot
state elsewhere in the kernel (Does any other architecture? That should be
a clue...), then some bits in memory like that should perhaps be defined
(though I'd wonder why it couldn't be a bit in some existing per-CPU state
entity like cpu_data). Otherwise, as I said earlier, the cleanest
approach strikes me as one of resetting the value of EntryHi as well as the
ASID cache when the hotplug event takes place. The cleanest possible
outcome would be if one could *move* the reset initialization of EntryHi
from wherever it is now to per_cpu_trap_init(), so there would be *zero* net
additional code, but it may be (it's Thanksgiving and I'm limited in time
and internet access, so I can't really go look for you) that it's
initialized as a side effect of something that happens repeatedly, such that
actually *moving* it would be dangerous. But if you have the time, try
setting up EntryHi explicitly and unconditionally in per_cpu_trap_init() and
see if it doesn't solve your initial problem.
Happy Holiday to you all,
On 11/24/10 7:03 PM, Maksim Rayskiy wrote:
I certainly agree that it is a bad idea to look at the current value
of asid_cache when figuring out if it is a warm or cold boot.
I could not tell how the code ended up with this entryHi value after
the hotplug. So, I can only address the simplest portion of issues you
How about we add a variable to tell warm restart from cold and
preserve asid_cache across hotplug event. It is not much of an
improvement over the original code, I must admit.
Signed-off-by: Maksim Rayskiy<firstname.lastname@example.org>
diff --git a/arch/mips/kernel/traps.c b/arch/mips/kernel/traps.c
index d83f325..9116adb 100644
@@ -1489,6 +1489,8 @@ static int __init ulri_disable(char *s)
+static int cpu_warm_boot[NR_CPUS];
void __cpuinit per_cpu_trap_init(void)
unsigned int cpu = smp_processor_id();
@@ -1577,7 +1579,9 @@ void __cpuinit per_cpu_trap_init(void)
#endif /* CONFIG_MIPS_MT_SMTC */
- cpu_data[cpu].asid_cache = ASID_FIRST_VERSION;
+ if (!cpu_warm_boot[cpu])
+ cpu_data[cpu].asid_cache = ASID_FIRST_VERSION;
+ cpu_warm_boot[cpu] = 1;
On Mon, Nov 22, 2010 at 1:34 PM, Kevin D. Kissell<email@example.com>
On 11/21/10 19:41, Ralf Baechle wrote:
Need to think a little about potencial consequences of your suggested
patch. It seems ok. Kevin, what do you think?
Since you ask, while I would imagine that Maksim's patch works fine for
I'm not sure that it's really the right fix. I never did succeed in
CPU hotplugging working back in the 2.6.18 days, so I don't know as much
about it as I'd like, but if per_cpu_trap_init() needs to be invoked on a
hot plugin event, and if its behavior needs to be different , I'd really,
really prefer to see that state propagated explicitly, rather than
it from whatever happens to be in cache/memory at
But beyond that, if the problem arises because setting
cpu_data[cpu].asid_cache to a known initial state on a plugin event can
conflict with the residual content of EntryHi, rather than creating a
special case where we don't initialize the ASID cache, since we seem to
(re)initializing a lot of other privileged state, why aren't we also
a known sane initial EntryHi value? Wouldn't that be a cleaner fix?
I don't mean that as a rhetorical question - there may be very good
to let EntryHi values persist across hot unplug/plug events. I just
imagine them offhand over coffee.)