From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Leon Romanovsky <leon@kernel•org>
Cc: Marek Szyprowski <m.szyprowski@samsung•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
Christoph Hellwig <hch@lst•de>, Jason Gunthorpe <jgg@nvidia•com>
Subject: Re: linux-next: boot failure after merge of the dma-mapping tree
Date: Thu, 10 Jul 2025 09:46:12 +1000 [thread overview]
Message-ID: <20250710094612.53f2d85b@canb.auug.org.au> (raw)
In-Reply-To: <20250709174108.GH592765@unreal>
[-- Attachment #1: Type: text/plain, Size: 704 bytes --]
Hi Leon,
On Wed, 9 Jul 2025 20:41:08 +0300 Leon Romanovsky <leon@kernel•org> wrote:
>
> Can you please provide the kernel command line to determine which DMA
> path is taken?
Sorry I did not respond earlier (your email arrived at 3:41am my time
:-)) but you seem to have figured it out, thanks. I will let you know
this evening if it has not worked.
For reference the qemu command line was
qemu-system-ppc64 -M pseries,cap-hpt-max-page-size=4k,accel=kvm -m 2G -vga none -nographic -enable-kvm -kernel $vmlinux -initrd $initrd
The kernel was a powercp pseries_le_defconfig build (but setting
CONFIG_PPC_4K_PAGES=y instead of CONFIG_PPC_64K_PAGES=y).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-07-09 23:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 13:39 linux-next: boot failure after merge of the dma-mapping tree Stephen Rothwell
2025-07-09 17:41 ` Leon Romanovsky
2025-07-09 23:46 ` Stephen Rothwell [this message]
2025-07-09 18:16 ` Leon Romanovsky
2025-07-10 0:10 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2020-08-20 5:51 Stephen Rothwell
2020-08-20 8:36 ` Nicolin Chen
2020-08-20 15:49 ` Christoph Hellwig
2020-08-20 20:31 ` Nicolin Chen
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=20250710094612.53f2d85b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=hch@lst$(echo .)de \
--cc=jgg@nvidia$(echo .)com \
--cc=leon@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=m.szyprowski@samsung$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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