> I'm not certain I caught everything but as far as I know I did. > Part of that was by having the code run at a fixed virtual address so > we still live in the last 2GB of the virtual address space. You changed the -2GB (or rather -40MB unpatched) mapping to not necessarily be linear? There are a couple of assumptions that it is, including at boot up (it doubles as the 1:1 mapping then) and in change_page_attr() and in suspend/resume. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- From: [email protected] (Eric W. Biederman)
- Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- References:
- [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- From: Magnus Damm <[email protected]>
- Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- From: Andi Kleen <[email protected]>
- Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- From: Vivek Goyal <[email protected]>
- Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- From: Andi Kleen <[email protected]>
- Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- From: [email protected] (Eric W. Biederman)
- [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- Prev by Date: Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- Next by Date: Re: [Fwd: ndiswrapper]
- Previous by thread: Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- Next by thread: Re: [Fastboot] [PATCH][RFC] x86_64: Reload CS when startup_64 is used.
- Index(es):
 |