[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BYAPR21MB16883A15812E1D20FC28DF76D73FA@BYAPR21MB1688.namprd21.prod.outlook.com>
Date: Fri, 21 Jul 2023 14:21:42 +0000
From: "Michael Kelley (LINUX)" <mikelley@...rosoft.com>
To: David Laight <David.Laight@...LAB.COM>,
Peter Zijlstra <peterz@...radead.org>
CC: KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"wei.liu@...nel.org" <wei.liu@...nel.org>,
Dexuan Cui <decui@...rosoft.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"hpa@...or.com" <hpa@...or.com>, "x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: RE: [PATCH 1/1] x86/hyperv: Disable IBT when hypercall page lacks
ENDBR instruction
From: David Laight <David.Laight@...LAB.COM> Sent: Friday, July 21, 2023 7:07 AM
>
> ...
> > I realized in the middle of the night that my reply was nonsense. :-(
> > pr_warn() makes the message visible when pr_info() might not. I'm
> > happy to change to pr_warn().
>
> PANIC_ON_WARN??
>
panic_on_warn applies to WARN() and variants. pr_warn() is unrelated;
it's just kernel logging level 4 vs. logging level 6 for pr_info().
Michael
Powered by blists - more mailing lists