From: Pu Wen <puwen@hygon.cn>
To: Borislav Petkov <bp@alien8.de>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, thomas.lendacky@amd.com, pbonzini@redhat.com,
tony.luck@intel.com, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, linux-edac@vger.kernel.org
Subject: [v5,10/16] x86/mce: enable Hygon support to MCE infrastructure
Date: Thu, 6 Sep 2018 23:47:31 +0800 [thread overview]
Message-ID: <f4bdfc6d-c8ad-16d8-c641-51db36d64e66@hygon.cn> (raw)
On 2018/9/6 20:29, Borislav Petkov wrote:
> Say what now?! What testing do you do if you boot a kernel which doesn't
> even use the functionality you're testing?!
I'm sorry, this case is not good to demonstrate the useage. And I think
there are no other people will do the test without MCE in kernel. So
with MCE enabled in kernel is the main case to support.
> The first way but change that dependency to CPU_SUP_AMD because there
> are people building their own kernels and don't run distro configs. And
> you need CPU_SUP_AMD because you're using their code.
That's good, will select CPU_SUP_AMD for CPU_SUP_HYGON to solve the
dependency issues in kernel.
next reply other threads:[~2018-09-06 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 15:47 Pu Wen [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-06 12:29 [v5,10/16] x86/mce: enable Hygon support to MCE infrastructure Borislav Petkov
2018-09-06 11:40 Pu Wen
2018-09-06 8:39 Borislav Petkov
2018-09-06 3:52 Pu Wen
2018-09-05 13:15 Borislav Petkov
2018-09-05 12:59 Pu Wen
2018-09-05 9:22 Borislav Petkov
2018-08-29 12:44 Pu Wen
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=f4bdfc6d-c8ad-16d8-c641-51db36d64e66@hygon.cn \
--to=puwen@hygon.cn \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tony.luck@intel.com \
--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