Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: lijiang <lijiang@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas.Lendacky@amd.com, x86@kernel.org,
	Baoquan He <bhe@redhat.com>,
	peterz@infradead.org, dave.hansen@linux.intel.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, luto@kernel.org, hpa@zytor.com,
	akpm@linux-foundation.org, dyoung@redhat.com, tglx@linutronix.de
Subject: Re: [PATCH 0/3 v11] add reserved e820 ranges to the kdump kernel e820 table
Date: Wed, 12 Jun 2019 09:14:57 +0800	[thread overview]
Message-ID: <6d7f4c6f-9d7c-c316-ea53-0c6b8a7b9631@redhat.com> (raw)
In-Reply-To: <20190610113747.GD5488@zn.tnic>

在 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.
> 

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2019-06-12  1:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23  1:30 [PATCH 0/3 v11] add reserved e820 ranges to the kdump kernel e820 table Lianbo Jiang
2019-04-23  1:30 ` [PATCH 1/3 v11] x86/e820, resource: add a new I/O resource descriptor 'IORES_DESC_RESERVED' Lianbo Jiang
2019-04-23  1:30 ` [PATCH 2/3 v11] x86/mm: change the check condition in SEV because a new descriptor is introduced Lianbo Jiang
2019-04-23  1:30 ` [PATCH 3/3 v11] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table Lianbo Jiang
2019-05-28  7:30 ` [PATCH 0/3 v11] add reserved e820 ranges to the " lijiang
2019-06-07 17:42   ` Borislav Petkov
2019-06-08  3:54     ` Baoquan He
2019-06-08  9:10       ` Borislav Petkov
2019-06-08 10:01         ` Baoquan He
2019-06-08 10:06           ` Borislav Petkov
2019-06-08 10:26             ` Baoquan He
2019-06-10 11:37               ` Borislav Petkov
2019-06-12  1:14                 ` lijiang [this message]
2019-06-12  1:55                 ` Baoquan He
2019-06-12  5:49                   ` Dave Young
2019-06-12 15:10                   ` Borislav Petkov
2019-06-12 16:52                     ` Lendacky, Thomas
2019-06-12 18:07                       ` Borislav Petkov
2019-06-12 19:10                         ` Lendacky, Thomas
2019-06-13 15:07                           ` Baoquan He
2019-06-13  1:18                         ` dyoung
2019-06-09  4:02     ` lijiang

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=6d7f4c6f-9d7c-c316-ea53-0c6b8a7b9631@redhat.com \
    --to=lijiang@redhat.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dyoung@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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