LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com> To: Cornelia Huck <cohuck@redhat.com> Cc: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>, Halil Pasic <pasic@linux.vnet.ibm.com>, linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, kvm@vger.kernel.org, borntraeger@de.ibm.com, bjsdjshi@linux.ibm.com, pmorel@linux.ibm.com Subject: Re: [PATCH v2 5/5] vfio: ccw: add traceponits for interesting error paths Date: Mon, 30 Apr 2018 18:51:54 +0200 [thread overview] Message-ID: <42c331bf-8ba1-7a67-5ec8-6bebcfad4ed7@linux.ibm.com> (raw) In-Reply-To: <20180430170358.0ee6fe6a.cohuck@redhat.com> On 04/30/2018 05:03 PM, Cornelia Huck wrote: >> I think the naming of this fctl thing is a bit cryptic, >> but if we don't see this as ABI I'm fine with it -- can be improved. >> What would be a better name? I was thinking along the lines accept_request. >> (Bad error code would mean that the request did not get accepted. Good >> code does not mean the requested function was performed successfully.) > I think fctl is fine (if you don't understand what 'fctl' is, you're > unlikely to understand it even if it were named differently.) > AFAIU this fctl is a bit more complicated than the normal fctl. But better let sleeping dogs lie. >> Also I think vfio_ccw_io_fctl with no zero error code would make sense >> as dev_warn. If I were an admin looking into a problem I would very much >> appreciate seeing something in the messages log (and not having to enable >> tracing first). This point seems to be a good one for high level 'request gone >> bad' kind of report. Opinions? > I'd also exclude -EOPNOTSUPP (as this also might happen with e.g. a halt/clear enabled user space, which probes availability of halt/clear support by giving it a try once (yes, I really want to post my patches this week.)) > I'm looking forward to the clear/halt. It hope it will help me understand the big vfio-ccw picture better. There are still dark spots, but I don't feel like doing something against this, as there is quite some activity going on here -- and I don't want to hamper the efforts by binding resources. Regards, Halil
next prev parent reply other threads:[~2018-04-30 16:52 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-23 11:01 [PATCH v2 0/5] vfio: ccw: error handling fixes and improvements Dong Jia Shi 2018-04-23 11:01 ` [PATCH v2 1/5] vfio: ccw: fix cleanup if cp_prefetch fails Dong Jia Shi 2018-04-23 11:38 ` Halil Pasic 2018-04-23 11:40 ` Cornelia Huck 2018-04-23 12:00 ` Halil Pasic 2018-04-24 9:31 ` Cornelia Huck [not found] ` <20180425024341.GY12194@bjsdjshi@linux.vnet.ibm.com> 2018-04-25 11:19 ` Halil Pasic 2018-04-23 11:01 ` [PATCH v2 2/5] vfio: ccw: shorten kernel doc description for pfn_array_pin() Dong Jia Shi 2018-04-23 11:44 ` Cornelia Huck 2018-04-23 11:01 ` [PATCH v2 3/5] vfio: ccw: refactor and improve pfn_array_alloc_pin() Dong Jia Shi 2018-04-23 11:01 ` [PATCH v2 4/5] vfio: ccw: set ccw->cda to NULL defensively Dong Jia Shi 2018-04-23 11:01 ` [PATCH v2 5/5] vfio: ccw: add traceponits for interesting error paths Dong Jia Shi 2018-04-27 10:13 ` Cornelia Huck [not found] ` <20180428055023.GS5428@bjsdjshi@linux.vnet.ibm.com> 2018-04-30 11:51 ` Cornelia Huck 2018-04-30 14:14 ` Halil Pasic 2018-04-30 15:03 ` Cornelia Huck 2018-04-30 16:51 ` Halil Pasic [this message] [not found] ` <20180502022330.GT5428@bjsdjshi@linux.vnet.ibm.com> [not found] ` <20180516065355.GB6363@bjsdjshi@linux.ibm.com> 2018-05-22 12:55 ` Cornelia Huck 2018-04-23 11:32 ` [PATCH v2 0/5] vfio: ccw: error handling fixes and improvements Cornelia Huck
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=42c331bf-8ba1-7a67-5ec8-6bebcfad4ed7@linux.ibm.com \ --to=pasic@linux.ibm.com \ --cc=bjsdjshi@linux.ibm.com \ --cc=bjsdjshi@linux.vnet.ibm.com \ --cc=borntraeger@de.ibm.com \ --cc=cohuck@redhat.com \ --cc=kvm@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-s390@vger.kernel.org \ --cc=pasic@linux.vnet.ibm.com \ --cc=pmorel@linux.ibm.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).