[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <5400ADD6020000780002F159@mail.emea.novell.com>
Date: Fri, 29 Aug 2014 15:44:06 +0100
From: "Jan Beulich" <JBeulich@...e.com>
To: "Stefan Bader" <stefan.bader@...onical.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@...cle.com>
Cc: "Kees Cook" <keescook@...omium.org>,
"David Vrabel" <david.vrabel@...rix.com>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [Xen-devel] [PATCH] Solved the Xen PV/KASLR riddle
>>> On 29.08.14 at 16:27, <stefan.bader@...onical.com> wrote:
> Sure. Btw, someone also contacted me saying they have the same problem
> without
> changing the layout but having really big initrd (500M). While that feels
> like
> it should be impossible (if the kernel+initrd+xen stuff has to fix the 512M
> kernel image size area then). But if it can happen, then surely it does
> cause
> mappings to be where the module space starts then.
Since the initrd doesn't really need to be mapped into the (limited)
virtual address space a pv guest starts with, we specifically got
/*
* Whether or not the guest can deal with being passed an initrd not
* mapped through its initial page tables.
*/
#define XEN_ELFNOTE_MOD_START_PFN 16
to deal with that situation. The hypervisor side for Dom0 is in place,
and the kernel side works in our (classic) kernels. Whether it got
implemented for DomU meanwhile I don't know; I'm pretty certain
pv-ops kernels don't support it so far.
Jan
--
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