Hi,
again i want ask if there is a change to bring the patch back to tip
and/or linux next?
I also need a review of [Patch v22 10/12] x86: Add 32 bit VDSO time
support for 64 bit kernel.
Some more tests and acked-by would be also fine :-)
Till the 32 bit VDSO time functions are not in the vanil
Am Montag, den 03.03.2014, 23:20 -0800 schrieb H. Peter Anvin:
> Pretty much... contact the glibc maintainers. However, with glibc being a
> GNU project you will have to sign a copyright transfer.
>
> On March 3, 2014 11:02:08 PM PST, Stefani Seibold wrote:
> >Hi,
> >
> >i want ask if there is
Pretty much... contact the glibc maintainers. However, with glibc being a GNU
project you will have to sign a copyright transfer.
On March 3, 2014 11:02:08 PM PST, Stefani Seibold wrote:
>Hi,
>
>i want ask if there is a change to bring the patch back to tip?
>
>As requested the glibc patch is
Hi,
i want ask if there is a change to bring the patch back to tip?
As requested the glibc patch is now available at
http://seibold.net/glibc.patch
Any idea how to bring this patch into glibc? Is the process similar to
the kernel?
- Stefani
--
To unsubscribe from this list: send the line "un
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fast and a reliable way, be
On 03/02/2014 08:32 AM, Andy Lutomirski wrote:
>
> OTOH, hpa may prefer incremental patches, now that this lives in tip.
>
The branch currently in -tip is dead, so it is not an issue either way.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bod
On Sun, Mar 2, 2014 at 2:47 AM, Ingo Molnar wrote:
>
> * Stefani Seibold wrote:
>
>> This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
>> and vdso_time() to the 32 bit VDSO.
>
> What I'm missing from all the series is any trace of the significant
> review and debug work that
* Stefani Seibold wrote:
> This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
> and vdso_time() to the 32 bit VDSO.
What I'm missing from all the series is any trace of the significant
review and debug work that Andy Lutomirski did for the series. Please
add Acked-by or Re
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fast and a reliable way, be
Am Samstag, den 01.03.2014, 14:56 -0800 schrieb H. Peter Anvin:
> On 02/28/2014 06:00 PM, Andy Lutomirski wrote:
> >
> > This leads to a potentially interesting question: is rdtsc_barrier()
> > actually necessary on UP? IIRC the point is that, if an
> > rdtsc_barrier(); rdtsc in one thread is "be
On 02/28/2014 06:00 PM, Andy Lutomirski wrote:
>
> This leads to a potentially interesting question: is rdtsc_barrier()
> actually necessary on UP? IIRC the point is that, if an
> rdtsc_barrier(); rdtsc in one thread is "before" (in the sense of
> being synchronized by some memory operation) an r
On Thu, Feb 27, 2014 at 11:22 PM, Stefani Seibold wrote:
> Am Mittwoch, den 26.02.2014, 16:55 -0800 schrieb Andy Lutomirski:
>>
>> Once I patch it to work, your 32-bit code is considerably faster than
>> the 64-bit case. It's enough faster that I suspect a bug. Dumping
>> the in-memory shows som
Am Mittwoch, den 26.02.2014, 16:55 -0800 schrieb Andy Lutomirski:
> Um. This code doesn't work. I'll send a patch. I can't speak
> towards how well it compiles in different configurations.
>
> I can't speak towards how well it compiles in different
> configurations. Also, vdso_fallback_gettime
* Andy Lutomirski wrote:
> On Wed, Feb 26, 2014 at 12:45 PM, Greg KH wrote:
> > On Wed, Feb 26, 2014 at 08:34:58PM +0100, Stefani Seibold wrote:
> >> Hi,
> >>
> >> i still wait for ACK's for the 32 bit VDSO time function support. Whats
> >> the next step? Is there a way to apply it to the linu
On 02/26/2014 12:54 PM, Andy Lutomirski wrote:
> On Wed, Feb 26, 2014 at 12:45 PM, Greg KH wrote:
>> On Wed, Feb 26, 2014 at 08:34:58PM +0100, Stefani Seibold wrote:
>>> Hi,
>>>
>>> i still wait for ACK's for the 32 bit VDSO time function support. Whats
>>> the next step? Is there a way to apply
Um. This code doesn't work. I'll send a patch. I can't speak
towards how well it compiles in different configurations.
I can't speak towards how well it compiles in different
configurations. Also, vdso_fallback_gettime needs .cfi annotations, I
think. I could probably dredge the required inca
On Wed, Feb 26, 2014 at 12:45 PM, Greg KH wrote:
> On Wed, Feb 26, 2014 at 08:34:58PM +0100, Stefani Seibold wrote:
>> Hi,
>>
>> i still wait for ACK's for the 32 bit VDSO time function support. Whats
>> the next step? Is there a way to apply it to the linux-git or linux-next
>> in near future?
>
On Wed, Feb 26, 2014 at 08:34:58PM +0100, Stefani Seibold wrote:
> Hi,
>
> i still wait for ACK's for the 32 bit VDSO time function support. Whats
> the next step? Is there a way to apply it to the linux-git or linux-next
> in near future?
I thought this was already in the tip tree. Didn't the
I'm planning on testing this, hopefully today.
--Andy
On Wed, Feb 26, 2014 at 11:34 AM, Stefani Seibold wrote:
> Hi,
>
> i still wait for ACK's for the 32 bit VDSO time function support. Whats
> the next step? Is there a way to apply it to the linux-git or linux-next
> in near future?
>
> - Ste
Hi,
i still wait for ACK's for the 32 bit VDSO time function support. Whats
the next step? Is there a way to apply it to the linux-git or linux-next
in near future?
- Stefani
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.k
Am Donnerstag, den 20.02.2014, 15:10 -0800 schrieb H. Peter Anvin:
> On 02/19/2014 01:09 AM, Stefani Seibold wrote:
> >
> > This kind of helper must be integrated into glibc, for x86 64 bit and
> > PowerPC it is already there.
> >
>
> Who is doing the glibc work?
>
I don't know. I hoped this w
On 02/19/2014 01:09 AM, Stefani Seibold wrote:
>
> This kind of helper must be integrated into glibc, for x86 64 bit and
> PowerPC it is already there.
>
Who is doing the glibc work?
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messa
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fast and a reliable way, be
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fast and a reliable way, be
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fast and a reliable way, be
On Sun, Feb 16, 2014 at 09:29:35AM +0100, Stefani Seibold wrote:
> Am Samstag, den 15.02.2014, 20:14 -0800 schrieb H. Peter Anvin:
> > On 02/15/2014 08:32 AM, Stefani Seibold wrote:
> > > This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
> > > and vdso_time() to the 32 bit VDSO
Am Samstag, den 15.02.2014, 20:14 -0800 schrieb H. Peter Anvin:
> On 02/15/2014 08:32 AM, Stefani Seibold wrote:
> > This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
> > and vdso_time() to the 32 bit VDSO.
>
> x86-64 allyesconfig:
>
> AS arch/x86/vdso/vdso32/int80.o
>
Am Samstag, den 15.02.2014, 20:14 -0800 schrieb H. Peter Anvin:
> On 02/15/2014 08:32 AM, Stefani Seibold wrote:
> > This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
> > and vdso_time() to the 32 bit VDSO.
>
> x86-64 allyesconfig:
>
> AS arch/x86/vdso/vdso32/int80.o
>
On 02/15/2014 08:32 AM, Stefani Seibold wrote:
> This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
> and vdso_time() to the 32 bit VDSO.
x86-64 allyesconfig:
AS arch/x86/vdso/vdso32/int80.o
/home/hpa/kernel/distwork/arch/x86/vdso/vdso32/../vclock_gettime.c:128:4:
warn
The generated/ prefix is wrong because when using O= to build we add
$(srcdir)/arch/x86/include and $(objdir)/arch/x86/include/generated to the
include path, not $(objdir)/arch/x86/include.
On February 15, 2014 6:33:21 AM PST, Stefani Seibold
wrote:
>
>Am Freitag, den 14.02.2014, 14:32 -0800 s
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fast and a reliable way, be
Am Freitag, den 14.02.2014, 14:40 -0800 schrieb Andy Lutomirski:
> On Fri, Feb 14, 2014 at 12:52 AM, Stefani Seibold wrote:
> > This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
> > and vdso_time() to the 32 bit VDSO.
>
> Is there any chance you can shove this in a git tree s
Am Freitag, den 14.02.2014, 14:32 -0800 schrieb H. Peter Anvin:
> I still get build errors.
>
Oops, i did it again...
> i386 allyesconfig, i386 allmodconfig as well as a more basic i386
> configuration:
>
> arch/x86/vdso/vdso32-int80.so.dbg: undefined symbols found
> make[4]: *** [arch/x86/vds
On Fri, Feb 14, 2014 at 02:40:12PM -0800, Andy Lutomirski wrote:
> On Fri, Feb 14, 2014 at 12:52 AM, Stefani Seibold wrote:
> > This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
> > and vdso_time() to the 32 bit VDSO.
>
> Is there any chance you can shove this in a git tree s
On Fri, Feb 14, 2014 at 12:52 AM, Stefani Seibold wrote:
> This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
> and vdso_time() to the 32 bit VDSO.
Is there any chance you can shove this in a git tree somewhere for the
next version (in addition to sending patches)? I don't ha
I still get build errors.
i386 allyesconfig, i386 allmodconfig as well as a more basic i386
configuration:
arch/x86/vdso/vdso32-int80.so.dbg: undefined symbols found
make[4]: *** [arch/x86/vdso/vdso32-int80.so.dbg] Error 1
x86-64 allyesconfig and x86-64 allmodconfig:
/home/hpa/kernel/distwork/a
This version looks good to me from a quick read.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkm
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fast and a reliable way, be
On 02/13/2014 11:48 PM, Stefani Seibold wrote:
> Am Donnerstag, den 13.02.2014, 22:47 -0800 schrieb H. Peter Anvin:
>> Hi,
>>
>> I tried this patchset, but it fails to compile on i386 "make allyesconfig".
>>
>> -hpa
>>
>
> I tried "make allyseconfig" on my i386, but the resulting config will
Am Donnerstag, den 13.02.2014, 22:47 -0800 schrieb H. Peter Anvin:
> Hi,
>
> I tried this patchset, but it fails to compile on i386 "make allyesconfig".
>
> -hpa
>
I tried "make allyseconfig" on my i386, but the resulting config will
always set CONFIG_X86_64=y, so it fails with
scripts/m
Hi,
I tried this patchset, but it fails to compile on i386 "make allyesconfig".
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fas
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fas
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fas
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fas
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fas
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fas
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fas
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fas
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fas
On Thu, Jan 30, 2014 at 10:03 AM, H. Peter Anvin wrote:
> On 01/30/2014 09:57 AM, Andy Lutomirski wrote:
>>
>> By definition there aren't any broken users of the new functions,
>> because there aren't any users at all. So... should we start
>> randomizing this thing from the beginning?
>>
>
> The
On 01/30/2014 09:57 AM, Andy Lutomirski wrote:
>
> By definition there aren't any broken users of the new functions,
> because there aren't any users at all. So... should we start
> randomizing this thing from the beginning?
>
The vdso already exists. It isn't new. Randomizing it might be a g
On Thu, Jan 30, 2014 at 7:52 AM, Stefani Seibold wrote:
> Am Donnerstag, den 30.01.2014, 07:31 -0800 schrieb H. Peter Anvin:
>> On 01/30/2014 02:49 AM, stef...@seibold.net wrote:
>> > The VDSO page for a 32 bit resided now on 0xc000, followed by the VVAR
>> > and
>> > HPET page.
>>
>> Any rea
On 01/30/2014 07:52 AM, Stefani Seibold wrote:
>
> The reason is that i get need than an additional VMA for HPET and VVAR.
>
> I seen no break of applications since the __FIXADDR_TOP is not on a fix
> place. Lguest, XEN, OPLC and the reservetop Kernel Parameter will change
> the VDSO Page Addres
Am Donnerstag, den 30.01.2014, 07:31 -0800 schrieb H. Peter Anvin:
> On 01/30/2014 02:49 AM, stef...@seibold.net wrote:
> > The VDSO page for a 32 bit resided now on 0xc000, followed by the VVAR
> > and
> > HPET page.
>
> Any reason to not move the vdso base page to the top, in order to avoid
On 01/30/2014 02:49 AM, stef...@seibold.net wrote:
> The VDSO page for a 32 bit resided now on 0xc000, followed by the VVAR and
> HPET page.
Any reason to not move the vdso base page to the top, in order to avoid
breaking broken applications? It seems a fairly innocuous shuffle...
probably li
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time stamp, without knowing the pitfalls. VDSO
time functions a fas
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time time stamp, without knowing the pitfalls. VDSO
time functions
On 12/17/2012 02:12 PM, stef...@seibold.net wrote:
> arch/x86/Kconfig | 4 +-
> arch/x86/include/asm/clocksource.h| 4 -
> arch/x86/include/asm/fixmap.h | 6 +-
> arch/x86/include/asm/vgtod.h | 10 ++-
> arch/x86/include/asm/vsyscall.h | 1 -
On Mon, Dec 17, 2012 at 2:12 PM, wrote:
> From: Stefani Seibold
>
> This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
> and vdso_time() to the 32 bit VDSO.
>
> The reason to do this was to get a fast reliable time stamp. Many developers
> uses TSC to get a fast time time sta
From: Stefani Seibold
This patch add the functions vdso_gettimeofday(), vdso_clock_gettime()
and vdso_time() to the 32 bit VDSO.
The reason to do this was to get a fast reliable time stamp. Many developers
uses TSC to get a fast time time stamp, without knowing the pitfalls. VDSO
time functions
61 matches
Mail list logo
