Re: [PATCH 11/26] KVM: PPC: Make RMO a define

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

 




Am 26.06.2010 um 18:52 schrieb Segher Boessenkool <segher@xxxxxxxxxxxxxxxxxxx >:

On PowerPC it's very normal to not support all of the physical RAM in real mode.

Oh? Are you referring to "real mode limit", or 32-bit implementations with
more than 32 address lines, or something else?

The former.


Either way, RMO is a really bad name for this, since that name is already
used for a similar but different concept.

It's the same concept, no? Not all physical memory is accessible from real mode.


Also, it seems you construct the physical address by masking out bits from the effective address. Most implementations will trap or machine check if
you address outside of physical address space, instead.

Well the only case where I remember to have hit a real RMO case is on the PS3 - that issues a data/instruction storage interrupt when accessing anything > 8MB in real mode.

So I'd argue this is heavily implementation specific.

Apart from that what I'm trying to cover is that on ppc64 accessing 0xc0000000000000 in real mode gets you 0x0. Is there a better name for this?

Alex


--
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