From: Paolo Bonzini <pbonzini@redhat.com>
To: James Hogan <james.hogan@imgtec.com>, Ralf Baechle <ralf@linux-mips.org>
Cc: "Paul Burton" <paul.burton@imgtec.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
linux-mips@linux-mips.org, kvm@vger.kernel.org
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 [thread overview]
Message-ID: <57309D29.6010903@redhat.com> (raw)
In-Reply-To: <1462541784-22128-2-git-send-email-james.hogan@imgtec.com>
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
next prev parent reply other threads:[~2016-05-09 14:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 13:36 [PATCH 0/7] MIPS: Add extended ASID support James Hogan
2016-05-06 13:36 ` [PATCH 1/7] MIPS: KVM/locore.S: Don't preserve host ASID around vcpu_run James Hogan
2016-05-09 14:22 ` Paolo Bonzini [this message]
2016-05-09 15:30 ` Ralf Baechle
2016-05-09 19:42 ` James Hogan
2016-05-06 13:36 ` [PATCH 2/7] MIPS: Add & use CP0_EntryHi ASID definitions James Hogan
2016-05-06 13:36 ` [PATCH 3/7] MIPS: KVM: Abstract guest ASID mask James Hogan
2016-05-06 13:36 ` [PATCH 4/7] MIPS: KVM/locore.S: Only preserve callee saved registers James Hogan
2016-05-06 13:36 ` [PATCH 5/7] MIPS: KVM/locore.S: Relax noat James Hogan
2016-05-06 13:36 ` [PATCH 6/7] MIPS: Retrieve ASID masks using function accepting struct cpuinfo_mips James Hogan
2016-05-06 13:36 ` [PATCH 7/7] MIPS: Support extended ASIDs James Hogan
2016-05-09 13:23 ` [PATCH 0/7] MIPS: Add extended ASID support Ralf Baechle
2016-05-09 17:01 ` Maciej W. Rozycki
2016-05-09 19:04 ` James Hogan
2016-05-09 19:56 ` Maciej W. Rozycki
2016-05-09 19:59 ` James Hogan
2016-05-10 7:34 ` Ralf Baechle
2016-05-10 8:55 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57309D29.6010903@redhat.com \
--to=pbonzini@redhat.com \
--cc=james.hogan@imgtec.com \
--cc=kvm@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=rkrcmar@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox