linux-kernel - Re: [PATCH v3 02/31] arm64: Kernel booting and initialisation

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]

Date:	Mon, 10 Sep 2012 07:53:39 +0200
From:	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
To:	Nicolas Pitre <nico@...xnic.net>
Cc:	Catalin Marinas <catalin.marinas@....com>,
	linux-arch@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 02/31] arm64: Kernel booting and initialisation

On 19:29 Sun 09 Sep     , Nicolas Pitre wrote:
> On Sun, 9 Sep 2012, Jean-Christophe PLAGNIOL-VILLARD wrote:
> 
> > On 17:26 Fri 07 Sep     , Catalin Marinas wrote:
> > > +4. Call the kernel image
> > > +------------------------
> > > +
> > > +Requirement: MANDATORY
> > > +
> > > +The decompressed kernel image contains a 32-byte header as follows:
> > > +
> > > +  u32 magic	= 0x14000008;	/* branch to stext, little-endian */
> > > +  u32 res0	= 0;		/* reserved */
> > > +  u64 text_offset;		/* Image load offset */
> > > +  u64 res1	= 0;		/* reserved */
> > > +  u64 res2	= 0;		/* reserved */
> > we need to have a magic to known it's a arm64 kernel
> 
> You have it: it's 0x14000008 at the beginning.
fragile
> 
> > > +
> > > +The image must be placed at the specified offset (currently 0x80000)
> > > +from the start of the system RAM and called there. The start of the
> > > +system RAM must be aligned to 2MB.
> > can we drop this
> 
> Drop what?
> And why?
This contrain the must be loadable at any address

Best Regards,
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/