From: Dave Hansen <dave.hansen@intel.com>
To: kernel test robot <oliver.sang@intel.com>,
John <therealgraysky@proton.me>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Unknown <x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: add more x86-64 micro-architecture levels
Date: Tue, 24 Sep 2024 06:38:56 -0700 [thread overview]
Message-ID: <6e6ffa78-1f8c-4f32-9fe7-141cb39d06d2@intel.com> (raw)
In-Reply-To: <202409241436.b37a069e-oliver.sang@intel.com>
On 9/24/24 00:00, kernel test robot wrote:
> we don't have enough knowledge how this commit causing the random
> early crash issue as report below.
>
> we noticed the config has below diff comparing to parent....
> +# CONFIG_MAMD_CPU_V2 is not set
> +# CONFIG_MAMD_CPU_V3 is not set
> +CONFIG_MAMD_CPU_V4=y
> +# CONFIG_MINTEL_CPU_V2 is not set
> +# CONFIG_MINTEL_CPU_V3 is not set
> +# CONFIG_MINTEL_CPU_V4 is not set
Clang is probably being induced to use some ISA that isn't supported on
Sandybridge.
In any case, I think this series is very unlikely to get applied.
next prev parent reply other threads:[~2024-09-24 13:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 11:05 John
2024-09-15 11:40 ` Dave Hansen
2024-09-15 12:25 ` John
2024-09-15 12:58 ` Dave Hansen
2024-09-15 18:42 ` John
2024-09-17 18:22 ` John
2024-09-17 18:45 ` H. Peter Anvin
2024-09-15 12:49 ` Borislav Petkov
2024-09-15 12:53 ` Dave Hansen
2024-09-17 21:33 ` Hanabishi
2024-09-18 19:02 ` John
2024-09-18 20:25 ` Hanabishi
2024-09-18 21:14 ` John
2024-09-18 21:48 ` Hanabishi
2024-09-18 23:07 ` John
2024-09-16 5:14 ` WangYuli
2024-09-24 7:00 ` kernel test robot
2024-09-24 13:38 ` Dave Hansen [this message]
2024-09-24 17:40 ` John
2024-09-26 1:43 ` Oliver Sang
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=6e6ffa78-1f8c-4f32-9fe7-141cb39d06d2@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=tglx@linutronix.de \
--cc=therealgraysky@proton.me \
--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
all inboxes | Powered by JetHome®