From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: Backport request Date: Mon, 13 Jan 2014 10:47:51 +0000 Message-ID: <52D3C457.3010903@citrix.com> References: <52D3B6A9.2090003@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <52D3B6A9.2090003@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper Cc: Jan Beulich , Xen-devel List List-Id: xen-devel@lists.xenproject.org On 13/01/14 09:49, Andrew Cooper wrote: > Hello, > > Can you please backport c/s 0896bd8bea84526b00e00d2d076f4f953a3d73cb > "x86: map portion of kexec crash area that is within the direct map > area" to staging-4.3 ASAP, as following the backport of > 8d611a00d3389d9c16506326e24145b94ac6fb86 "kexec/x86: do not map crash > kernel area", kexec loading is broken in exactly the same way as it was > in staging. This shouldn't be necessary for 4.3 as the old kexec implementation didn't use map_domain_page() but used several fixmap slots instead. If this is broken in our XenServer 4.3 tree it's because we've backported the new kexec implementation and we'll have to do the backport of 0896bd8be ourselves. David