diff options
author | Alexey Kardashevskiy <aik@ozlabs.ru> | 2018-09-10 18:29:11 +1000 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2018-10-09 16:04:27 +1100 |
commit | 2691f0ff3d96b471a69c7ef29f3340b91056845d (patch) | |
tree | d3ceacc8402d97ebc92c03d55e3abcfa7b4a6a66 /certs/blacklist.h | |
parent | 42de7b9e216728edbe53e0c4513e06fe3d566c5d (diff) | |
download | linux-stable-2691f0ff3d96b471a69c7ef29f3340b91056845d.tar.gz linux-stable-2691f0ff3d96b471a69c7ef29f3340b91056845d.tar.bz2 linux-stable-2691f0ff3d96b471a69c7ef29f3340b91056845d.zip |
KVM: PPC: Propagate errors to the guest when failed instead of ignoring
At the moment if the PUT_TCE{_INDIRECT} handlers fail to update
the hardware tables, we print a warning once, clear the entry and
continue. This is so as at the time the assumption was that if
a VFIO device is hotplugged into the guest, and the userspace replays
virtual DMA mappings (i.e. TCEs) to the hardware tables and if this fails,
then there is nothing useful we can do about it.
However the assumption is not valid as these handlers are not called for
TCE replay (VFIO ioctl interface is used for that) and these handlers
are for new TCEs.
This returns an error to the guest if there is a request which cannot be
processed. By now the only possible failure must be H_TOO_HARD.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'certs/blacklist.h')
0 files changed, 0 insertions, 0 deletions