From: Vladimir Murzin <vladimir.murzin@arm.com> To: gengdongjiu <gengdongjiu@huawei.com>, Marc Zyngier <marc.zyngier@arm.com>, "christoffer.dall@linaro.org" <christoffer.dall@linaro.org>, "pbonzini@redhat.com" <pbonzini@redhat.com>, "rkrcmar@redhat.com" <rkrcmar@redhat.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "suzuki.poulose@arm.com" <suzuki.poulose@arm.com>, mark.rutland@arm.com, catalin.marinas@arm.com Cc: James Morse <James.Morse@arm.com>, zhanghaibin7@huawei.com, Huangshaoyu <huangshaoyu@huawei.com> Subject: Re: [PATCH] arm64: KVM: VHE: save and restore some PSTATE bits Date: Wed, 6 Sep 2017 13:30:43 +0100 [thread overview] Message-ID: <b7d8388d-d9df-9cc4-3d07-82e7f807017a@arm.com> (raw) In-Reply-To: <57ba125f-9c3c-3504-35a6-9800a47450cf@huawei.com> On 06/09/17 13:14, gengdongjiu wrote: > > > On 2017/9/6 20:00, Vladimir Murzin wrote: >> On 06/09/17 11:35, gengdongjiu wrote: >>> Vladimir, >>> >>> On 2017/9/6 17:41, Vladimir Murzin wrote: >>>> Can you please elaborate on cases where PAN is not enabled? >>> >>> I mean the informal private usage, For example, he disabled the PAN dynamically to let kernel space to access the user space. >>> After he dynamic disabled the PAN, then switched to guest OS. after return to host. he found the PAN stage is modified. >>> Of cause this is not a formal usage, in our host kernel, it is always enabled, no dynamic change, but I means it may exist such cases. >>> >>> >> >> So, in short, there is no real issue with PAN, right? What about UAO? > For the PAN, if host OS dynamically enable/disable PAN should have issue. > Do you think that is not a issue as above description? > > "host OS dynamically disable the PAN, but after go back from the guest OS, The PAN is unexpectedly enabled" Do you see effect of "PAN is unexpectedly enabled"? Cheers Vladimir > >> >> Cheers >> Vladimir >> >> . >> > >
WARNING: multiple messages have this Message-ID (diff)
From: vladimir.murzin@arm.com (Vladimir Murzin) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH] arm64: KVM: VHE: save and restore some PSTATE bits Date: Wed, 6 Sep 2017 13:30:43 +0100 [thread overview] Message-ID: <b7d8388d-d9df-9cc4-3d07-82e7f807017a@arm.com> (raw) In-Reply-To: <57ba125f-9c3c-3504-35a6-9800a47450cf@huawei.com> On 06/09/17 13:14, gengdongjiu wrote: > > > On 2017/9/6 20:00, Vladimir Murzin wrote: >> On 06/09/17 11:35, gengdongjiu wrote: >>> Vladimir, >>> >>> On 2017/9/6 17:41, Vladimir Murzin wrote: >>>> Can you please elaborate on cases where PAN is not enabled? >>> >>> I mean the informal private usage, For example, he disabled the PAN dynamically to let kernel space to access the user space. >>> After he dynamic disabled the PAN, then switched to guest OS. after return to host. he found the PAN stage is modified. >>> Of cause this is not a formal usage, in our host kernel, it is always enabled, no dynamic change, but I means it may exist such cases. >>> >>> >> >> So, in short, there is no real issue with PAN, right? What about UAO? > For the PAN, if host OS dynamically enable/disable PAN should have issue. > Do you think that is not a issue as above description? > > "host OS dynamically disable the PAN, but after go back from the guest OS, The PAN is unexpectedly enabled" Do you see effect of "PAN is unexpectedly enabled"? Cheers Vladimir > >> >> Cheers >> Vladimir >> >> . >> > >
next prev parent reply other threads:[~2017-09-06 12:30 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-05 18:58 [PATCH] arm64: KVM: VHE: save and restore some PSTATE bits gengdongjiu 2017-09-05 18:58 ` gengdongjiu 2017-09-05 18:58 ` gengdongjiu 2017-09-06 5:26 ` gengdongjiu 2017-09-06 5:26 ` gengdongjiu 2017-09-06 5:26 ` gengdongjiu 2017-09-06 5:26 ` gengdongjiu 2017-09-06 8:17 ` Marc Zyngier 2017-09-06 8:17 ` Marc Zyngier 2017-09-06 8:17 ` Marc Zyngier 2017-09-06 9:32 ` gengdongjiu 2017-09-06 9:32 ` gengdongjiu 2017-09-06 9:32 ` gengdongjiu 2017-09-06 9:32 ` gengdongjiu 2017-09-06 9:41 ` Vladimir Murzin 2017-09-06 9:41 ` Vladimir Murzin 2017-09-06 9:41 ` Vladimir Murzin 2017-09-06 10:35 ` gengdongjiu 2017-09-06 10:35 ` gengdongjiu 2017-09-06 10:35 ` gengdongjiu 2017-09-06 10:35 ` gengdongjiu 2017-09-06 12:00 ` Vladimir Murzin 2017-09-06 12:00 ` Vladimir Murzin 2017-09-06 12:00 ` Vladimir Murzin 2017-09-06 12:14 ` gengdongjiu 2017-09-06 12:14 ` gengdongjiu 2017-09-06 12:14 ` gengdongjiu 2017-09-06 12:14 ` gengdongjiu 2017-09-06 12:30 ` Vladimir Murzin [this message] 2017-09-06 12:30 ` Vladimir Murzin 2017-09-06 12:30 ` Vladimir Murzin 2017-09-06 12:44 ` gengdongjiu 2017-09-06 12:44 ` gengdongjiu 2017-09-06 12:44 ` gengdongjiu 2017-09-06 12:44 ` gengdongjiu 2017-09-06 13:00 ` Vladimir Murzin 2017-09-06 13:00 ` Vladimir Murzin 2017-09-06 13:00 ` Vladimir Murzin 2017-09-06 12:32 ` gengdongjiu 2017-09-06 12:32 ` gengdongjiu 2017-09-06 12:32 ` gengdongjiu 2017-09-06 12:32 ` gengdongjiu 2017-09-06 9:49 ` gengdongjiu 2017-09-06 9:49 ` gengdongjiu 2017-09-06 9:49 ` gengdongjiu 2017-09-06 9:49 ` gengdongjiu 2017-09-06 20:49 ` kbuild test robot 2017-09-06 20:49 ` kbuild test robot 2017-09-06 20:49 ` kbuild test robot 2017-09-06 14:10 gengdongjiu 2017-09-06 14:10 ` gengdongjiu 2017-09-06 14:10 ` gengdongjiu 2017-09-06 14:40 ` Vladimir Murzin 2017-09-06 14:40 ` Vladimir Murzin 2017-09-06 14:40 ` Vladimir Murzin 2017-09-06 14:40 ` Vladimir Murzin 2017-09-06 15:08 ` gengdongjiu 2017-09-06 15:08 ` gengdongjiu 2017-09-06 15:19 ` Vladimir Murzin 2017-09-06 15:19 ` Vladimir Murzin 2017-09-06 22:09 gengdongjiu 2017-09-06 22:09 ` gengdongjiu
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=b7d8388d-d9df-9cc4-3d07-82e7f807017a@arm.com \ --to=vladimir.murzin@arm.com \ --cc=James.Morse@arm.com \ --cc=catalin.marinas@arm.com \ --cc=christoffer.dall@linaro.org \ --cc=gengdongjiu@huawei.com \ --cc=huangshaoyu@huawei.com \ --cc=kvm@vger.kernel.org \ --cc=kvmarm@lists.cs.columbia.edu \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=marc.zyngier@arm.com \ --cc=mark.rutland@arm.com \ --cc=pbonzini@redhat.com \ --cc=rkrcmar@redhat.com \ --cc=suzuki.poulose@arm.com \ --cc=zhanghaibin7@huawei.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.