Re: [PATCH v4 02/10] ARM: KVM: Hypervisor identity mapping

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Aug 09, 2011 at 10:20:27AM +0100, Avi Kivity wrote:
> On 08/06/2011 01:39 PM, Christoffer Dall wrote:
> > Adds support in the identity mapping feature that allows KVM to setup
> > identity mapping for the Hyp mode with the AP[1] bit set as required by
> > the specification and also supports freeing created sub pmd's after
> > finished use.
> >
> > These two functions:
> >   - hyp_identity_mapping_add(pgd, addr, end);
> >   - hyp_identity_mapping_del(pgd, addr, end);
> > are essentially calls the same function as the non-hyp versions but
> > with a different argument value. KVM calls these functions to setup
> > and teardown the identity mapping used to initialize the hypervisor.
> >
> > Note, the hyp-version of the _del function actually frees the pmd's
> > pointed to by the pgd as opposed to the non-hyp version which just
> > clears them.
> >
> >
> 
> These are for mapping host memory, not guest memory, right?

Yes. There is some code that is built into the kernel image (and address
space) but it needs to run in Hypervisor mode which has its own MMU
translation tables.

-- 
Catalin
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux