linux-kernel - Re: Extending boot protocol & bzImage for paravirt

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 01 Jun 2007 17:37:51 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	"H. Peter Anvin" <hpa@...or.com>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Chris Wright <chrisw@...s-sol.org>,
	Virtualization Mailing List <virtualization@...ts.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Extending boot protocol & bzImage for paravirt_ops

H. Peter Anvin wrote:
> Well, if we define is as a movable object then it has to be treated as
> such.  It's a protocol definition issue.  If we define it opaque, though
> -- of for that matter, if we don't -- we should define what memory it
> can live in, though.  Right now, the only "available" memory we have is
> end of setup to 0xa0000; the command line is defined to be allocated
> from this memory.
>   

Well, I think we can safely say that its something that's only
meaningful in 32/64-bit mode, so we aren't constrained by the real-mode
address space.

One of my goals in this project is to make the boot image, in some way,
completely define which memory it needs it get started.  That means that
the boot loader can either place things knowing they'll avoid the boot
image and/or definitively know that the image is unloadable.

So I don't think its strictly necessary to pre-define what memory this
object can use, since I think it can be safely determined dynamically.

    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/