From: Alexander Gordeev <agordeev@linux.ibm.com>
To: Alexander Egorenkov <egorenar@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>
Cc: Matthew Wilcox <willy@infradead.org>, Baoquan He <bhe@redhat.com>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [PATCH v2 0/1] s390/crash: allow multi-segment iterators
Date: Thu, 7 Jul 2022 08:01:14 +0200 [thread overview]
Message-ID: <cover.1657172539.git.agordeev@linux.ibm.com> (raw)
Unlike other architectures s390 can not use copyout() and memcopy() for
accessing memory and thus using copy_to_iter() now is not possible. But
a fix is needed, since 'cp' routine as 'core_collector' for kdump service
initiates multi-segment iterator.
The reason iterate_iovec() and __iterate_and_advance() macros copied from
lib/iov_iter.c (thus introducing redundancy) is to avoid custom iterator-
treating in s390 code. I doubt these macros could be turned public (i.e
with a follow-up patch), so the intention is to do it like _copy_to_iter()
does.
Changes since v1:
- number of bytes left to copy on fail fixed;
Alexander Gordeev (1):
s390/crash: allow multi-segment iterators
arch/s390/kernel/crash_dump.c | 65 +++++++++++++++++++++++++++--------
1 file changed, 50 insertions(+), 15 deletions(-)
--
2.34.1
next reply other threads:[~2022-07-07 6:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 6:01 Alexander Gordeev [this message]
2022-07-07 6:01 ` [PATCH v2 1/1] s390/crash: allow multi-segment iterators Alexander Gordeev
2022-07-07 12:36 ` Al Viro
2022-07-07 12:54 ` Matthew Wilcox
2022-07-07 13:31 ` Al Viro
2022-07-07 19:06 ` Matthew Wilcox
2022-07-13 11:17 ` Alexander Gordeev
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=cover.1657172539.git.agordeev@linux.ibm.com \
--to=agordeev@linux.ibm.com \
--cc=bhe@redhat.com \
--cc=egorenar@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=willy@infradead.org \
/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: link
Be 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