On Sat, Sep 25 2021 at 15:30, Thomas Gleixner wrote:
> On Fri, Sep 24 2021 at 01:07, Thomas Gleixner wrote:
> The obvious question is: What is the value of clearing UINV?
>
> Absolutely none. That notification vector cannot be used for anything
> else, so why would the OS be interested to see it ever? This is about
> user space interupts, right?
>
> UINV should be set _ONCE_ when CR4.UINTR is enabled and not be touched
> by XSAVES/XRSTORS at all. Any delivery of this vector to the OS should
> be considered a hardware bug.
After decoding the documentation (sigh) and staring at the implications of
keeping UINV armed, I can see the point vs. the UPID lifetime issue when
a task gets scheduled out and migrated to a different CPU.
Not the most pretty solution, but as there needs to be some invalidation
which needs to be undone on return to user space it probably does not
matter much.
As the whole thing is tightly coupled to XSAVES/RSTORS we need to
integrate it into that machinery and not pretend that it's something
half independent.
That means we have to handle the setting of the SN bit in UPID whenever
XSTATE is saved either during context switch, when the kernel uses the
FPU or in other places (signals, fpu_clone ...). They all end up in
save_fpregs_to_fpstate() so that might be the place to look at.
While talking about that: fpu_clone() has to invalidate the UINTR state
in the clone's xstate after the memcpy() or xsaves() operation.
Also the restore portion on the way back to user space has to be coupled
more tightly:
arch_exit_to_user_mode_prepare()
{
...
if (unlikely(ti_work & _TIF_UPID))
uintr_restore_upid(ti_work & _TIF_NEED_FPU_LOAD);
if (unlikely(ti_work & _TIF_NEED_FPU_LOAD))
switch_fpu_return();
}
upid_set_ndst(upid)
{
apicid = __this_cpu_read(x86_cpu_to_apicid);
if (x2apic_enabled())
upid->ndst.x2apic = apicid;
else
upid->ndst.apic = apicid;
}
uintr_restore_upid(bool xrstors_pending)
{
clear_thread_flag(TIF_UPID);
// Update destination
upid_set_ndst(upid);
// Do we need something stronger here?
barrier();
clear_bit(SN, upid->status);
// Any SENDUIPI after this point sends to this CPU
// Any bit which was set in upid->pir after SN was set
// and/or UINV was cleared by XSAVES up to the point
// where SN was cleared above is not reflected in UIRR.
// As this runs with interrupts disabled the current state
// of upid->pir can be read and used for restore. A SENDUIPI
// which sets a bit in upid->pir after that read will send
// the notification vector which is going to be handled once
// the task reenables interrupts on return to user space.
// If the SENDUIPI set the bit before the read then the
// notification vector handling will just observe the same
// PIR state.
// Needs to be a locked access as there might be a
// concurrent SENDUIPI modiying it.
pir = read_locked(upid->pir);
if (xrstors_pending)) {
// Update the saved xstate for xrstors
current->xstate.uintr.uinv = UINTR_NOTIFICATION_VECTOR;
current->xstate.uintr.uirr = pir;
} else {
// Manually restore UIRR and UINV
wrmsrl(IA32_UINTR_RR, pir);
misc.val64 = 0;
misc.uittsz = current->uintr->uittsz;
misc.uinv = UINTR_NOTIFICATION_VECTOR;
wrmsrl(IA32_UINTR_MISC, misc.val64);
}
}
That's how I deciphered the documentation and I don't think this is far
from reality, but I might be wrong as usual.
Hmm?
Thanks,
tglx
