Searched refs:hard (Results 1 – 21 of 21) sorted by relevance
46 struct vfp_hard_struct hard; member71 struct fp_hard_struct hard; member
65 if (thread->vfpstate.hard.cpu != cpu) in vfp_state_in_hw()83 thread->vfpstate.hard.cpu = NR_CPUS; in vfp_force_reload()111 vfp->hard.fpexc = FPEXC_EN; in vfp_thread_flush()112 vfp->hard.fpscr = FPSCR_ROUND_NEAREST; in vfp_thread_flush()114 vfp->hard.cpu = NR_CPUS; in vfp_thread_flush()136 thread->vfpstate.hard.cpu = NR_CPUS; in vfp_thread_copy()552 struct vfp_hard_struct *hwstate = &thread->vfpstate.hard; in vfp_preserve_user_clear_hwstate()590 struct vfp_hard_struct *hwstate = &thread->vfpstate.hard; in vfp_restore_user_hwstate()
22 hard lockup.
644 struct vfp_hard_struct const *vfp = &thread->vfpstate.hard; in vfp_get()671 new_vfp = thread->vfpstate.hard; in vfp_set()693 thread->vfpstate.hard = new_vfp; in vfp_set()
57 DEFINE(VFP_CPU, offsetof(union vfp_state, hard.cpu)); in main()
86 /* MCAN interrupts are hard-wired to irqs 67, 68 */
65 * "C" : hard reset
140 /* Use the thermal sensor in the hard drive */
147 * signal and hard to be dealt with in a standard way by the
1110 * watchdog provides no debugging information (compared to soft/hard
1092 * watchdog provides no debugging information (compared to soft/hard
54 for handling hard and soft interrupts. This can help avoid
41 which allows direct access to the hard drives without using
481 * that isn't a valid hard IRQ, therefore we bypass the do_IRQ()
111 This support is required to access the PS3 hard disk.
68 hard drives anyway.
509 # The worst case internal to a compressed block is very hard to figure.
316 for handling hard and soft interrupts. This can help avoid
175 using libm4.0 (hard).
1223 # answer,so we try hard to limit the available choices. Also the use of a
1057 performance counters), and the NMI watchdog which detects hard