On 10/27/17 10:40 +0200, Ingo Molnar wrote:
>
> * Haozhong Zhang wrote:
>
> > By default, KVM treats a reserved page as for MMIO purpose, and maps
> > it to guest with UC memory type. However, some reserved pages are not
> > for MMIO, such as pages of DAX device
On 10/27/17 10:40 +0200, Ingo Molnar wrote:
>
> * Haozhong Zhang wrote:
>
> > By default, KVM treats a reserved page as for MMIO purpose, and maps
> > it to guest with UC memory type. However, some reserved pages are not
> > for MMIO, such as pages of DAX device (e.g., /dev/daxX.Y). Mapping
>
* Haozhong Zhang wrote:
> By default, KVM treats a reserved page as for MMIO purpose, and maps
> it to guest with UC memory type. However, some reserved pages are not
> for MMIO, such as pages of DAX device (e.g., /dev/daxX.Y). Mapping
> them with UC memory type will
* Haozhong Zhang wrote:
> By default, KVM treats a reserved page as for MMIO purpose, and maps
> it to guest with UC memory type. However, some reserved pages are not
> for MMIO, such as pages of DAX device (e.g., /dev/daxX.Y). Mapping
> them with UC memory type will harm the performance. In
By default, KVM treats a reserved page as for MMIO purpose, and maps
it to guest with UC memory type. However, some reserved pages are not
for MMIO, such as pages of DAX device (e.g., /dev/daxX.Y). Mapping
them with UC memory type will harm the performance. In order to
exclude those cases, we
By default, KVM treats a reserved page as for MMIO purpose, and maps
it to guest with UC memory type. However, some reserved pages are not
for MMIO, such as pages of DAX device (e.g., /dev/daxX.Y). Mapping
them with UC memory type will harm the performance. In order to
exclude those cases, we
6 matches
Mail list logo