LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> To: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org, kvm@vger.kernel.org Cc: cohuck@redhat.com, borntraeger@de.ibm.com, bjsdjshi@linux.ibm.com, pasic@linux.ibm.com, pmorel@linux.ibm.com, Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> Subject: [PATCH v2 0/5] vfio: ccw: error handling fixes and improvements Date: Mon, 23 Apr 2018 13:01:08 +0200 [thread overview] Message-ID: <20180423110113.59385-1-bjsdjshi@linux.vnet.ibm.com> (raw) Dear Reviewers, Here is a new version for this patch series. We didn't get agreement on patch #5 (#4 in v1) in the former cycle though, I made it based on my understanding. We can continue discussing on it. Changelog: v1->v2: - #1. Reworded commit message and comment, plus some typo fixes. - #2. New patch. - #3. Added the missing suggested-by Pierre. Fixed typos. Added sanity check on pa->pa_iova_pfn and updated comments accordingly. - #4. Removed unused idaw_nr. - #5. Replaced leading white spaces with TABs. Traced the function in anycase. Dong Jia Shi (3): vfio: ccw: shorten kernel doc description for pfn_array_pin() vfio: ccw: refactor and improve pfn_array_alloc_pin() vfio: ccw: set ccw->cda to NULL defensively Halil Pasic (2): vfio: ccw: fix cleanup if cp_prefetch fails vfio: ccw: add traceponits for interesting error paths drivers/s390/cio/Makefile | 1 + drivers/s390/cio/vfio_ccw_cp.c | 134 ++++++++++++++++++++------------------ drivers/s390/cio/vfio_ccw_fsm.c | 16 ++++- drivers/s390/cio/vfio_ccw_trace.h | 77 ++++++++++++++++++++++ 4 files changed, 164 insertions(+), 64 deletions(-) create mode 100644 drivers/s390/cio/vfio_ccw_trace.h -- 2.13.5
next reply other threads:[~2018-04-23 11:01 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-23 11:01 Dong Jia Shi [this message] 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 [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=20180423110113.59385-1-bjsdjshi@linux.vnet.ibm.com \ --to=bjsdjshi@linux.vnet.ibm.com \ --cc=bjsdjshi@linux.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.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).