From: Borislav Petkov <bp@alien8.de>
To: Baoquan He <bhe@redhat.com>
Cc: Jiri Bohac <jbohac@suse.cz>, 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: Sun, 17 Dec 2017 22:47:35 +0100 [thread overview]
Message-ID: <20171217214735.nuxq5zo2eknqpbpi@pd.tnic> (raw)
In-Reply-To: <20171216010142.GK12442@x1>
On Sat, Dec 16, 2017 at 09:01:42AM +0800, Baoquan He wrote:
> 2) If firmware is broken, you can't enable gart in firmware, will
> firmware engineer fix this since it's a firmware bug?
Slow down and get a reality check first please!
A firmware engineer will fix a 10yr old BIOS?!? Yeah right. And I'll get
a pink pony for Christmas. Geez.
We need a reliable way to tell the second kernel not to access the gart
range. And frankly, the best thing to do would be to teach the *second*
kernel to simply avoid the gart range. Regardless of what it gets told
by the ELF header. Because there are some ranges which it shouldn't
touch. Maybe we can reuse the gart detection code to do that in the
second kernel too.
But I haven't looked at it, might be hairy. Need to deal with this PTI
madness first.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Baoquan He <bhe@redhat.com>
Cc: Jiri Bohac <jbohac@suse.cz>, 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>,
"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: Sun, 17 Dec 2017 22:47:35 +0100 [thread overview]
Message-ID: <20171217214735.nuxq5zo2eknqpbpi@pd.tnic> (raw)
In-Reply-To: <20171216010142.GK12442@x1>
On Sat, Dec 16, 2017 at 09:01:42AM +0800, Baoquan He wrote:
> 2) If firmware is broken, you can't enable gart in firmware, will
> firmware engineer fix this since it's a firmware bug?
Slow down and get a reality check first please!
A firmware engineer will fix a 10yr old BIOS?!? Yeah right. And I'll get
a pink pony for Christmas. Geez.
We need a reliable way to tell the second kernel not to access the gart
range. And frankly, the best thing to do would be to teach the *second*
kernel to simply avoid the gart range. Regardless of what it gets told
by the ELF header. Because there are some ranges which it shouldn't
touch. Maybe we can reuse the gart detection code to do that in the
second kernel too.
But I haven't looked at it, might be hairy. Need to deal with this PTI
madness first.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2017-12-17 21:47 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 [this message]
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
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=20171217214735.nuxq5zo2eknqpbpi@pd.tnic \
--to=bp@alien8.de \
--cc=airlied@linux.ie \
--cc=bhe@redhat.com \
--cc=bhelgaas@google.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=jbohac@suse.cz \
--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: 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.