| To: | Adil Hafeez <adilhafeez80@gmail.com> |
|---|---|
| Subject: | Re: Fixed kernel entry point suggestion |
| From: | Thiemo Seufer <ths@networkno.de> |
| Date: | Fri, 30 Dec 2005 22:04:27 +0100 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <82e4189c0512300222k426764e0ldefeafb232ad36d@mail.gmail.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <82e4189c0512272336xed0fe2ax9fee6119ea2d6b00@mail.gmail.com> <06af7c9f9f82dd2b306e02997869e709@embeddedalley.com> <82e4189c0512300136w5112edf2kf3d243ddbc9313d@mail.gmail.com> <20051230094750.GI1882@hattusa.textio> <82e4189c0512300222k426764e0ldefeafb232ad36d@mail.gmail.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.11 |
Adil Hafeez wrote: > What about placing the jump instruction just after reserved space, like this > > .text > /* > * Reserved space for exception handlers. > * Necessary for machines which link their kernels at KSEG0. > */ > .fill 0x400 > > /* The following two symbols are used for kernel profiling. */ > EXPORT(stext) > EXPORT(_stext) > => j kernel_entry > __INIT > > I disassembled vmlinux binary and now jump instruction is placed after > reserved space This only works iff the fill is done with NOPs. On a more general note, it is usually considered to be the bootloader's job to find the correct entry, not the kernel's one. Thiemo |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] AMD Au1xx0 serial: claim the memory resource, Sergei Shtylylov |
|---|---|
| Next by Date: | [PATCH] Au1xx0: replace casual readl() with au_readl() in the drivers, Sergei Shtylylov |
| Previous by Thread: | Re: Fixed kernel entry point suggestion, Adil Hafeez |
| Next by Thread: | Re: [PATCH] Retain the write-only OD from being clobbered, Sergei Shtylylov |
| Indexes: | [Date] [Thread] [Top] [All Lists] |