From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from us-smtp-delivery-124.mimecast.com ([63.128.21.124]) by desiato.infradead.org with esmtps (Exim 4.94 #2 (Red Hat Linux)) id 1lRACv-0036n3-43 for kexec@lists.infradead.org; Tue, 30 Mar 2021 08:58:42 +0000 Subject: Re: [PATCH v1 0/3] crashdump/x86: dump dax/kmem and virito-mem added System RAM References: <20210323100111.8365-1-david@redhat.com> From: David Hildenbrand Message-ID: <1c014e9b-88f3-085c-2e67-38007e21c031@redhat.com> Date: Tue, 30 Mar 2021 10:58:28 +0200 MIME-Version: 1.0 In-Reply-To: <20210323100111.8365-1-david@redhat.com> Content-Language: en-US List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: kexec@lists.infradead.org Cc: Baoquan He , Dan Williams , Dave Hansen , Simon Horman On 23.03.21 11:01, David Hildenbrand wrote: > Let's properly support dumping any kind of "System RAM" that is not on the > top level of the kernel resource tree in /proc/iomem, processing any > /proc/iomem entry that contains "System RAM". In addition, increase > the maximum number of crash memory ranges to fully support virtio-mem > even in corner cases where we end up with a lot of individual memory > ranges. > > David Hildenbrand (3): > crashdump/x86: dump any kind of "System RAM" > crashdump/x86: iterate only over actual crash memory ranges > crashdump/x86: increase CRASH_MAX_MEMORY_RANGES to 32k > > kexec/arch/i386/crashdump-x86.c | 18 +++++++++++++----- > kexec/arch/i386/crashdump-x86.h | 3 ++- > 2 files changed, 15 insertions(+), 6 deletions(-) > Gentle ping. -- Thanks, David / dhildenb _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec