Messages in this thread | | | From | Thomas Gleixner <> | Subject | Re: [PATCH v5 3/9] x86/split_lock: Re-define the kernel param option for split_lock_detect | Date | Tue, 24 Mar 2020 19:42:29 +0100 |
| |
Sean Christopherson <sean.j.christopherson@intel.com> writes: > On Tue, Mar 24, 2020 at 11:40:18AM +0100, Thomas Gleixner wrote: >> >> It's very much about whether the host is split lock clean. >> >> If your host kernel is not, then this wants to be fixed first. If your >> host application is broken, then either fix it or use "warn". > > The "kvm only" option was my suggestion. The thought was to provide a way > for users to leverage KVM to debug/test kernels without having to have a > known good kernel and/or to minimize the risk of crashing their physical > system. E.g. debug a misbehaving driver by assigning its associated device > to a guest.
warn is giving you that, right? I won't crash the host because the #AC triggers in guest context.
Thanks,
tglx
| |