<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/powerpc/kernel/vdso64, branch linux-2.6.28.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.28.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.28.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2008-07-03T06:58:10Z</updated>
<entry>
<title>powerpc: Fixup lwsync at runtime</title>
<updated>2008-07-03T06:58:10Z</updated>
<author>
<name>Kumar Gala</name>
</author>
<published>2008-07-01T15:16:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2d1b2027626d5151fff8ef7c06ca8e7876a1a510'/>
<id>urn:sha1:2d1b2027626d5151fff8ef7c06ca8e7876a1a510</id>
<content type='text'>
To allow for a single kernel image on e500 v1/v2/mc we need to fixup lwsync
at runtime.  On e500v1/v2 lwsync causes an illop so we need to patch up
the code.  We default to 'sync' since that is always safe and if the cpu
is capable we will replace 'sync' with 'lwsync'.

We introduce CPU_FTR_LWSYNC as a way to determine at runtime if this is
needed.  This flag could be moved elsewhere since we dont really use it
for the normal CPU_FTR purpose.

Finally we only store the relative offset in the fixup section to keep it
as small as possible rather than using a full fixup_entry.

Signed-off-by: Kumar Gala &lt;galak@kernel.crashing.org&gt;
Signed-off-by: Paul Mackerras &lt;paulus@samba.org&gt;
</content>
</entry>
<entry>
<title>powerpc: Introduce infrastructure for feature sections with alternatives</title>
<updated>2008-07-01T01:28:28Z</updated>
<author>
<name>Michael Ellerman</name>
</author>
<published>2008-06-24T01:32:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fac23fe4be23259a8eaa9bad822f5b14dd07d15c'/>
<id>urn:sha1:fac23fe4be23259a8eaa9bad822f5b14dd07d15c</id>
<content type='text'>
The current feature section logic only supports nop'ing out code, this means
if you want to choose at runtime between instruction sequences, one or both
cases will have to execute the nop'ed out contents of the other section, eg:

BEGIN_FTR_SECTION
	or	1,1,1
END_FTR_SECTION_IFSET(FOO)
BEGIN_FTR_SECTION
	or	2,2,2
END_FTR_SECTION_IFCLR(FOO)

and the resulting code will be either,

	or	1,1,1
	nop

or,
	nop
	or	2,2,2

For small code segments this is fine, but for larger code blocks and in
performance criticial code segments, it would be nice to avoid the nops.
This commit starts to implement logic to allow the following:

BEGIN_FTR_SECTION
	or	1,1,1
FTR_SECTION_ELSE
	or	2,2,2
ALT_FTR_SECTION_END_IFSET(FOO)

and the resulting code will be:

	or	1,1,1
or,
	or	2,2,2

We achieve this by extending the existing FTR macros. The current feature
section semantic just becomes a special case, ie. if the else case is empty
we nop out the default case.

The key limitation is that the size of the else case must be less than or
equal to the size of the default case. If the else case is smaller the
remainder of the section is nop'ed.

We let the linker put the else case code in with the rest of the text,
so that relative branches from the else case are more likley to link,
this has the disadvantage that we can't free the unused else cases.

This commit introduces the required macro and linker script changes, but
does not enable the patching of the alternative sections.

We also need to update two hand-made section entries in reg.h and timex.h

Signed-off-by: Michael Ellerman &lt;michael@ellerman.id.au&gt;
Signed-off-by: Paul Mackerras &lt;paulus@samba.org&gt;
</content>
</entry>
<entry>
<title>[POWERPC] Tweak VDSO linker script to avoid upsetting old binutils</title>
<updated>2008-05-23T05:27:23Z</updated>
<author>
<name>Roland McGrath</name>
</author>
<published>2008-05-11T00:40:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2ca7633dc73405ee775a2e9b7961b47a38bc882d'/>
<id>urn:sha1:2ca7633dc73405ee775a2e9b7961b47a38bc882d</id>
<content type='text'>
This works around bugs in older binutils' objcopy.
The placement of these sections does not really matter,
but it confused the buggy old BFD libraries.

Signed-off-by: Roland McGrath &lt;roland@redhat.com&gt;
Signed-off-by: Paul Mackerras &lt;paulus@samba.org&gt;
</content>
</entry>
<entry>
<title>[POWERPC] vdso: Fixes for cache block sizes</title>
<updated>2007-11-20T02:56:31Z</updated>
<author>
<name>Olof Johansson</name>
</author>
<published>2007-11-20T01:24:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fbe481756df57673b6acbcd2e139d0d2658f2188'/>
<id>urn:sha1:fbe481756df57673b6acbcd2e139d0d2658f2188</id>
<content type='text'>
The current VDSO implementation is hardcoded to 128 byte cache blocks,
which are only used on IBM's 64-bit processors.

Convert it to get the cache block sizes out of vdso_data instead,
similar to how the ppc64 in-kernel cache flush does it.

Signed-off-by: Olof Johansson &lt;olof@lixom.net&gt;
Signed-off-by: Paul Mackerras &lt;paulus@samba.org&gt;
</content>
</entry>
<entry>
<title>[POWERPC] Fix 64 bits vDSO DWARF info for CR register</title>
<updated>2007-10-17T12:30:09Z</updated>
<author>
<name>Benjamin Herrenschmidt</name>
</author>
<published>2007-10-17T04:26:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=081c11a5d0cc24ab58adc7de2ddf209149bf176f'/>
<id>urn:sha1:081c11a5d0cc24ab58adc7de2ddf209149bf176f</id>
<content type='text'>
The current DWARF info for CR are incorrect, causing the gcc unwinder to
go to lunch if we take a segfault in the vdso.  This fixes it.

Problem identified by Andrew Haley, and fix provided by Jakub Jelinek
(thanks !).

Unfortunately, a bug in gcc cause it to not quite work either, but that
is being fixed separately with something around the lines of:

linux-unwind.h:

     fs-&gt;regs.reg[R_CR2].loc.offset = (long) &amp;regs-&gt;ccr - new_cfa;
+    /* CR? regs are just 32-bit and PPC is big-endian.  */
+    fs-&gt;regs.reg[R_CR2].loc.offset += sizeof (long) - 4;

(According to Jakub)

Signed-off-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Signed-off-by: Paul Mackerras &lt;paulus@samba.org&gt;
</content>
</entry>
<entry>
<title>powerpc64 vDSO: linker script indentation</title>
<updated>2007-10-16T17:01:50Z</updated>
<author>
<name>Roland McGrath</name>
</author>
<published>2007-10-16T03:43:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=558da7561e3362d4ec3a62e5994235d21651d802'/>
<id>urn:sha1:558da7561e3362d4ec3a62e5994235d21651d802</id>
<content type='text'>
This cleans up the formatting in the vDSO linker script, mostly just the
use of whitespace.  It's intended to approximate the kernel standard
conventions for indenting C, treating elements of the linker script about
like initialized variable definitions.

Signed-off-by: Roland McGrath &lt;roland@redhat.com&gt;
Acked-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Cc: Sam Ravnborg &lt;sam@ravnborg.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[POWERPC] Update .gitignore for new vdso generated files</title>
<updated>2007-10-08T13:38:12Z</updated>
<author>
<name>Kumar Gala</name>
</author>
<published>2007-10-03T15:43:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6039680705906f270411435c05c869ac4f59ef10'/>
<id>urn:sha1:6039680705906f270411435c05c869ac4f59ef10</id>
<content type='text'>
We now generate vdso[32,64].so.dbg as part of the build so
add them to .gitignore

Signed-off-by: Kumar Gala &lt;galak@kernel.crashing.org&gt;
</content>
</entry>
<entry>
<title>[POWERPC] powerpc vDSO: install unstripped copies on disk</title>
<updated>2007-10-03T02:02:43Z</updated>
<author>
<name>Roland McGrath</name>
</author>
<published>2007-10-02T20:30:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8150caad02266623b5b9f58088d589f130fccd97'/>
<id>urn:sha1:8150caad02266623b5b9f58088d589f130fccd97</id>
<content type='text'>
This keeps an unstripped copy of the vDSO images built before they are
stripped and embedded in the kernel.  The unstripped copies get installed in
$(MODLIB)/vdso/ by "make install".  These files can be useful when they
contain source-level debugging information.

Signed-off-by: Roland McGrath &lt;roland@redhat.com&gt;
Cc: Sam Ravnborg &lt;sam@ravnborg.org&gt;
Cc: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Paul Mackerras &lt;paulus@samba.org&gt;
</content>
</entry>
<entry>
<title>Fix VDSO gettimeofday() when called with NULL struct timeval.</title>
<updated>2007-06-30T04:27:00Z</updated>
<author>
<name>Will Schmidt</name>
</author>
<published>2007-06-29T20:49:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fde937d826e43c9fe7fecc98b6f3da7188e76930'/>
<id>urn:sha1:fde937d826e43c9fe7fecc98b6f3da7188e76930</id>
<content type='text'>
The vdso64 portion of patch 74609f4536f2b8fd6a48381bbbe3cd37da20a527 for
fixing problems with NULL gettimeofday input mistakenly checks for a
null tz field twice, when it should be checking for null tz once, and
null tv once; by way of a r10/r11 typo.

Any application calling gettimeofday(&amp;tv,NULL) will "fail".

This corrects that typo, and makes my G5 happy.

Tested on G5.

Signed-off-by: Will Schmidt &lt;will_schmidt@vnet.ibm.com&gt;
Cc: Tony Breeds &lt;tony@bakeyournoodle.com&gt;
Forwarded-by: Ben Herrenschmidt &lt;benh@kernel.crashing.org&gt;

[ Ben says: "I checked the 32 bits part of the change is correct.  You
  can probably blame me for originally writing the 2 versions with
  inversed usage of r10 and r11, thus confusing Tony :-)"

  Ben duly blamed.   - Linus ]

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>[POWERPC] Fix VDSO gettimeofday() when called with NULL struct timeval</title>
<updated>2007-06-26T04:41:19Z</updated>
<author>
<name>Tony Breeds</name>
</author>
<published>2007-06-25T23:50:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=74609f4536f2b8fd6a48381bbbe3cd37da20a527'/>
<id>urn:sha1:74609f4536f2b8fd6a48381bbbe3cd37da20a527</id>
<content type='text'>
Consider the prototype for gettimeofday():
	int gettimofday(struct timeval *tv, struct timezone *tz);

Although it is valid to call with /either/ tv or tz being NULL, and
the C version of sys_gettimeofday() supports this, the current version
of gettimeofday() in the VDSO will SEGV if called with a NULL tv.

This adds a check for tv being NULL so that it doesn't SEGV.

Signed-off-by: Tony Breeds &lt;tony@bakeyournoodle.com&gt;
Acked-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Signed-off-by: Paul Mackerras &lt;paulus@samba.org&gt;
</content>
</entry>
</feed>
