Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5330634ybi; Wed, 12 Jun 2019 00:21:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqzsei06v2QlTUF5ytNhGabLPqRXxDt0jY/aikvxWaCM5RbQUyrVgwgucNT4iuyl3OwyzeFF X-Received: by 2002:a63:de0e:: with SMTP id f14mr4797381pgg.348.1560324059931; Wed, 12 Jun 2019 00:20:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560324059; cv=none; d=google.com; s=arc-20160816; b=pICdraFjzCLQdGXEOtte0lNTmNPWoLnqMPgmphv6lQMsP6PoOxvQ3b67z6zIH45z/E VUlsCvMPgXi69qAuYRlysbGic583FlIRO/po8dwP4FJ4QsSi2/40WSCFKdbI4KGFI28L 12DaPQNOUX6LFHrC7SkN687tBXRQYlIttFFO4XOr3vR2+0Ow3kc0AR0zbmSSnR5jOCm4 Yamh334oWCipTf3e4OLcYM+Zx/1i96iTHyFRH2pqiifg0AdLKGRPI0gvrIuUSYGiaCQ9 +UIXvjGBayQHZZexGm+LwGA1F9egGqeQxmBogyz8YzXyKPIzyD/5zWNrbXmaUkinM7gY +qVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=QKrBAmOdZKuRULcbGciOcXJ2Y5Vf0CkRUvynVL+L1R4=; b=SMlqZ6Cb3KQeb1ERhC8GUngRDaa/UmXL3fAfCFuOqZllaA+43k23a9C3gUwPFEG57e Fq7q5s8OTwmPXuOrnbTRfcY2n8MCBLcy5xNqOswO/g2LoWrpgg9BCzTFlGluzsao1+97 QrzTAF/7kIMvhm5DrwDF/4opFjprbnQgdWYkdArZQvZ6VFFPsIjH7xi3D8QO6Ntay9Be hYotrEzhAmZg+OBC680tzpEaLZOmlxJ7+AeiVlz7Ya8rsc0PuCCPexBljDjc6Ac9D9oK TI59sPs1sYBbHe3p8PS95KdG+WP70scG39Xuoh1o68reL4XyHy31PiWcwL4yOKRbLjcN 0uXg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 13si14617518pgk.239.2019.06.12.00.20.44; Wed, 12 Jun 2019 00:20:59 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2406600AbfFLBPf (ORCPT + 99 others); Tue, 11 Jun 2019 21:15:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42228 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404906AbfFLBPe (ORCPT ); Tue, 11 Jun 2019 21:15:34 -0400 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 75BD8C04FFF1; Wed, 12 Jun 2019 01:15:18 +0000 (UTC) Received: from localhost.localdomain (ovpn-12-17.pek2.redhat.com [10.72.12.17]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0BC67643DA; Wed, 12 Jun 2019 01:15:02 +0000 (UTC) Subject: Re: [PATCH 0/3 v11] add reserved e820 ranges to the kdump kernel e820 table To: Borislav Petkov Cc: Baoquan He , linux-kernel@vger.kernel.org, kexec@lists.infradead.org, tglx@linutronix.de, mingo@redhat.com, akpm@linux-foundation.org, dave.hansen@linux.intel.com, luto@kernel.org, peterz@infradead.org, x86@kernel.org, hpa@zytor.com, dyoung@redhat.com, Thomas.Lendacky@amd.com References: <20190423013007.17838-1-lijiang@redhat.com> <12847a03-3226-0b29-97b5-04d404410147@redhat.com> <20190607174211.GN20269@zn.tnic> <20190608035451.GB26148@MiWiFi-R3L-srv> <20190608091030.GB32464@zn.tnic> <20190608100139.GC26148@MiWiFi-R3L-srv> <20190608100623.GA9138@zn.tnic> <20190608102659.GA9130@MiWiFi-R3L-srv> <20190610113747.GD5488@zn.tnic> From: lijiang Message-ID: <6d7f4c6f-9d7c-c316-ea53-0c6b8a7b9631@redhat.com> Date: Wed, 12 Jun 2019 09:14:57 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20190610113747.GD5488@zn.tnic> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Wed, 12 Jun 2019 01:15:34 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2019年06月10日 19:37, Borislav Petkov 写道: > On Sat, Jun 08, 2019 at 06:26:59PM +0800, Baoquan He wrote: >> OK, I see. Then it should be the issue we have met and talked about with >> Tom. >> https://lkml.kernel.org/r/20190604134952.GC26891@MiWiFi-R3L-srv >> >> You can apply Tom's patch as below. I tested it, it can make kexec >> kernel succeed to boot, but failed for kdump kernel booting. The kdump >> kernel can boot till the end of kernel initialization, then hang with a >> call trace. I have pasted the log in the above thread. Haven't got the >> reason. >> http://lkml.kernel.org/r/508c2853-dc4f-70a6-6fa8-97c950dc31c6@amd.com > > I can confirm the same observation. > Currently, i haven't seen any updates yet, so i'm not sure whether this patch passed your test. Thanks. Lianbo > Thx. >