[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50D09733.3080502@zytor.com>
Date: Tue, 18 Dec 2012 08:17:55 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: stefani@...bold.net
CC: linux-kernel@...r.kernel.org, x86@...nel.org, tglx@...utronix.de,
mingo@...hat.com, ak@...ux.intel.com, aarcange@...hat.com,
john.stultz@...aro.org, luto@...capital.net, xemul@...allels.com,
gorcunov@...nvz.org, andriy.shevchenko@...ux.intel.com
Subject: Re: [PATCH 6/6] Add 32 bit VDSO support for 32 and 64 bit kernels
On 12/18/2012 01:40 AM, stefani@...bold.net wrote:
> From: Stefani Seibold <stefani@...bold.net>
>
> This patch adds support for 32 bit VDSO.
>
> For 32 bit programs running on a 32 bit kernel, the same mechanism is
> used as for 64 bit programs running on a 64 bit kernel.
>
> For 32 bit programs running under a 64 bit IA32_EMULATION, it is a
> little bit more tricky. In this case the VVAR and HPET will be mapped
> into the 32 bit address space, by cutting of the upper 32 bit. So the
> address for this will not changed in the view of the 32 bit VDSO. The
> HPET will be mapped in this case at 0xff5fe000 and the VVAR at 0xff5ff000.
>
> The transformation between the in 64 bit kernel representation and the 32 bit
> abi will be also provided.
>
> So we have one VDSO Source for all.
>
You seem to once again have disregarded the request to make the vvar and
hpet part of the vdso address space proper. If this is not possible or
highly impractical, please extend a technical motivation why that is so,
rather than simply ignoring it.
-hpa
--
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