On Wed, Mar 04, 2020 at 03:38:44PM +0800, Liu, Jing2 wrote:
>
> On 1/17/2020 2:26 PM, Sean Christopherson wrote:
> >TIF_FPU_NEED_LOAD can be set any time
> >control is transferred out of KVM, e.g. via IRQ->softirq, not just when
> >KVM is preempted.
>
> Hi Sean,
>
> Is this just because kernel_fpu_begin() is called during softirq? I saw the
> dump trace in 3/4 message, but didn't find out clue.
Yes, but "just" doing kernel_fpu_begin() swaps the task's (e.g. guest's in
this case) XSAVE/FPU state out of the CPU's registers.
> Could I ask where kernel_fpu_begin() is called? Or is this just a "possible"
> thing?
In the trace from patch 3, it's called by gcmaes_crypt_by_sg() to decrypt a
packet[*] during a receive action after the kernel was interruped by the
network device.
[*] I assume it's decrypting a packet, I'm not at all familiar with the
networking stack so it could be decrypting something else entirely.
> Because I just want to make sure that, kvm can use this flag to cover all
> preempt/softirq/(other?) cases?
Yes, TIF_FPU_NEED_LOAD is set any time its associated tasks's FPU state is
swapped out and needs to be reloaded before returning to userspace. For
KVM, "returning to userspace" also means entering the guest or accessing
guest state.
