From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 1/7] MIPS: KVM/locore.S: Don't preserve host ASID around vcpu_run Date: Mon, 9 May 2016 16:22:33 +0200 Message-ID: <57309D29.6010903@redhat.com> References: <1462541784-22128-1-git-send-email-james.hogan@imgtec.com> <1462541784-22128-2-git-send-email-james.hogan@imgtec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Paul Burton , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , linux-mips@linux-mips.org, kvm@vger.kernel.org To: James Hogan , Ralf Baechle Return-path: In-Reply-To: <1462541784-22128-2-git-send-email-james.hogan@imgtec.com> Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-subscribe: List-owner: List-post: List-archive: List-Id: kvm.vger.kernel.org On 06/05/2016 15:36, James Hogan wrote: > - It is actually redundant, since the host ASID will be restored > correctly by kvm_arch_vcpu_put(), which is called almost immediately > after kvm_arch_vcpu_ioctl_run() returns. What happens if the guest does a rogue access to the area where the host kernel resides? Would that cause a wrong entry in the TLB? Paolo