Lines Matching refs:DAWR

2 DAWR issues on POWER9
5 On older POWER9 processors, the Data Address Watchpoint Register (DAWR) can
7 has no way to distinguish CI memory when configuring the DAWR, so on affected
8 systems, the DAWR is disabled.
21 On a system with the issue, the DAWR is disabled as detailed below.
26 DAWR has 6 different ways of being set.
28 2) h_set_mode(DAWR)
37 h_set_mode(DAWR) and h_set_dabr() will now return an error to the
39 they will silently not get the DAWR.
44 DAWR on the migration.
61 and configure the hardware to use the DAWR. This will run at full
68 Force enabling the DAWR
70 Kernels (since ~v5.2) have an option to force enable the DAWR via::
74 This enables the DAWR even on POWER9.
79 (ie. single user/desktop systems) and really want the DAWR.  This
80 allows them to force enable DAWR.
82 This flag can also be used to disable DAWR access. Once this is
83 cleared, all DAWR access should be cleared immediately and your
86 Userspace may get confused by toggling this. If DAWR is force
91 For the DAWR to be enabled in a KVM guest, the DAWR needs to be force
95 writing the DAWR.
97 To double check the DAWR is working, run this kernel selftest: