On 02/19/2015 06:35 PM, David Vrabel wrote:
On 18/02/2015 06:52, Juergen Gross wrote:
In case a pre-allocated memory area is to be moved in order to avoid
a conflict with the target E820 map we need a way to copy data between
physical addresses.
Add a function doing this via early_memremap().
On 02/19/2015 06:35 PM, David Vrabel wrote:
On 18/02/2015 06:52, Juergen Gross wrote:
In case a pre-allocated memory area is to be moved in order to avoid
a conflict with the target E820 map we need a way to copy data between
physical addresses.
Add a function doing this via early_memremap().
On 18/02/2015 06:52, Juergen Gross wrote:
In case a pre-allocated memory area is to be moved in order to avoid
a conflict with the target E820 map we need a way to copy data between
physical addresses.
Add a function doing this via early_memremap().
[...]
--- a/arch/x86/xen/setup.c
+++
On 18/02/2015 06:52, Juergen Gross wrote:
In case a pre-allocated memory area is to be moved in order to avoid
a conflict with the target E820 map we need a way to copy data between
physical addresses.
Add a function doing this via early_memremap().
[...]
--- a/arch/x86/xen/setup.c
+++
In case a pre-allocated memory area is to be moved in order to avoid
a conflict with the target E820 map we need a way to copy data between
physical addresses.
Add a function doing this via early_memremap().
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 29
In case a pre-allocated memory area is to be moved in order to avoid
a conflict with the target E820 map we need a way to copy data between
physical addresses.
Add a function doing this via early_memremap().
Signed-off-by: Juergen Gross jgr...@suse.com
---
arch/x86/xen/setup.c | 29
6 matches
Mail list logo