From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: linuxppc-dev@lists.ozlabs.org,
"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Cc: Christophe Leroy <chleroy@kernel.org>,
linux-mm@kvack.org, kvm@vger.kernel.org,
Alex Williamson <alex@shazbot.org>, Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH v2 1/2] drivers/vfio_pci_core: Change PXD_ORDER check from switch case to if/else block
Date: Wed, 8 Apr 2026 09:59:06 +0530 [thread overview]
Message-ID: <177562236414.1381144.5625779243354479459.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <b155e19993ee1f5584c72050192eb468b31c5029.1773058761.git.ritesh.list@gmail.com>
On Mon, 09 Mar 2026 18:08:37 +0530, Ritesh Harjani (IBM) wrote:
> Architectures like PowerPC uses runtime defined values for
> PMD_ORDER/PUD_ORDER. This is because it can use either RADIX or HASH MMU
> at runtime using kernel cmdline. So the pXd_index_size is not known at
> compile time. Without this fix, when we add huge pfn support on powerpc
> in the next patch, vfio_pci_core driver compilation can fail with the
> following errors.
>
> [...]
Applied to powerpc/next.
[1/2] drivers/vfio_pci_core: Change PXD_ORDER check from switch case to if/else block
https://git.kernel.org/powerpc/c/948b71aa81cd89b222942db6055e8d9c51c54e78
[2/2] powerpc/64s: Add support for huge pfnmaps
https://git.kernel.org/powerpc/c/d1503aa9ab8057cb93367e0184528f61f7510845
cheers
prev parent reply other threads:[~2026-04-08 4:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 12:38 Ritesh Harjani (IBM)
2026-03-09 12:38 ` [PATCH v2 2/2] powerpc/64s: Add support for huge pfnmaps Ritesh Harjani (IBM)
2026-03-09 14:24 ` [PATCH v2 1/2] drivers/vfio_pci_core: Change PXD_ORDER check from switch case to if/else block Christophe Leroy (CS GROUP)
2026-03-09 21:46 ` Alex Williamson
2026-03-11 2:20 ` Ritesh Harjani
2026-03-10 6:27 ` Venkat
2026-04-08 4:29 ` Madhavan Srinivasan [this message]
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=177562236414.1381144.5625779243354479459.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=alex@shazbot.org \
--cc=chleroy@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=peterx@redhat.com \
--cc=ritesh.list@gmail.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: 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