On Wed, Sep 27, 2017 at 10:13:33AM +0100, Will Deacon wrote:
> On Wed, Sep 27, 2017 at 09:31:41AM +0100, Marc Zyngier wrote:
> > On Tue, Sep 26 2017 at 9:45:42 pm BST, Yury Norov
> > wrote:
> > > On Wed, Sep 13, 2017 at 09:08:30PM +0300, Yury Norov wrote:
> > >> The Documentation/arm64/memory.tx
On Wed, Sep 27 2017 at 10:13:33 am BST, Will Deacon wrote:
> On Wed, Sep 27, 2017 at 09:31:41AM +0100, Marc Zyngier wrote:
>> On Tue, Sep 26 2017 at 9:45:42 pm BST, Yury Norov
>> wrote:
>> > On Wed, Sep 13, 2017 at 09:08:30PM +0300, Yury Norov wrote:
>> >> The Documentation/arm64/memory.txt say
On Wed, Sep 27, 2017 at 09:31:41AM +0100, Marc Zyngier wrote:
> On Tue, Sep 26 2017 at 9:45:42 pm BST, Yury Norov
> wrote:
> > On Wed, Sep 13, 2017 at 09:08:30PM +0300, Yury Norov wrote:
> >> The Documentation/arm64/memory.txt says:
> >> When using KVM, the hypervisor maps kernel pages in EL2, a
On Tue, Sep 26 2017 at 9:45:42 pm BST, Yury Norov
wrote:
> Ping?
>
> On Wed, Sep 13, 2017 at 09:08:30PM +0300, Yury Norov wrote:
>> The Documentation/arm64/memory.txt says:
>> When using KVM, the hypervisor maps kernel pages in EL2, at a fixed
>> offset from the kernel VA (top 24bits of the kern
Ping?
On Wed, Sep 13, 2017 at 09:08:30PM +0300, Yury Norov wrote:
> The Documentation/arm64/memory.txt says:
> When using KVM, the hypervisor maps kernel pages in EL2, at a fixed
> offset from the kernel VA (top 24bits of the kernel VA set to zero):
>
> In fact, kernel addresses are transleted to
The Documentation/arm64/memory.txt says:
When using KVM, the hypervisor maps kernel pages in EL2, at a fixed
offset from the kernel VA (top 24bits of the kernel VA set to zero):
In fact, kernel addresses are transleted to HYP with kern_hyp_va macro,
which has more options, and none of them assumes
