From: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
To: Peter Zijlstra <peterz@infradead.org>,
Bruno Goncalves <bgoncalv@redhat.com>
Cc: <arjan@linux.intel.com>, <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [6.5.0-rc1] unchecked MSR access error: RDMSR from 0xe2 at rIP: 0xffffffff87090227 (native_read_msr+0x7/0x40) (intel_idle_init_cstates_icpu)
Date: Tue, 11 Jul 2023 20:37:51 +0200 [thread overview]
Message-ID: <0837a34c-f66e-aa04-d4a7-b032d3dbab7a@intel.com> (raw)
In-Reply-To: <20230711132553.GN3062772@hirez.programming.kicks-ass.net>
On 7/11/2023 3:25 PM, Peter Zijlstra wrote:
> On Tue, Jul 11, 2023 at 02:55:57PM +0200, Peter Zijlstra wrote:
>
>> Oohh, this vm-guest mode is new :/ But it doesn't make sense, that
>> commit babbles something about waking CPUs from idle to do TLB
>> invalidate, but that shouldn't be the case, that's what we have
>> kvm_flush_tlb_multi() for, it should avoid the IPI and flush on
>> vcpu-enter.
>>
>> Arjan, what is the actual problem you're trying to solve any why hide
>> this in intel_idle ?
>
> static __always_inline int __intel_idle_hlt(struct cpuidle_device *dev,
> struct cpuidle_driver *drv, int index)
> {
> raw_safe_halt();
> raw_local_irq_disable();
> return index;
> }
>
> Which does:
>
> STI
> HLT
> CLI
>
> static __cpuidle int intel_idle_hlt_irq_on(struct cpuidle_device *dev,
> struct cpuidle_driver *drv, int index)
> {
> int ret;
>
> raw_local_irq_enable();
> ret = __intel_idle_hlt(dev, drv, index);
> raw_local_irq_disable();
>
> return ret;
> }
>
> That is nonsensical code; because now you have:
>
> STI
> STI
> HLT
> CLI
> CLI
>
> And that makes sense how?
>
> Rafael, can we please just pull these patches and try again later?
I think you mean "revert"?
That can be done, but maybe it can be fixed instead?
next prev parent reply other threads:[~2023-07-11 18:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 9:11 Bruno Goncalves
2023-07-11 11:24 ` Peter Zijlstra
2023-07-11 12:25 ` Bruno Goncalves
2023-07-11 12:55 ` Peter Zijlstra
2023-07-11 13:15 ` Peter Zijlstra
2023-07-11 13:25 ` Peter Zijlstra
2023-07-11 18:37 ` Wysocki, Rafael J [this message]
2023-07-11 18:39 ` Arjan van de Ven
2023-07-14 21:11 ` Peter Zijlstra
2023-07-14 21:47 ` Arjan van de Ven
2023-07-14 22:02 ` Peter Zijlstra
2023-07-14 21:10 ` Peter Zijlstra
2023-07-14 21:45 ` Arjan van de Ven
2023-07-14 21:55 ` Peter Zijlstra
2023-07-14 22:28 ` Peter Zijlstra
2023-07-11 14:26 ` Arjan van de Ven
2023-07-11 15:32 ` Peter Zijlstra
2023-07-11 14:22 ` Arjan van de Ven
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=0837a34c-f66e-aa04-d4a7-b032d3dbab7a@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=arjan@linux.intel.com \
--cc=bgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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®