s390x/mmu: Drop debug logging from MMU code
commita780d096e640ce736577aba17163a3f6ec4b50b0
authorDavid Hildenbrand <david@redhat.com>
Wed, 25 Sep 2019 09:37:04 +0000 (25 11:37 +0200)
committerDavid Hildenbrand <david@redhat.com>
Wed, 9 Oct 2019 10:33:47 +0000 (9 12:33 +0200)
treefd12d92868bb40f83a14c725c97bf500e0f408ba
parent98b2e3c9ab3abfe476a2b02f8f51813edb90e72d
s390x/mmu: Drop debug logging from MMU code

Let's get it out of the way to make some further refactorings easier.
Personally, I've never used these debug statements at all. And if I had
to debug issues, I used plain GDB instead (debug prints are just way too
much noise in the MMU). We might want to introduce tracing at some point
instead, so we can able selected events on demand.

Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: David Hildenbrand <david@redhat.com>
target/s390x/mmu_helper.c