OK, so it is OK for send kernel message to take OS core IDs. Yes, the __ version of the send IPI does the conversion. Undoing some code ...
On Fri, Dec 4, 2015 at 10:36 AM, Barret Rhoden <[email protected]> wrote: > On 2015-12-04 at 10:03 "'Davide Libenzi' via Akaros" > <[email protected]> wrote: > > This opens the question of what do we mean for core ID (as in > > core_id() result) within the kernel. > > We do use this in many places: > > core_id() is the "OS" core_id. the distinction between the hardware > and the OS core_id is an arch-dependent thing. > > > send_kernel_message(core_id(), ...); > > > > And the send_kernel_message() API uses that core ID directly as LAPIC > > ID in send IPI. > > send_ipi() takes an os_core_id. the x86-specific __send_ipi() takes a > HW coreid. > > > So there seem to be an implicit 1:1 between the logical core IDs, and > > the LAPIC IDs AFAICS. > > if there is somewhere, then it's a bug. > > -- > You received this message because you are subscribed to the Google Groups > "Akaros" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
