[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] MSR load lists on Harpertown


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
  • From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  • Date: Tue, 18 Dec 2018 09:56:26 +0000
  • Autocrypt: addr=andrew.cooper3@xxxxxxxxxx; prefer-encrypt=mutual; keydata= mQINBFLhNn8BEADVhE+Hb8i0GV6mihnnr/uiQQdPF8kUoFzCOPXkf7jQ5sLYeJa0cQi6Penp VtiFYznTairnVsN5J+ujSTIb+OlMSJUWV4opS7WVNnxHbFTPYZVQ3erv7NKc2iVizCRZ2Kxn srM1oPXWRic8BIAdYOKOloF2300SL/bIpeD+x7h3w9B/qez7nOin5NzkxgFoaUeIal12pXSR Q354FKFoy6Vh96gc4VRqte3jw8mPuJQpfws+Pb+swvSf/i1q1+1I4jsRQQh2m6OTADHIqg2E ofTYAEh7R5HfPx0EXoEDMdRjOeKn8+vvkAwhviWXTHlG3R1QkbE5M/oywnZ83udJmi+lxjJ5 YhQ5IzomvJ16H0Bq+TLyVLO/VRksp1VR9HxCzItLNCS8PdpYYz5TC204ViycobYU65WMpzWe LFAGn8jSS25XIpqv0Y9k87dLbctKKA14Ifw2kq5OIVu2FuX+3i446JOa2vpCI9GcjCzi3oHV e00bzYiHMIl0FICrNJU0Kjho8pdo0m2uxkn6SYEpogAy9pnatUlO+erL4LqFUO7GXSdBRbw5 gNt25XTLdSFuZtMxkY3tq8MFss5QnjhehCVPEpE6y9ZjI4XB8ad1G4oBHVGK5LMsvg22PfMJ ISWFSHoF/B5+lHkCKWkFxZ0gZn33ju5n6/FOdEx4B8cMJt+cWwARAQABtClBbmRyZXcgQ29v cGVyIDxhbmRyZXcuY29vcGVyM0BjaXRyaXguY29tPokCOgQTAQgAJAIbAwULCQgHAwUVCgkI CwUWAgMBAAIeAQIXgAUCWKD95wIZAQAKCRBlw/kGpdefoHbdD/9AIoR3k6fKl+RFiFpyAhvO 59ttDFI7nIAnlYngev2XUR3acFElJATHSDO0ju+hqWqAb8kVijXLops0gOfqt3VPZq9cuHlh IMDquatGLzAadfFx2eQYIYT+FYuMoPZy/aTUazmJIDVxP7L383grjIkn+7tAv+qeDfE+txL4 SAm1UHNvmdfgL2/lcmL3xRh7sub3nJilM93RWX1Pe5LBSDXO45uzCGEdst6uSlzYR/MEr+5Z JQQ32JV64zwvf/aKaagSQSQMYNX9JFgfZ3TKWC1KJQbX5ssoX/5hNLqxMcZV3TN7kU8I3kjK mPec9+1nECOjjJSO/h4P0sBZyIUGfguwzhEeGf4sMCuSEM4xjCnwiBwftR17sr0spYcOpqET ZGcAmyYcNjy6CYadNCnfR40vhhWuCfNCBzWnUW0lFoo12wb0YnzoOLjvfD6OL3JjIUJNOmJy RCsJ5IA/Iz33RhSVRmROu+TztwuThClw63g7+hoyewv7BemKyuU6FTVhjjW+XUWmS/FzknSi dAG+insr0746cTPpSkGl3KAXeWDGJzve7/SBBfyznWCMGaf8E2P1oOdIZRxHgWj0zNr1+ooF /PzgLPiCI4OMUttTlEKChgbUTQ+5o0P080JojqfXwbPAyumbaYcQNiH1/xYbJdOFSiBv9rpt TQTBLzDKXok86LkCDQRS4TZ/ARAAkgqudHsp+hd82UVkvgnlqZjzz2vyrYfz7bkPtXaGb9H4 Rfo7mQsEQavEBdWWjbga6eMnDqtu+FC+qeTGYebToxEyp2lKDSoAsvt8w82tIlP/EbmRbDVn 7bhjBlfRcFjVYw8uVDPptT0TV47vpoCVkTwcyb6OltJrvg/QzV9f07DJswuda1JH3/qvYu0p vjPnYvCq4NsqY2XSdAJ02HrdYPFtNyPEntu1n1KK+gJrstjtw7KsZ4ygXYrsm/oCBiVW/OgU g/XIlGErkrxe4vQvJyVwg6YH653YTX5hLLUEL1NS4TCo47RP+wi6y+TnuAL36UtK/uFyEuPy wwrDVcC4cIFhYSfsO0BumEI65yu7a8aHbGfq2lW251UcoU48Z27ZUUZd2Dr6O/n8poQHbaTd 6bJJSjzGGHZVbRP9UQ3lkmkmc0+XCHmj5WhwNNYjgbbmML7y0fsJT5RgvefAIFfHBg7fTY/i kBEimoUsTEQz+N4hbKwo1hULfVxDJStE4sbPhjbsPCrlXf6W9CxSyQ0qmZ2bXsLQYRj2xqd1 bpA+1o1j2N4/au1R/uSiUFjewJdT/LX1EklKDcQwpk06Af/N7VZtSfEJeRV04unbsKVXWZAk uAJyDDKN99ziC0Wz5kcPyVD1HNf8bgaqGDzrv3TfYjwqayRFcMf7xJaL9xXedMcAEQEAAYkC HwQYAQgACQUCUuE2fwIbDAAKCRBlw/kGpdefoG4XEACD1Qf/er8EA7g23HMxYWd3FXHThrVQ HgiGdk5Yh632vjOm9L4sd/GCEACVQKjsu98e8o3ysitFlznEns5EAAXEbITrgKWXDDUWGYxd pnjj2u+GkVdsOAGk0kxczX6s+VRBhpbBI2PWnOsRJgU2n10PZ3mZD4Xu9kU2IXYmuW+e5KCA vTArRUdCrAtIa1k01sPipPPw6dfxx2e5asy21YOytzxuWFfJTGnVxZZSCyLUO83sh6OZhJkk b9rxL9wPmpN/t2IPaEKoAc0FTQZS36wAMOXkBh24PQ9gaLJvfPKpNzGD8XWR5HHF0NLIJhgg 4ZlEXQ2fVp3XrtocHqhu4UZR4koCijgB8sB7Tb0GCpwK+C4UePdFLfhKyRdSXuvY3AHJd4CP 4JzW0Bzq/WXY3XMOzUTYApGQpnUpdOmuQSfpV9MQO+/jo7r6yPbxT7CwRS5dcQPzUiuHLK9i nvjREdh84qycnx0/6dDroYhp0DFv4udxuAvt1h4wGwTPRQZerSm4xaYegEFusyhbZrI0U9tJ B8WrhBLXDiYlyJT6zOV2yZFuW47VrLsjYnHwn27hmxTC/7tvG3euCklmkn9Sl9IAKFu29RSo d5bD8kMSCYsTqtTfT6W4A3qHGvIDta3ptLYpIAOD2sY3GYq2nf3Bbzx81wZK14JdDDHUX2Rs 6+ahAA==
  • Cc: "Lai, Paul C" <paul.c.lai@xxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxx>, Xen-devel List <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Tue, 18 Dec 2018 09:56:38 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Openpgp: preference=signencrypt

