Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-07 Thread H.J. Lu
On Sat, Mar 7, 2015 at 4:00 AM, Alan Modra wrote: > On Fri, Mar 06, 2015 at 05:03:21PM -0800, H.J. Lu wrote: >> I updated the testcase to > > Thanks, that's good to see. > Did you make it to work on PPC? -- H.J.

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-07 Thread Alan Modra
On Fri, Mar 06, 2015 at 05:03:21PM -0800, H.J. Lu wrote: > I updated the testcase to Thanks, that's good to see. -- Alan Modra Australia Development Lab, IBM

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-06 Thread H.J. Lu
On Fri, Mar 6, 2015 at 4:15 PM, Alan Modra wrote: > On Fri, Mar 06, 2015 at 05:04:56AM -0800, H.J. Lu wrote: >> On Thu, Mar 5, 2015 at 8:19 PM, Alan Modra wrote: >> > On Wed, Mar 04, 2015 at 03:26:10PM -0800, H.J. Lu wrote: >> >> Protected symbol means that it can't be pre-emptied. It >> >> does

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-06 Thread Alan Modra
On Fri, Mar 06, 2015 at 05:04:56AM -0800, H.J. Lu wrote: > On Thu, Mar 5, 2015 at 8:19 PM, Alan Modra wrote: > > On Wed, Mar 04, 2015 at 03:26:10PM -0800, H.J. Lu wrote: > >> Protected symbol means that it can't be pre-emptied. It > >> doesn't mean its address won't be external. This is true > >

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-06 Thread H.J. Lu
On Thu, Mar 5, 2015 at 6:39 AM, H.J. Lu wrote: > On Wed, Mar 4, 2015 at 3:26 PM, H.J. Lu wrote: >> Protected symbol means that it can't be pre-emptied. It >> doesn't mean its address won't be external. This is true >> for pointer to protected function. With copy relocation, >> address of prote

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-06 Thread H.J. Lu
On Fri, Mar 6, 2015 at 10:29 AM, Joseph Myers wrote: > On Wed, 4 Mar 2015, H.J. Lu wrote: > >> Protected symbol means that it can't be pre-emptied. It >> doesn't mean its address won't be external. This is true >> for pointer to protected function. With copy relocation, >> address of protected

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-06 Thread Joseph Myers
On Wed, 4 Mar 2015, H.J. Lu wrote: > Protected symbol means that it can't be pre-emptied. It > doesn't mean its address won't be external. This is true > for pointer to protected function. With copy relocation, > address of protected data defined in the shared library may > also be external. W

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-06 Thread H.J. Lu
On Thu, Mar 5, 2015 at 8:19 PM, Alan Modra wrote: > On Wed, Mar 04, 2015 at 03:26:10PM -0800, H.J. Lu wrote: >> Protected symbol means that it can't be pre-emptied. It >> doesn't mean its address won't be external. This is true >> for pointer to protected function. With copy relocation, >> addr

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-06 Thread Szabolcs Nagy
On 04/03/15 23:26, H.J. Lu wrote: > Protected symbol means that it can't be pre-emptied. It > doesn't mean its address won't be external. This is true > for pointer to protected function. With copy relocation, > address of protected data defined in the shared library may > also be external. W

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-05 Thread Alan Modra
On Wed, Mar 04, 2015 at 03:26:10PM -0800, H.J. Lu wrote: > Protected symbol means that it can't be pre-emptied. It > doesn't mean its address won't be external. This is true > for pointer to protected function. With copy relocation, > address of protected data defined in the shared library may >

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-05 Thread H.J. Lu
On Thu, Mar 5, 2015 at 9:32 AM, Rich Felker wrote: > On Thu, Mar 05, 2015 at 06:39:10AM -0800, H.J. Lu wrote: >> On Wed, Mar 4, 2015 at 3:26 PM, H.J. Lu wrote: >> > Protected symbol means that it can't be pre-emptied. It >> > doesn't mean its address won't be external. This is true >> > for poi

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-05 Thread Rich Felker
On Thu, Mar 05, 2015 at 06:39:10AM -0800, H.J. Lu wrote: > On Wed, Mar 4, 2015 at 3:26 PM, H.J. Lu wrote: > > Protected symbol means that it can't be pre-emptied. It > > doesn't mean its address won't be external. This is true > > for pointer to protected function. With copy relocation, > > add

Re: RFC: PATCHES: Properly handle reference to protected data on x86

2015-03-05 Thread H.J. Lu
On Wed, Mar 4, 2015 at 3:26 PM, H.J. Lu wrote: > Protected symbol means that it can't be pre-emptied. It > doesn't mean its address won't be external. This is true > for pointer to protected function. With copy relocation, > address of protected data defined in the shared library may > also be