From: Jiri Bohac <jbohac@suse.cz> To: Baoquan He <bhe@redhat.com> Cc: Borislav Petkov <bp@alien8.de>, Toshi Kani <toshi.kani@hpe.com>, David Airlie <airlied@linux.ie>, Dave Young <dyoung@redhat.com>, joro@8bytes.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>, Bjorn Helgaas <bhelgaas@google.com>, Thomas Gleixner <tglx@linutronix.de>, yinghai@kernel.org, Vivek Goyal <vgoyal@redhat.com> Subject: Re: [PATCH v2] x86/kexec: Exclude GART aperture from vmcore Date: Tue, 19 Dec 2017 18:58:27 +0100 [thread overview] Message-ID: <20171219175827.oqfskuax6zzm2ljq@dwarf.suse.cz> (raw) In-Reply-To: <20171219015804.GC4035@x1> On Tue, Dec 19, 2017 at 09:58:04AM +0800, Baoquan He wrote: > Hmm, as I have said in the first replying mail, the v2 will introduce > issues: > > 1) If 'iommu=off' is specified in 1st kernel but not in kdump kernel, it > will ignore the ram we need dump. yes, instead of crashing the machine (because GART may be initialized in the 2nd kernel, overlapping the 1st kernel memory, which the 2nd kernel with its fake e820 map sees as unused). I'd say this is an improvement. > 2) If 'iommu=off' is specified in kdump kernel, but not in 1st kernel, > it won't get the GART region, this patch does't work. No. It will work: First kernel initializes the GART (either in a hole properly provided by the BIOS or overlapping e820 RAM). Second kernel will start with the GART initialized. In gart_iommu_hole_init() the setting is read from the northbridge registers and verified as valid. It does not overlap e820 memory, because the second kernel has a fake e820 map only spanning the crashkernel= reserved range. "fix" is never set to 1, so it will exclude GART from vmcore in this path: out: if (!fix && !fallback_aper_force) { if (last_aper_base) { exclude_from_vmcore(last_aper_base, last_aper_order); return 1; (fix is never set to 1) no_iommu is only checked after that. > 3) If people enable GART in bios, there's a ram memory hole for GART. > Nothing need to do while kdump kernel doesn't know GART is enabled or > not in bios, will try to avoid it anyway. It won't hurt anythig though, > in logic it's not suggested since confusion will be brought in. I don't have easy access to the HP machines. I have a machine right here in our lab that has this issue. It has no "enable GART" setting in BIOS. It has a "enable IOMMU" setting. The bug stays there regardless of the setting. It's old. Noone will fix the firmware. The patch fixes it. Thanks, -- Jiri Bohac <jbohac@suse.cz> SUSE Labs, Prague, Czechia
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Bohac <jbohac@suse.cz> To: Baoquan He <bhe@redhat.com> Cc: Toshi Kani <toshi.kani@hpe.com>, David Airlie <airlied@linux.ie>, yinghai@kernel.org, joro@8bytes.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>, Bjorn Helgaas <bhelgaas@google.com>, Thomas Gleixner <tglx@linutronix.de>, Dave Young <dyoung@redhat.com>, Vivek Goyal <vgoyal@redhat.com> Subject: Re: [PATCH v2] x86/kexec: Exclude GART aperture from vmcore Date: Tue, 19 Dec 2017 18:58:27 +0100 [thread overview] Message-ID: <20171219175827.oqfskuax6zzm2ljq@dwarf.suse.cz> (raw) In-Reply-To: <20171219015804.GC4035@x1> On Tue, Dec 19, 2017 at 09:58:04AM +0800, Baoquan He wrote: > Hmm, as I have said in the first replying mail, the v2 will introduce > issues: > > 1) If 'iommu=off' is specified in 1st kernel but not in kdump kernel, it > will ignore the ram we need dump. yes, instead of crashing the machine (because GART may be initialized in the 2nd kernel, overlapping the 1st kernel memory, which the 2nd kernel with its fake e820 map sees as unused). I'd say this is an improvement. > 2) If 'iommu=off' is specified in kdump kernel, but not in 1st kernel, > it won't get the GART region, this patch does't work. No. It will work: First kernel initializes the GART (either in a hole properly provided by the BIOS or overlapping e820 RAM). Second kernel will start with the GART initialized. In gart_iommu_hole_init() the setting is read from the northbridge registers and verified as valid. It does not overlap e820 memory, because the second kernel has a fake e820 map only spanning the crashkernel= reserved range. "fix" is never set to 1, so it will exclude GART from vmcore in this path: out: if (!fix && !fallback_aper_force) { if (last_aper_base) { exclude_from_vmcore(last_aper_base, last_aper_order); return 1; (fix is never set to 1) no_iommu is only checked after that. > 3) If people enable GART in bios, there's a ram memory hole for GART. > Nothing need to do while kdump kernel doesn't know GART is enabled or > not in bios, will try to avoid it anyway. It won't hurt anythig though, > in logic it's not suggested since confusion will be brought in. I don't have easy access to the HP machines. I have a machine right here in our lab that has this issue. It has no "enable GART" setting in BIOS. It has a "enable IOMMU" setting. The bug stays there regardless of the setting. It's old. Noone will fix the firmware. The patch fixes it. Thanks, -- Jiri Bohac <jbohac@suse.cz> SUSE Labs, Prague, Czechia _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2017-12-19 17:58 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-12-16 0:15 [PATCH v2] x86/kexec: Exclude GART aperture from vmcore Jiri Bohac 2017-12-16 0:15 ` Jiri Bohac 2017-12-16 1:01 ` Baoquan He 2017-12-16 1:01 ` Baoquan He 2017-12-17 21:47 ` Borislav Petkov 2017-12-17 21:47 ` Borislav Petkov 2017-12-18 13:47 ` Baoquan He 2017-12-18 13:47 ` Baoquan He 2017-12-18 14:37 ` Borislav Petkov 2017-12-19 1:58 ` Baoquan He 2017-12-19 1:58 ` Baoquan He 2017-12-19 17:58 ` Jiri Bohac [this message] 2017-12-19 17:58 ` Jiri Bohac 2017-12-27 7:44 ` Baoquan He 2017-12-27 7:44 ` Baoquan He 2017-12-27 12:25 ` Borislav Petkov 2017-12-27 12:44 ` Baoquan He 2017-12-27 12:44 ` Baoquan He 2018-01-06 1:00 ` Jiri Bohac 2018-01-06 1:00 ` Jiri Bohac 2018-01-09 6:19 ` Baoquan He 2018-01-09 6:19 ` Baoquan He 2018-01-11 14:13 ` [tip:x86/mm] x86/gart: " tip-bot for Jiri Bohac
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=20171219175827.oqfskuax6zzm2ljq@dwarf.suse.cz \ --to=jbohac@suse.cz \ --cc=airlied@linux.ie \ --cc=bhe@redhat.com \ --cc=bhelgaas@google.com \ --cc=bp@alien8.de \ --cc=dyoung@redhat.com \ --cc=hpa@zytor.com \ --cc=joro@8bytes.org \ --cc=kexec@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@redhat.com \ --cc=tglx@linutronix.de \ --cc=toshi.kani@hpe.com \ --cc=vgoyal@redhat.com \ --cc=yinghai@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: linkBe 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.