From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan Lynch Subject: Re: [PATCH] c/r: Fix arch-specific use of mm->context.vdso in v14-rc3 Date: Wed, 8 Apr 2009 13:41:21 -0500 Message-ID: <20090408134121.0f75a232@manatee.lan> References: <1239127585-15930-1-git-send-email-danms@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1239127585-15930-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Dan Smith Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org List-Id: containers.vger.kernel.org Dan Smith wrote: > On s390 and PPC, the mm_context does not have a void *vdso member, but > rather an unsigned long vdso_base. Since we cast the void * to an > unsigned long anyway, add an arch-specific cr_arch_vdso() function to > return the address. Looks technically correct for powerpc at least, thanks.