[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 15/21] libs/guest: obtain a compatible cpu policy from two input ones
- To: Wei Liu <wl@xxxxxxx>
- From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Date: Wed, 21 Apr 2021 13:26:49 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CjA3XpiWFUlWc655WKA0W69uVPRIRbj68f3OjbzNZrQ=; b=dneIymlwv8/f/7C9la0j92tOoh5e7xNfykwP+Q1jFeS/sRswEq/U0wvTBCrPF/BRIwHwqMH6/VfqNLVgxoQH4VUhKUGSYcNXxc852NszF0DVOiubDy4udA6Wtq13IPI5PlBVFyYtk9EJkqSCmxMy3xfH+4P4WMR0dsaVodzbcgRJiU5oVBUDbeOrcACjlvASMCnPYCvmvrecQqhyKp1WVJElBk4sbcVUCE9tb+YL7ML4wUXNoYSlKO0dMyWPlMJiLAYhy55fcc3wicUcQ+CLYGGMW3X52K3tEmILNhJ8vSju6zPS1Z9JQnoP9hRDS41OAe9D/2M/T/rZgzgnig9K6g==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DUbGH8Z6A5NrcFASkPGFWj5pgr82Nc0cpyJwO2uDwbG5Xp8z5Xe8UZkoQPkf1S7Am24oH30FIRqSxxcMRSrwpsYQL2pXgr9jqRzXrQ/GlCy2iNayUzbqod+tGAFR64/qAk/Ah2harJKXN5C62I2SjVzh995JGE+JTKknDZFgL6yAX3xkJ0EqxFNL8cutnGDjJDXGh+zGdoSsHI7mHl9UgpjDqp7yqdgGYwnsfq1b82b3PGm4/PU0A5fGMWdnofqxjnynYeE5jKSLTyLRhpZdW9fecUZh7us7FD9SxwYphDEH/qpB5zae0PUypbHEUGCU54PGyqBuSnga920XrJBWcQ==
- Authentication-results: esa5.hc3370-68.iphmx.com; dkim=pass (signature verified) header.i=@citrix.onmicrosoft.com
- Cc: <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Ian Jackson <iwj@xxxxxxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>
- Delivery-date: Wed, 21 Apr 2021 11:27:05 +0000
- Ironport-hdrordr: A9a23:sOuXR6E6Lffm/PrVpLqFe5TXdLJzesId70hD6mlYcjYQWtCEls yogfQQ3QL1jjFUY307hdWcIsC7L0/03aVepa0cJ62rUgWjgmunK4l+8ZDvqgeOJwTXzcQY76 tpdsFFZOHYJURmjMr8/QmzG8shxt7Cy6yzmeLC1R5WLT1CQYsI1XYeNi+wFEpqSA5aQbc4Do Ob/MpbpzymEE5nE/iTLH8DQuTFupn3hIvrCCR2fSIPxSuvqXeT6LD8GwWFxRt2aVJy6Jor7G StqX2d2oyNqPe+oyWss1P7z5MTo9f5z8sGOcrksLloFhzJqiKFILtsQKeDujddmpDe1H8PnM PXqxkte+RfgkmhBl2dmhfm1wn+3DtG0RaLojX08BiTw72KeBsAB8VMno5feBfCgnBQx+1U66 5Xw3mf86NeEBKoplWN2/HzSxpomkCoyEBS6NI7sno3a/p4VJZh6aYb/E9TDa4aGjP75I0NAI BVfb/hzccTXlWAY3/DuG5zhPSqQ3QoBx+DBnMPo8qPzlFt7TxE5npd4PZasmYL9Zo7RZUBz+ PYMp5wnLULasMNd6pyCMoIXMPfMB2DfTv8dEapZXj3HqAOPHzA77Tt5q8u2e2scJsUiLMvhZ XoSjpjxC4PUnOrLffL8IxA8xjLTmn4dy/q0Nti659wvaC5bKb3MBeEVEsln6Kb0rQiK/yef8 z2FINdAvflI2erM51OxRfCV55bLmRbf9YSvvo9RlKSsuPGIoDnrYXgAbTuDYuoNQxhdnL0A3 MFUjS2Dt5H9FqXVnjxhwWUe36FQD27wbtAVIzhu8QDwokEMYNB9iIPj06i282NITpe9og/fE 50JqLbgrq2zFPGuVrg3iFMAF5wH0xV6LLvXzdhvgkRKX75dr4FppG5dX1N2mCEYjtyVdnfHg Iah1kfw9P4E7WggQQZT/63OGOTiHUe4FiQSY0Hp6GF7cD5PrUiDpgnX6R1PR7RFwN8nDtrrG srUn5GembvUhfVzYm1hp0dA+/SM/Nmhh2wHMJSoXXD8XmHqdoXXXsdVT62WcuxiQIjLgAkwW FZwus6uv6tiDyvIWwwjKAdPEdXYGqaOr5AET+IfZ5ZgLztZQF2Q1qbnDDysWBBRkPas2Epwk DxJyydfv/GRmBQvX1VyY7G2lJ5fGf1RTM6VllK9alGUUjWsHd61uGGIpep22yKc10Y36U2Kz feewYfJQto2vG63BOYgyy5CH0j35kiV9atSogLQvX24DeAOYeInaYJE7to555jLsnpqfJOfu SFeQOZRQmIfd8B6kiwnDICNyZ1onV/zq+t9x3h8WSi3HkwRdDVO09rQrkHI9eaq0joLsz4pK lRvJYQh6+XNG60V/utjYfwRBRHIgnIoWG3Q/ozwKok9Z4ahf9WJd3jTTDM1Ht7xx0wI8f/qV MGTM1AkcX8E74qW/ZXRjlQ8VUonumeNUcHsgT5BeklYFEm5kWrSO+h0v7tqbA1BFeGqxa1EV 6D8zdF9/OtZVrI6ZcqT4YxK39Rck4y9TBL+/6DbZTZDEGPe/tY9FS3dl+7f7k1ctnJJZwg6j J76cqPhemZam7R3x3RpyJyJuZ2yFmcKPnCST6kKKpv6Ny1OVOFn6us7oqStV7MOESGQnVdo5 ZEe0wWZtlEkR84guQMo3GPdpA=
- Ironport-sdr: jMg5UdUImqcflGpiBpva7Y94D4JFgQC9vpTxJTm7es/2rQg+8g5XcgYWlpp2+Q/THoksqNoFIs 1dGVV+/KsHBMQy19vPJSYz0FzqukHOo17ITQXOCred/8vsWCvGd7FVtIxrrvqMezjrHaSta7lt kTjzpgrEkX8fnJWYI0cSPaUksnfBDK22E+yVxjzj0CpfqJnXmx13hhl9seyFH9WA5m4nF3ffGv lhJnOTqpu1TtZTKU7g37EVJpgpC8lgZ/uDlv6M/F3bFmj/lES09m+JcqquX8j6Z4C4YmQMh7K2 wyo=
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Wed, Apr 21, 2021 at 10:22:39AM +0000, Wei Liu wrote:
> On Tue, Apr 13, 2021 at 04:01:33PM +0200, Roger Pau Monne wrote:
> > Introduce a helper to obtain a compatible cpu policy based on two
> > input cpu policies. Currently this is done by and'ing all CPUID leaves
> > and MSR entries, except for MSR_ARCH_CAPABILITIES which has the RSBA
> > bit or'ed.
> >
>
> I thought canonical source for compatibility was to be put into the
> hypervisor, thus all this functionality would be in the hypervisor. Am I
> misremembering?
Andrew said something similar on v1, but I'm not able to figure how
this would be used by the hypervisor.
It's my understating that the toolstack will attempt to generate a CPU
policy and forward it to the hypervisor, which will either accept or
reject it based on the capabilities of the system. I'm not sure I see
why we would need to give the hypervisor two policies in order to
generate a resulting compatible one - it should all be done by the
toolstack AFAICT.
If there's a use case for this being in the hypervisor I'm happy to
add it there, but so far I haven't been able to come up with one
myself, and hence I don't see the need to make the code available.
Thanks, Roger.
|
