On 2015/5/15 16:54, Jan Beulich wrote:
On 15.05.15 at 10:47, wrote:
On 2015/5/15 16:12, Jan Beulich wrote:
On 15.05.15 at 10:00, wrote:
On 2015/5/15 15:34, Jan Beulich wrote:
On 15.05.15 at 09:11, wrote:
On 2015/5/15 14:56, Jan Beulich wrote:
On 15.05.15 at 08:39, wrote:
On 2015/5/15 1
>>> On 15.05.15 at 10:47, wrote:
> On 2015/5/15 16:12, Jan Beulich wrote:
> On 15.05.15 at 10:00, wrote:
>>> On 2015/5/15 15:34, Jan Beulich wrote:
>>> On 15.05.15 at 09:11, wrote:
> On 2015/5/15 14:56, Jan Beulich wrote:
> On 15.05.15 at 08:39, wrote:
>>> On 2015/5/15 1
On 2015/5/15 16:12, Jan Beulich wrote:
On 15.05.15 at 10:00, wrote:
On 2015/5/15 15:34, Jan Beulich wrote:
On 15.05.15 at 09:11, wrote:
On 2015/5/15 14:56, Jan Beulich wrote:
On 15.05.15 at 08:39, wrote:
On 2015/5/15 14:25, Jan Beulich wrote:
On 15.05.15 at 08:11, wrote:
Even we may se
>>> On 15.05.15 at 10:00, wrote:
> On 2015/5/15 15:34, Jan Beulich wrote:
> On 15.05.15 at 09:11, wrote:
>>> On 2015/5/15 14:56, Jan Beulich wrote:
>>> On 15.05.15 at 08:39, wrote:
> On 2015/5/15 14:25, Jan Beulich wrote:
> On 15.05.15 at 08:11, wrote:
>>> Even we may se
On 2015/5/15 15:34, Jan Beulich wrote:
On 15.05.15 at 09:11, wrote:
On 2015/5/15 14:56, Jan Beulich wrote:
On 15.05.15 at 08:39, wrote:
On 2015/5/15 14:25, Jan Beulich wrote:
On 15.05.15 at 08:11, wrote:
Even we may separate the
low memory to construct memory_map.map[]...
???
Sorry I
>>> On 15.05.15 at 09:11, wrote:
> On 2015/5/15 14:56, Jan Beulich wrote:
> On 15.05.15 at 08:39, wrote:
>>> On 2015/5/15 14:25, Jan Beulich wrote:
>>> On 15.05.15 at 08:11, wrote:
> Even we may separate the
> low memory to construct memory_map.map[]...
???
>>>
>>> Sorr
On 2015/5/15 14:56, Jan Beulich wrote:
On 15.05.15 at 08:39, wrote:
On 2015/5/15 14:25, Jan Beulich wrote:
On 15.05.15 at 08:11, wrote:
Even we may separate the
low memory to construct memory_map.map[]...
???
Sorry I just mean that the low memory is not represented with only one
memory_m
>>> On 15.05.15 at 08:39, wrote:
> On 2015/5/15 14:25, Jan Beulich wrote:
> On 15.05.15 at 08:11, wrote:
>>> Even we may separate the
>>> low memory to construct memory_map.map[]...
>>
>> ???
>
> Sorry I just mean that the low memory is not represented with only one
> memory_map.map[] in so
On 2015/5/15 14:25, Jan Beulich wrote:
On 15.05.15 at 08:11, wrote:
On 2015/4/20 22:29, Jan Beulich wrote:
On 10.04.15 at 11:22, wrote:
@@ -119,10 +120,6 @@ int build_e820_table(struct e820entry *e820,
/* Low RAM goes here. Reserve space for special pages. */
BUG_ON((hvm_info-
>>> On 15.05.15 at 08:11, wrote:
> On 2015/4/20 22:29, Jan Beulich wrote:
> On 10.04.15 at 11:22, wrote:
>>> @@ -119,10 +120,6 @@ int build_e820_table(struct e820entry *e820,
>>>
>>> /* Low RAM goes here. Reserve space for special pages. */
>>> BUG_ON((hvm_info->low_mem_pgend << P
On 2015/4/20 22:29, Jan Beulich wrote:
On 10.04.15 at 11:22, wrote:
--- a/tools/firmware/hvmloader/e820.c
+++ b/tools/firmware/hvmloader/e820.c
@@ -73,7 +73,8 @@ int build_e820_table(struct e820entry *e820,
unsigned int lowmem_reserved_base,
unsigne
>>> On 10.04.15 at 11:22, wrote:
> --- a/tools/firmware/hvmloader/e820.c
> +++ b/tools/firmware/hvmloader/e820.c
> @@ -73,7 +73,8 @@ int build_e820_table(struct e820entry *e820,
> unsigned int lowmem_reserved_base,
> unsigned int bios_image_base)
> {
>
12 matches
Mail list logo
