Searched full:unavoidable (Results 1 – 9 of 9) sorted by relevance
22 general enough such that they are unavoidable regardless of implementation
117 * If ___bits == 0 then setting bit 31 is unavoidable. \
260 * go backwards compared to the host RTC, but this is unavoidable. in pl031_post_load()
139 * degree, this is unavoidable for small synthetic benchmarks.
182 are unfortunately unavoidable due to the large number of packages
216 * too much data, implementing this would cause an unavoidable race.2061 * (6.6.1), so it's unavoidable. It also says we must in received_cbw()
1931 * There is an unavoidable race condition if a different vCPU sets a in kvm_get_xen_state()
281 * or two-stage paging is enabled. It's unavoidable though, in riscv_iommu_spa_fetch()
35 # unavoidable when linking the built-in.o targets which finally