From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH v4 00/17] x86/split_lock: Enable #AC exception for split locked accesses Date: Mon, 4 Mar 2019 16:55:05 -0500 Message-ID: <20190304215505.GC30350@char.us.oracle.com> References: <1551494711-213533-1-git-send-email-fenghua.yu@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Thomas Gleixner , Ingo Molnar , Borislav Petkov , H Peter Anvin , Paolo Bonzini , Dave Hansen , Ashok Raj , Peter Zijlstra , Ravi V Shankar , Xiaoyao Li , linux-kernel , x86 , kvm@vger.kernel.org To: Fenghua Yu Return-path: Content-Disposition: inline In-Reply-To: <1551494711-213533-1-git-send-email-fenghua.yu@intel.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org > This capability may also find usage in cloud. A user process with split > lock running in one guest can block other cores from accessing shared > memory during its split locked memory access. That may cause overall > system performance degradation. "shared memory" ? As in memory shared between two guests? > > Split lock may open a security hole where malicious user code may slow > down overall system by executing instructions with split lock. How much slowdown are we talking?