Instead of ignoring the VFP registers, set the dumppcb's pcb_fpusaved
field, so that they are saved, as they may be used in the kernel, in the EFI and the crypto code. Reviewed by: andrew
This commit is contained in:
parent
7a07dfbc7c
commit
a9772d1a0e
@ -172,12 +172,11 @@ vfp_save_state(struct thread *td, struct pcb *pcb)
|
||||
|
||||
/*
|
||||
* savectx() will be called on panic with dumppcb as an argument,
|
||||
* dumppcb doesn't have pcb_fpusaved set so don't make any attempt
|
||||
* to store the VFP registers in it, we probably don't care much
|
||||
* at that point, anyway.
|
||||
* dumppcb doesn't have pcb_fpusaved set, so set it to save
|
||||
* the VFP registers.
|
||||
*/
|
||||
if (pcb->pcb_fpusaved == NULL)
|
||||
return;
|
||||
pcb->pcb_fpusaved = &pcb->pcb_fpustate;
|
||||
|
||||
if (td == NULL)
|
||||
td = curthread;
|
||||
|
Loading…
Reference in New Issue
Block a user