From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.0 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8FDA1C433DF for ; Fri, 21 Aug 2020 10:12:53 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 252AB20656 for ; Fri, 21 Aug 2020 10:12:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=aepfle.de header.i=@aepfle.de header.b="Zza7FlIF" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 252AB20656 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=aepfle.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1k942L-0006sW-DY; Fri, 21 Aug 2020 10:12:41 +0000 Received: from all-amaz-eas1.inumbo.com ([34.197.232.57] helo=us1-amaz-eas2.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1k942I-0006sE-29 for xen-devel@lists.xenproject.org; Fri, 21 Aug 2020 10:12:40 +0000 X-Inumbo-ID: f033baaa-4fb1-46d5-93a8-ebb03960ef8e Received: from mo4-p00-ob.smtp.rzone.de (unknown [85.215.255.25]) by us1-amaz-eas2.inumbo.com (Halon) with ESMTPS id f033baaa-4fb1-46d5-93a8-ebb03960ef8e; Fri, 21 Aug 2020 10:12:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1598004755; s=strato-dkim-0002; d=aepfle.de; h=Message-ID:Subject:Cc:To:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH:From: Subject:Sender; bh=yDScki7LVBF/OMK4i9Zan/qzWnU781I0F33uEZg/VSc=; b=Zza7FlIFY8TBoNbCLaUWZjgLJ5JsF8IWNEbKH1Gm7jnDtBixhtYI2hMblOrLQRivei f/Tgt+Tllv44juplKmh3nFReRS03p4uNJPjB3hJI6Zj9lrhi6Q/AHRcasU/a3HdaiMJX BbPJSaS5ApasHlOeUf5KMQ8NHcSecylKH2s97QPvqR3wewxERWNRUSp6Dzwc31+k0gjD bOABGXWAZ8nnAO8Jo0BK3PsboWiVHRZU4sBgWwkkpHXv8Y+62WZ9PFeKmYq4SWpkj37+ 3Fd2SpFC7fiHFF4poJiXnr5PuEgRErP1j2oHWnhHMU7twd8HsuoPPh/lrWvyyoEWDBhP gU4w== X-RZG-AUTH: ":P2EQZWCpfu+qG7CngxMFH1J+3q8wa/QLpd5ylWvMDXdoX8l8pYAcz5OTWe6X" X-RZG-CLASS-ID: mo00 Received: from sender by smtp.strato.de (RZmta 46.10.7 DYNA|AUTH) with ESMTPSA id 60ad29w7LACWAIr (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Fri, 21 Aug 2020 12:12:32 +0200 (CEST) Date: Fri, 21 Aug 2020 12:12:24 +0200 From: Olaf Hering To: Andrew Cooper Cc: xen-devel@lists.xenproject.org Subject: shared features in cpuid Message-ID: <20200821121224.24cecb4e.olaf@aepfle.de> X-Mailer: Claws Mail 2020.07.13 (GTK+ 2.24.32; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/UojaCl4ZRN7UbfvfmYMHGNj"; protocol="application/pgp-signature" X-BeenThere: xen-devel@lists.xenproject.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" --Sig_/UojaCl4ZRN7UbfvfmYMHGNj Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable While reviewing changed behavior in 'xen-cpuid -d' output between Xen 4.8 a= nd 4.9 I found commit 20e92c97f904aa460e2223c30dcad36c234496b6 ("x86/cpuid:= Only recalculate the shared feature bits once"). I wonder what the mentioned "cross-vendor case" in the comment, which was r= emoved from sanitise_featureset(), really means. Does Xen attempt to support domU migration between AMD and Intel hardware? Olaf --Sig_/UojaCl4ZRN7UbfvfmYMHGNj Content-Type: application/pgp-signature Content-Description: Digitale Signatur von OpenPGP -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE97o7Um30LT3B+5b/86SN7mm1DoAFAl8/nggACgkQ86SN7mm1 DoBgIA//cwPi82/1a2+cSrGidqs66swizt2JrGIN48P9dremL9ojqmBZZH1gBfwD /1YG3Rp6q+6fxZjf3YfMM7DHXRzzjd43bYay/6N+vspcaCk1Y31ajzHHuPbOlF+G pADigU6m2FTaVPHSobhN4VhWlA73QtvSoxrCeWhRtBCsHnUGmm9M7w362hFmPLhC dEgz/lneMX2hQpGdjltzvFBH5Xg/YyLgDrBMMfV+PGsqgqNDOhISozyXRiukoUS/ AQVr9vOeO0XzzZ3LKkTAKNDlz1jP7C7YpYU7/jkA8ESNc2VnWZoW44EnbVS3X763 ln4YbkQOTAmNKEQLU7igsZI98XoEypv4BbSL8TCY5ZfYgssIxb7aCSn9YRsXkXlU ILQ49ubzSoq62ypqEkPM3aYmMKLWgNa9JnEKuzQPOeZgW08qtJJPWiKp7YOlIN/o N3yfH6nlYDbvBDIOc/iFk1e4LJQryR8chddpBWDFVVE4yn9ZFHhVwXFCrRM2O2I7 Ciz9APgZutVtugnE1K3qfBuapSfKqway75a5RjaujQo6zX4I95aOCGUcA+fQrbrj aCCpG2H6OKVigT/21scbLWnoUtAnh7/SgeTqlAKL+88IebAEb7BGgkDKh9oSN498 96O5DxnCqd5qOXC7jDTtrZBtY3lo8ftpKEToxS1QKyuh+q+E1qU= =RDqJ -----END PGP SIGNATURE----- --Sig_/UojaCl4ZRN7UbfvfmYMHGNj--