From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vitaly Kuznetsov Subject: Re: [PATCH RFC 1/3] x86/kvm/vmx: read MSR_FS_BASE from current->thread Date: Mon, 05 Mar 2018 10:56:11 +0100 Message-ID: <874llu26dg.fsf@vitty.brq.redhat.com> References: <20180302105503.24428-1-vkuznets@redhat.com> <20180302105503.24428-2-vkuznets@redhat.com> Mime-Version: 1.0 Content-Type: text/plain Cc: kvm list , LKML , X86 ML , Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" To: Andy Lutomirski Return-path: In-Reply-To: (Andy Lutomirski's message of "Fri, 2 Mar 2018 20:18:18 +0000") Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org Andy Lutomirski writes: > On Fri, Mar 2, 2018 at 10:55 AM, Vitaly Kuznetsov wrote: >> vmx_save_host_state() is only called from kvm_arch_vcpu_ioctl_run() so >> the context is pretty well defined >> > > True. > >> and MSR_FS_BASE should always be >> equal to current->thread.fsbase. > > Not true. current->thread.fsbase is almost entirely undefined in this > context. What you *could* do is export save_fsgs() and call it first. > When FSGSBASE support lands (which will happen eventually!), the code > in your patch will be completely wrong. > > Admittedly, your patch isn't 100% bogus, but the reason is subtle and > you need lots of comments there *and* in save_fsgs(). Thank you Andy, I'll take a look. -- Vitaly