From: Jan Stancek <jstancek@redhat.com>
To: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Hari Bathini <hbathini@in.ibm.com>,
Gavin Shan <gwshan@linux.vnet.ibm.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Ben Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
David Gibson <david@gibson.dropbear.id.au>,
Wei Yang <weiyang@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/powernv/pci-ioda: fix kdump with non-power-of-2 crashkernel=
Date: Fri, 4 Sep 2015 15:03:40 -0400 (EDT) [thread overview]
Message-ID: <1241394720.5843765.1441393420849.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20150904182252.GN47557@linux.vnet.ibm.com>
----- Original Message -----
> From: "Nishanth Aravamudan" <nacc@linux.vnet.ibm.com>
> To: "Michael Ellerman" <mpe@ellerman.id.au>
> Cc: "Hari Bathini" <hbathini@in.ibm.com>, "Gavin Shan" <gwshan@linux.vnet.ibm.com>, "Alexey Kardashevskiy"
> <aik@ozlabs.ru>, "Ben Herrenschmidt" <benh@kernel.crashing.org>, "Paul Mackerras" <paulus@samba.org>, "David Gibson"
> <david@gibson.dropbear.id.au>, "Wei Yang" <weiyang@linux.vnet.ibm.com>, linuxppc-dev@lists.ozlabs.org, "Jan Stancek"
> <jstancek@redhat.com>
> Sent: Friday, 4 September, 2015 8:22:52 PM
> Subject: [PATCH v2] powerpc/powernv/pci-ioda: fix kdump with non-power-of-2 crashkernel=
>
> The 32-bit TCE table initialization relies on the DMA window having a
> size equal to a power of 2 (and checks for it explicitly). But
> crashkernel= has no constraint that requires a power-of-2 be specified.
> This causes the kdump kernel to fail to boot as none of the PCI devices
> (including the disk controller) are successfully initialized.
>
> After this change, the PCI devices successfully set up the 32-bit TCE
> table and kdump succeeds.
>
> Fixes: aca6913f5551 ("powerpc/powernv/ioda2: Introduce helpers to allocate
> TCE pages")
> Signed-off-by: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
> Cc: stable@vger.kernel.org # 4.2
Tested-by: Jan Stancek <jstancek@redhat.com>
I can confirm, that this patch along with
http://patchwork.ozlabs.org/patch/513229/
applied on top of 4.2 is fixing kdump for me on Power S812L.
(ppc64le bare metal, crashkernel=1024M)
Regards,
Jan
>
> ---
>
> Michael, I kept this as a follow-on patch to my previous one. If you'd
> rather I made a v3 of that patch with the two fixes combined, I can
> resend. Also, I fixed up the context on my end to be u64, but not sure
> if that will match your tree (next doesn't have my prior patch applied
> yet, that I can see).
>
> diff --git a/arch/powerpc/platforms/powernv/pci-ioda.c
> b/arch/powerpc/platforms/powernv/pci-ioda.c
> index f1c74c28e564..d5e635f2c3aa 100644
> --- a/arch/powerpc/platforms/powernv/pci-ioda.c
> +++ b/arch/powerpc/platforms/powernv/pci-ioda.c
> @@ -2078,12 +2078,18 @@ static long pnv_pci_ioda2_setup_default_config(struct
> pnv_ioda_pe *pe)
> struct iommu_table *tbl = NULL;
> long rc;
> /*
> + * crashkernel= specifies the kdump kernel's maximum memory at
> + * some offset and there is no guaranteed the result is a power
> + * of 2, which will cause errors later.
> + */
> + const u64 max_memory = __rounddown_pow_of_two(memory_hotplug_max());
> + /*
> * In memory constrained environments, e.g. kdump kernel, the
> * DMA window can be larger than available memory, which will
> * cause errors later.
> */
> const u64 window_size =
> - min((u64)pe->table_group.tce32_size, memory_hotplug_max());
> + min((u64)pe->table_group.tce32_size, max_memory);
>
> rc = pnv_pci_ioda2_create_table(&pe->table_group, 0,
> iommu_page_shift_4k,
>
>
next prev parent reply other threads:[~2015-09-04 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 18:22 [PATCH v2] powerpc/powernv/pci-ioda: fix kdump with non-power-of-2 crashkernel= Nishanth Aravamudan
2015-09-04 19:03 ` Jan Stancek [this message]
2015-09-07 9:19 ` Michael Ellerman
2015-09-08 3:10 ` Nishanth Aravamudan
2015-09-08 12:05 ` [v2] " Michael Ellerman
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=1241394720.5843765.1441393420849.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=gwshan@linux.vnet.ibm.com \
--cc=hbathini@in.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nacc@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=weiyang@linux.vnet.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.