Searched refs:hard (Results 1 – 21 of 21) sorted by relevance
49 struct vfp_hard_struct hard; member74 struct fp_hard_struct hard; member
68 if (thread->vfpstate.hard.cpu != cpu) in vfp_state_in_hw()86 thread->vfpstate.hard.cpu = NR_CPUS; in vfp_force_reload()114 vfp->hard.fpexc = FPEXC_EN; in vfp_thread_flush()115 vfp->hard.fpscr = FPSCR_ROUND_NEAREST; in vfp_thread_flush()117 vfp->hard.cpu = NR_CPUS; in vfp_thread_flush()139 thread->vfpstate.hard.cpu = NR_CPUS; in vfp_thread_copy()561 struct vfp_hard_struct *hwstate = &thread->vfpstate.hard; in vfp_preserve_user_clear_hwstate()604 struct vfp_hard_struct *hwstate = &thread->vfpstate.hard; in vfp_restore_user_hwstate()
24 hard lockup.
672 struct vfp_hard_struct const *vfp = &thread->vfpstate.hard; in vfp_get()714 new_vfp = thread->vfpstate.hard; in vfp_set()736 thread->vfpstate.hard = new_vfp; in vfp_set()
79 DEFINE(VFP_CPU, offsetof(union vfp_state, hard.cpu)); in main()
46 for handling hard and soft interrupts. This can help avoid
39 which allows direct access to the hard drives without using
484 * that isn't a valid hard IRQ, therefore we bypass the do_IRQ()
112 This support is required to access the PS3 hard disk.
68 hard drives anyway.
181 If you plan on running programs which are compiled to use hard floats
267 for handling hard and soft interrupts. This can help avoid
497 # The worst case internal to a compressed block is very hard to figure.
18 does not hard-code any board-specific knowledge but instead uses
35 hard-reset-gpios = <&LEDs_8Bit 2 1>;
254 is buggy and can cause a situation which would lead unexplained hard
1054 * watchdog provides no debugging information (compared to soft/hard
1085 * watchdog provides no debugging information (compared to soft/hard
175 using libm4.0 (hard).
879 destination. This catches hard-to-find kernel bugs and973 performance counters), and the NMI watchdog which detects hard
1186 # answer,so we try hard to limit the available choices. Also the use of a