On 18/12/2018 02:17, Tian, Kevin wrote:
>> From: Andrew Cooper [mailto:andrew.cooper3@xxxxxxxxxx]
>> Sent: Monday, December 17, 2018 10:21 PM
>>
>> On 17/12/2018 13:09, Andrew Cooper wrote:
>>> On 17/12/2018 02:39, Tian, Kevin wrote:
>>>>>>> After some investigation, it turns out that after vmentry, while the
>>>>>>> load list has the value 0xd01 (NXE, LMA, LME, SCE), the value loaded
>>>>>>> into hardware is 0xd00 (NXE, LMA, LME).
>>>>>>>
>>>>>>> I.e. when an MSR load list is used for EFER, we resume the guest with
>>>>>>> SCE cleared.  This is rather terminal for 64bit guests, as
>>>>>>> syscall/sysret instructions take a #UD fault.
>>>>>>>
>>>>>>> I can't see anything relevant in the Specification Update for this
>>>>>>> processor.
>>>>>>>
>>>>>>> I've confirmed that by not using a load list, the current value in EFER
>>>>>>> is preserved once the vmentry is complete, and by disabling the EFER
>>>>>>> intercept, I can re-set SCE in non-root context and have syscall/sysret
>>>>>>> work correctly.
>>>>>>>
>>>>>>> However, given this behaviour, I can't think of any way to context
>>>>>>> switch NX properly, and leave 64bit guests in a working state.
>>>>>>>
>>>>>>> Do you have any suggestions?
>>>>>>>
>>>>> I'm checking internally whether it's a known issue.
>>>> from feedbacks that I collected so far, no one is aware of this issue.
>>>>
>>>>> btw did you try upgrading to a newer microcode?
>>>>>
>>>> while I'm approaching more channels, does it work by directly
>>>> WRMSR to EFER just before VMENTRY for above special case (
>>>> thus remove EFER from MSR load/save list), if ucode update
>>>> also fails? there is just a small window where NX might be wrong
>>>> setting for Xen, but it might be OK for that carefully-baked code
>>>> snippet?
>>> Apologies for the delay.  I was travelling last week.
>>>
>>> We cannot load the full guest's EFER value in Xen context.  If the guest
>>> has NX disabled, the next stack access in Xen will fault because the NX
>>> bit becomes reserved when EFER.NXE is clear.
>>>
>>> As for the more general case of loading the guests EFER value (ignoring
>>> NXE), we already know that works, because it is how Xen functioned for a
>>> decade.
>>>
>>> I see that the latest production microcode on otcshare is slightly newer
>>> than exists in the microcode_ctl package.  I'll give it a spin.
>> The behaviour is still the same, even with the latest microcode:
>>
>> (XEN) microcode: CPU0 updated from revision 0x60f to 0x612, date =
>> 2015-08-02
>>
> Just confirmed that there is no erratum which could explain above 
> behavior.
>
> I see several options here:
>
> a) load guest EFER in Xen context, just before vmentry. make sure no stack 
> access between load and VM enter. but it sounds messy to add such sku
> specific workaround in that common path (especially just for an old one);
>
> b) leave guest following Xen NXE setting on Harpertown. doing so bears
> with limitation as what fd32dcfe tries to fix, but it's better than syscall
> error in 64bit guest. also not clean since some ad-hoc logic that is removed
> by fd32dcfe may have to be added back;
>
> c) leave above issue unfixed. Harpertown is pretty old...
>
> d) more debug whether above is caused by other software bug

Option a) is not possible.  While we could in principle turn the line of
pop gpr's into movs and avoid the stack accesses, we will triple fault
if an NMI/#MC hits.

As for option d), I'm quite certain at this point that it is a
hardware/microcode issue, rather than a software issue.

I'd prefer to leave Harpertown cores working than simply dismissing them
at this point, because they are still useful for compatibility testing. 
TBH,  I was expecting option b) to be the outcome.

I don't suppose there is any chance of this being published as an
erratum which I can reference in the source code?

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.