Re: [PATCH v2 0/2] kdump: simplify code
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: David Laight <David.Laight@xxxxxxxxxx>
- Subject: Re: [PATCH v2 0/2] kdump: simplify code
- From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
- Date: Mon, 13 Dec 2021 14:43:52 +0000
- Cc: "'Tiezhu Yang'" <yangtiezhu@xxxxxxxxxxx>, Dave Young <dyoung@xxxxxxxxxx>, Baoquan He <bhe@xxxxxxxxxx>, Vivek Goyal <vgoyal@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, "linux-arm-kernel@xxxxxxxxxxxxxxxxxxx" <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>, "linux-ia64@xxxxxxxxxxxxxxx" <linux-ia64@xxxxxxxxxxxxxxx>, "linux-mips@xxxxxxxxxxxxxxx" <linux-mips@xxxxxxxxxxxxxxx>, "linuxppc-dev@xxxxxxxxxxxxxxxx" <linuxppc-dev@xxxxxxxxxxxxxxxx>, "linux-riscv@xxxxxxxxxxxxxxxxxxx" <linux-riscv@xxxxxxxxxxxxxxxxxxx>, "linux-sh@xxxxxxxxxxxxxxx" <linux-sh@xxxxxxxxxxxxxxx>, "x86@xxxxxxxxxx" <x86@xxxxxxxxxx>, "linux-fsdevel@xxxxxxxxxxxxxxx" <linux-fsdevel@xxxxxxxxxxxxxxx>, "kexec@xxxxxxxxxxxxxxxxxxx" <kexec@xxxxxxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Xuefeng Li <lixuefeng@xxxxxxxxxxx>
- In-reply-to: <b7a75ae9253445af81ff2fedd5268af4@AcuMS.aculab.com>
- References: <1639193588-7027-1-git-send-email-yangtiezhu@loongson.cn> <0c5cb37139af4f3e85cc2c5115d7d006@AcuMS.aculab.com> <YbXhVxRJfjvKw++W@casper.infradead.org> <b7a75ae9253445af81ff2fedd5268af4@AcuMS.aculab.com>
On Mon, Dec 13, 2021 at 08:30:33AM +0000, David Laight wrote:
> From: Matthew Wilcox
> > Sent: 12 December 2021 11:48
> >
> > On Sat, Dec 11, 2021 at 05:53:46PM +0000, David Laight wrote:
> > > From: Tiezhu Yang
> > > > Sent: 11 December 2021 03:33
> > > >
> > > > v2:
> > > > -- add copy_to_user_or_kernel() in lib/usercopy.c
> > > > -- define userbuf as bool type
> > >
> > > Instead of having a flag to indicate whether the buffer is user or kernel,
> > > would it be better to have two separate buffer pointers.
> > > One for a user space buffer, the other for a kernel space buffer.
> > > Exactly one of the buffers should always be NULL.
> >
> > No. You should be using an iov_iter instead. See
> > https://lore.kernel.org/all/Ya4bdB0UBJCZhUSo@xxxxxxxxxxxxxxxxxxxx/
> > for a start on this.
>
> iov_iter gets horribly expensive...
Oh, right. Reading the kcore is a high-performance path, my mistake.
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]