lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <483DCD97.20103@goop.org>
Date:	Wed, 28 May 2008 22:24:39 +0100
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Yinghai Lu <yhlu.kernel@...il.com>
CC:	Rusty Russell <rusty@...tcorp.com.au>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: extend e820 ealy_res support 32bit - fix #2

Yinghai Lu wrote:
>> ===================================================================
>> --- a/arch/x86/xen/enlighten.c
>> +++ b/arch/x86/xen/enlighten.c
>> @@ -1266,6 +1266,15 @@
>>                add_preferred_console("hvc", 0, NULL);
>>        }
>>
>> +       /*
>> +        * Reserve Xen bits:
>> +        *  - mfn_list
>> +        *  - xen_start_info
>> +        * See comment above "struct start_info" in <xen/interface/xen.h>
>> +        */
>> +       reserve_early(__pa(xen_start_info->mfn_list),
>> +                     __pa(xen_start_info->pt_base), "XEN");
>> +
>>     
>
> can we use e820 entries for that? So the domain builder could have
> several entries for E820_RAM and E820_RESERVED...
>   

Yeah, seems reasonable.  I'll try it out.

> will need x86_64_start_kernel there, maybe we should change all name
> to x86_start_kernel

We can do that later.  For now it's better to give them distinct names.

    J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