From: Boris Petkov <bp@alien8.de>
To: lijiang <lijiang@redhat.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
x86@kernel.org, tglx@linutronix.de, mingo@redhat.com,
akpm@linux-foundation.org, dyoung@redhat.com, bhe@redhat.com
Subject: Re: [PATCH 1/2 v6] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name
Date: Wed, 21 Nov 2018 14:06:22 +0100 [thread overview]
Message-ID: <49B3EB59-ABD2-4A5C-BE8A-B078283B8418@alien8.de> (raw)
In-Reply-To: <ddeff176-2517-4b58-73b6-3787e84b2a5e@redhat.com>
On November 21, 2018 11:54:09 AM GMT+01:00, lijiang <lijiang@redhat.com> wrote:
>If you understood this issue, you might ignore it, please.
Yes,I got it. Simply figuring out which reserved regions to export and which not, is not worth the effort - we can do the simple thing of directly exporting them all.
Thx.
--
Sent from a small device: formatting sux and brevity is inevitable.
next prev parent reply other threads:[~2018-11-21 13:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 7:29 [PATCH 0/2 v6] add reserved e820 ranges to the kdump kernel e820 table Lianbo Jiang
2018-11-14 7:29 ` [PATCH 1/2 v6] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name Lianbo Jiang
2018-11-14 11:26 ` Borislav Petkov
2018-11-15 5:44 ` lijiang
2018-11-15 5:58 ` Dave Young
2018-11-16 1:34 ` lijiang
2018-11-15 10:39 ` Borislav Petkov
2018-11-16 3:25 ` lijiang
2018-11-18 11:52 ` Borislav Petkov
2018-11-20 4:07 ` lijiang
2018-11-21 10:54 ` lijiang
2018-11-21 13:06 ` Boris Petkov [this message]
2018-11-19 9:55 ` Dave Young
2018-11-19 10:28 ` Borislav Petkov
2018-11-20 3:37 ` lijiang
2018-11-20 19:29 ` Borislav Petkov
2018-11-20 20:43 ` Bjorn Helgaas
2018-11-21 18:42 ` Borislav Petkov
2018-11-14 7:29 ` [PATCH 2/2 v6] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table Lianbo Jiang
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=49B3EB59-ABD2-4A5C-BE8A-B078283B8418@alien8.de \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=helgaas@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).