From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id B0A16C433F5
	for <linux-kernel@archiver.kernel.org>; Tue,  4 Oct 2022 17:45:30 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S229607AbiJDRp2 (ORCPT <rfc822;linux-kernel@archiver.kernel.org>);
        Tue, 4 Oct 2022 13:45:28 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54608 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S230005AbiJDRpL (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 4 Oct 2022 13:45:11 -0400
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 89DAAB1E7;
        Tue,  4 Oct 2022 10:44:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
  d=intel.com; i=@intel.com; q=dns/txt; s=Intel;
  t=1664905497; x=1696441497;
  h=message-id:date:mime-version:from:to:subject:
   content-transfer-encoding;
  bh=NTKKHeoEYZWSl1Ry7nAI5w9pUYcyarim9OndgbtenE4=;
  b=nC60IhX0iXMQ2eHdvjvmwLh3QG/4oEOC93JUaJJItfCcH0Q1sf9L5OoA
   Tr9dB11S6ZFNuA4nJwQwWAHm4GVEwVbA3lcXvciF6ARK1prcaIyAnl0CB
   yHVx72PTa22w0rCQS+eWXZU+OUK27x8cKQv66jzHknJEPPmbFzVxA52+i
   sgW4wY7ACKIEKSWLPynCkkYWt4/7WZAqJduNeaBl3HEjRlu+sTKZbWjhj
   u9CTiddqKEdXrwMrmosm5pAx/Ya6wHTL1BfMhxmbBIZ3efk8iyWjT5/0q
   YwtW4c+T8cHTPo/BjR3AtMluMy9rBUKUxF3Pw9R6dvEmMO+Ga/+Qy0MNd
   Q==;
X-IronPort-AV: E=McAfee;i="6500,9779,10490"; a="290213451"
X-IronPort-AV: E=Sophos;i="5.95,158,1661842800"; 
   d="scan'208";a="290213451"
Received: from orsmga006.jf.intel.com ([10.7.209.51])
  by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Oct 2022 10:34:12 -0700
X-IronPort-AV: E=McAfee;i="6500,9779,10490"; a="601706208"
X-IronPort-AV: E=Sophos;i="5.95,158,1661842800"; 
   d="scan'208";a="601706208"
Received: from samrober-mobl.amr.corp.intel.com (HELO [10.209.85.136]) ([10.209.85.136])
  by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Oct 2022 10:34:11 -0700
Message-ID: <547a1203-0339-7ad2-9505-eab027046298@intel.com>
Date:   Tue, 4 Oct 2022 10:34:11 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.11.0
Content-Language: en-US
From:   Dave Hansen <dave.hansen@intel.com>
To:     Sean Christopherson <seanjc@google.com>,
        Paolo Bonzini <pbonzini@redhat.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
        x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
        kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
        Arjan van de Ven <arjan@linux.intel.com>
Subject: Finish removing MPX from arch/x86?
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

We zapped the userspace MPX ABIs and most of its supporting code in here:

	45fc24e89b7c ("x86/mpx: remove MPX from arch/x86")

But, the XSAVE enabling and KVM code were left in place.  This let folks
at least keep running guests with MPX.

It's been a couple of years and I don't think I've had a single person
opine about the loss of MPX.  Intel also followed through and there's no
MPX to be found on newer CPUs like my "Tiger Lake" 11th Gen Intel(R)
Core(TM) i7-1165G7.

Is it time to zap MPX from arch/x86/kvm/?