From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BFDF8C3A59C for ; Fri, 16 Aug 2019 15:15:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9B3552133F for ; Fri, 16 Aug 2019 15:15:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727544AbfHPPPO (ORCPT ); Fri, 16 Aug 2019 11:15:14 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41236 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727324AbfHPPPO (ORCPT ); Fri, 16 Aug 2019 11:15:14 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 58511302C07D; Fri, 16 Aug 2019 15:15:14 +0000 (UTC) Received: from localhost (dhcp-192-222.str.redhat.com [10.33.192.222]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D6B906B917; Fri, 16 Aug 2019 15:15:12 +0000 (UTC) From: Cornelia Huck To: Eric Farman , Halil Pasic Cc: linux-s390@vger.kernel.org, kvm@vger.kernel.org, Cornelia Huck Subject: [PATCH RFC 0/1] s390dbf logging for vfio-ccw Date: Fri, 16 Aug 2019 17:15:04 +0200 Message-Id: <20190816151505.9853-1-cohuck@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.46]); Fri, 16 Aug 2019 15:15:14 +0000 (UTC) Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org The current discussions around uuids and mdev devices got me thinking, and I realized that the uuid is an interesting information for debugging devices. Currently, vfio-ccw does not really log any debug data (there's just a lone trace event). The common I/O layer has logged interesting information into the s390dbf for a long time; this has been very useful in the past, as the logged information can be accessed in a crash dump (e.g. by the crash tool). We cannot log directly into the common I/O layer debug features, though, as vfio-ccw may be a module. Another limitation is that for the sprintf-type debug feature, any string logged via '%s' must outlive the debug feature (as it is not copied for performance reasons). That means that logging the device name is right out, as devices may go away (the current common I/O layer code logs the numerical values of ssid/subchannel number instead); logging the uuid of an mdev device via %pU just works fine, though. My patch just logs some basics right now, we can certainly add more events. We should also think about adding more trace events: they may serve a similar purpose, especially if we should enhance the vfio code with trace events in the future (so that we can correlate those trace events with the vfio-ccw trace events, just as we can correlate the s390dbf events with the common I/O layer dbf events to get a more complete picture.) Cornelia Huck (1): vfio-ccw: add some logging drivers/s390/cio/vfio_ccw_drv.c | 50 ++++++++++++++++++++++++++-- drivers/s390/cio/vfio_ccw_fsm.c | 51 ++++++++++++++++++++++++++++- drivers/s390/cio/vfio_ccw_ops.c | 10 ++++++ drivers/s390/cio/vfio_ccw_private.h | 17 ++++++++++ 4 files changed, 124 insertions(+), 4 deletions(-) -- 2.20.1