mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Zhiquan Li <zhiquan1.li@intel.com>
Cc: x86@kernel.org, linux-edac@vger.kernel.org,
	linux-kernel@vger.kernel.org, patches@lists.linux.dev,
	tony.luck@intel.com, naoya.horiguchi@nec.com
Subject: Re: [PATCH RESEND v2] x86/mce: Set PG_hwpoison page flag to avoid the capture kernel panic
Date: Thu, 12 Oct 2023 16:57:08 +0200	[thread overview]
Message-ID: <20231012145708.GIZSgJRIRq8OSF6UaB@fat_crate.local> (raw)
In-Reply-To: <3f9e9468-ec74-42ad-8d42-c3f6fb8b5f74@intel.com>

On Wed, Oct 11, 2023 at 11:00:57AM +0800, Zhiquan Li wrote:
> Aha, this is the neat thing about the patch.  The main task of kdump
> kernel is providing a "window" - /proc/vmcore, for the dump program to
> access old memory.  A dump program running in userspace determines the
> "policy".  Which pages need to be dumped is determined by the
> configuration of dump program, it reads out the pages that the
> sustaining engineer is interested in and excludes the rest.  The de
> facto dump program (makedumpfile) already supports to identify those
> poisoned pages and exclude them a decade ago:

Yes, put that in your commit message.

> When we were developing the patch internally, Tony contributed a lot of
> precious ideas and guidance, not only the code change he mentioned in
> commit message.
> 
> The previous V2 sent by Tony missed the merge window of v6.5, so I
> re-based it onto the latest v6.6 rc, re-validated and re-send the patch.
>  And I will follow up the feedback from community.

Then you should ask Tony whether he wants Co-developed-by:. See

Documentation/process/submitting-patches.rst

for detail.

There it is also explained what an SOB chain is and how it should look
like.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2023-10-12 14:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14  3:05 Zhiquan Li
2023-10-02 19:06 ` Ingo Molnar
2023-10-10  0:56   ` Zhiquan Li
2023-10-10  8:25     ` Borislav Petkov
2023-10-10  8:28 ` Borislav Petkov
2023-10-11  3:00   ` Zhiquan Li
2023-10-12 14:57     ` Borislav Petkov [this message]
2023-10-13  0:26       ` Zhiquan Li

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=20231012145708.GIZSgJRIRq8OSF6UaB@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naoya.horiguchi@nec.com \
    --cc=patches@lists.linux.dev \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    --cc=zhiquan1.li@intel.com \
    /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

all inboxes | Powered by JetHome®