Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752795AbbD3Tc2 (ORCPT ); Thu, 30 Apr 2015 15:32:28 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:44012 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752617AbbD3Tc0 (ORCPT ); Thu, 30 Apr 2015 15:32:26 -0400 Message-ID: <554282BC.5000103@oracle.com> Date: Thu, 30 Apr 2015 15:30:04 -0400 From: Boris Ostrovsky User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Andy Lutomirski CC: Konrad Rzeszutek Wilk , David Vrabel , "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , "linux-kernel@vger.kernel.org" , "xen-devel@lists.xenproject.org" , linux@eikelenboom.it Subject: Re: [PATCH] hypervisor/x86/xen: Unset X86_BUG_SYSRET_SS_ATTRS on Xen PV guests References: <1430420925-20474-1-git-send-email-boris.ostrovsky@oracle.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: aserv0022.oracle.com [141.146.126.234] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1432 Lines: 34 On 04/30/2015 03:17 PM, Andy Lutomirski wrote: > On Thu, Apr 30, 2015 at 12:08 PM, Boris Ostrovsky > wrote: >> Commit 61f01dd941ba ("x86_64, asm: Work around AMD SYSRET SS descriptor >> attribute issue") makes AMD processors set SS to __KERNEL_DS in >> __switch_to() to deal with cases when SS is NULL. >> >> This breaks Xen PV guests who do not want to load SS with__KERNEL_DS. >> >> Since the problem that the commit is trying to address would have to be >> fixed in the hypervisor (if it in fact exists under Xen) there is no >> reason to set X86_BUG_SYSRET_SS_ATTRS flag for PV VPCUs here. >> > Seems reasonable. > > Have you run the test case on a Xen PV guest on AMD? It's possible > that Xen is affected, since the old accidental workaround that we > deleted was in the vdso and probably would have worked on Xen. Is there a specific test that would trigger this bug? I booted/suspended/resumed a bunch of various guest types on both AMD and Intel but not much more than that. What is the commit that you deleted? I doubt that a change in the guest could suddenly start triggering this issue but I will take a look at hypervisor code. -boris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/