From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail.skyhub.de ([2a01:4f8:120:8448::d00d]) by merlin.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1VnQ3u-00086f-N5 for kexec@lists.infradead.org; Mon, 02 Dec 2013 09:45:07 +0000 Date: Mon, 2 Dec 2013 10:44:41 +0100 From: Borislav Petkov Subject: Re: [PATCH v4 07/12] efi: passing kexec necessary efi data via setup_data Message-ID: <20131202094441.GB7380@pd.tnic> References: <1385445477-9665-1-git-send-email-dyoung@redhat.com> <1385445477-9665-8-git-send-email-dyoung@redhat.com> <20131127140732.GD32267@pd.tnic> <20131129091415.GH4186@dhcp-16-126.nay.redhat.com> <20131129164632.GD4266@pd.tnic> <20131202024914.GD3999@dhcp-16-126.nay.redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20131202024914.GD3999@dhcp-16-126.nay.redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org To: Dave Young Cc: mjg59@srcf.ucam.org, linux-efi@vger.kernel.org, toshi.kani@hp.com, matt@console-pimps.org, greg@kroah.com, x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, James.Bottomley@HansenPartnership.com, horms@verge.net.au, ebiederm@xmission.com, hpa@zytor.com, vgoyal@redhat.com On Mon, Dec 02, 2013 at 10:49:15AM +0800, Dave Young wrote: > All these setup_data passing, remapping etc. is mostly for kexec, > add a lot of contiditional #if #endif makes the code a mess. I would > prefer to not do this if you are not strongly object. Right, having efi_kexec.c could solve all that, see my other mail. > I'm confused how to connect this with DMI.. This HP platform - like any other platform out there - has specific DMI strings identifying it. Look for examples calling dmi_check_system(). > Ok, so I will leave this to you after this series settle down. Ok, /me puts it on the TODO list :) Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH v4 07/12] efi: passing kexec necessary efi data via setup_data Date: Mon, 2 Dec 2013 10:44:41 +0100 Message-ID: <20131202094441.GB7380@pd.tnic> References: <1385445477-9665-1-git-send-email-dyoung@redhat.com> <1385445477-9665-8-git-send-email-dyoung@redhat.com> <20131127140732.GD32267@pd.tnic> <20131129091415.GH4186@dhcp-16-126.nay.redhat.com> <20131129164632.GD4266@pd.tnic> <20131202024914.GD3999@dhcp-16-126.nay.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <20131202024914.GD3999-je1gSBvt1TcFLmT5oZ11vB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org> Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Dave Young Cc: toshi.kani-VXdhtT5mjnY@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org, hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org, James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org, vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org, horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org, kexec-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, greg-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org, matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org List-Id: linux-efi@vger.kernel.org On Mon, Dec 02, 2013 at 10:49:15AM +0800, Dave Young wrote: > All these setup_data passing, remapping etc. is mostly for kexec, > add a lot of contiditional #if #endif makes the code a mess. I would > prefer to not do this if you are not strongly object. Right, having efi_kexec.c could solve all that, see my other mail. > I'm confused how to connect this with DMI.. This HP platform - like any other platform out there - has specific DMI strings identifying it. Look for examples calling dmi_check_system(). > Ok, so I will leave this to you after this series settle down. Ok, /me puts it on the TODO list :) Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. -- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753208Ab3LBJor (ORCPT ); Mon, 2 Dec 2013 04:44:47 -0500 Received: from mail.skyhub.de ([78.46.96.112]:38237 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752562Ab3LBJoq (ORCPT ); Mon, 2 Dec 2013 04:44:46 -0500 Date: Mon, 2 Dec 2013 10:44:41 +0100 From: Borislav Petkov To: Dave Young Cc: toshi.kani@hp.com, linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org, x86@kernel.org, mjg59@srcf.ucam.org, hpa@zytor.com, James.Bottomley@HansenPartnership.com, vgoyal@redhat.com, ebiederm@xmission.com, horms@verge.net.au, kexec@lists.infradead.org, greg@kroah.com, matt@console-pimps.org Subject: Re: [PATCH v4 07/12] efi: passing kexec necessary efi data via setup_data Message-ID: <20131202094441.GB7380@pd.tnic> References: <1385445477-9665-1-git-send-email-dyoung@redhat.com> <1385445477-9665-8-git-send-email-dyoung@redhat.com> <20131127140732.GD32267@pd.tnic> <20131129091415.GH4186@dhcp-16-126.nay.redhat.com> <20131129164632.GD4266@pd.tnic> <20131202024914.GD3999@dhcp-16-126.nay.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20131202024914.GD3999@dhcp-16-126.nay.redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 02, 2013 at 10:49:15AM +0800, Dave Young wrote: > All these setup_data passing, remapping etc. is mostly for kexec, > add a lot of contiditional #if #endif makes the code a mess. I would > prefer to not do this if you are not strongly object. Right, having efi_kexec.c could solve all that, see my other mail. > I'm confused how to connect this with DMI.. This HP platform - like any other platform out there - has specific DMI strings identifying it. Look for examples calling dmi_check_system(). > Ok, so I will leave this to you after this series settle down. Ok, /me puts it on the TODO list :) Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --