On Thu, 2007-07-12 at 21:14 -0700, Daniel Walker wrote:
> 
> It looks like your patch might be line wrapped ?
> 

I reconstituted the patch to clear the white space damage.

- Sven

>From [EMAIL PROTECTED] Thu Jul 12 21:59:46 2007
Mime-Version: 1.0
X-Mailer: GroupWise 7.0.2 HP
Subject: [PATCH] RT: add clock.cycle_accumulated to vsyscall gtod update
Date: Thu, 12 Jul 2007 21:59:46 -0600
Message-ID: <[EMAIL PROTECTED]>
From: "Gregory Haskins" <[EMAIL PROTECTED]>
To: "Ingo Molnar" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Cc: "Sven Dietrich" <[EMAIL PROTECTED]>, "David Bahi" <[EMAIL PROTECTED]>, 
[email protected]
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
X-Evolution-Source: imap://[EMAIL PROTECTED]/
Content-Transfer-Encoding: 8bit

2.6.22 changed the vsyscall mechanism to store a more cache-thrash
friendly version of the gtod data.  The original gtod cache code used an
entire struct clock + structure-copy, whereas the new code uses a
pseudo/shadow version + explicit-copy. 

clock.cycle_accumulated was added to RT prior to 2.6.22 so the vsyscall
code must also be updated for the port to 22.

Signed-off-by: Gregory Haskins <[EMAIL PROTECTED]>

Acked-by: Sven-Thorsten Dietrich <[EMAIL PROTECTED]>

--- 

 vsyscall.c |    1 +
 1 file changed, 1 insertion(+)

Index: linux-2.6.22/arch/x86_64/kernel/vsyscall.c
===================================================================
--- linux-2.6.22.orig/arch/x86_64/kernel/vsyscall.c
+++ linux-2.6.22/arch/x86_64/kernel/vsyscall.c
@@ -90,6 +90,7 @@ void update_vsyscall(struct timespec *wa
        /* copy vsyscall data */
        vsyscall_gtod_data.clock.vread = clock->vread;
        vsyscall_gtod_data.clock.cycle_last = clock->cycle_last;
+       vsyscall_gtod_data.clock.cycle_accumulated = clock->cycle_accumulated;
        vsyscall_gtod_data.clock.mask = clock->mask;
        vsyscall_gtod_data.clock.mult = clock->mult;
        vsyscall_gtod_data.clock.shift = clock->shift;
-
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to