All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <xili_gchen_5257@hotmail.com>
To: Steven Miao <realmz6@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
	bfin <adi-buildroot-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blackfin: Makefile: Skip reloc overflow issue when COMPILE_TEST enabled
Date: Fri, 24 Apr 2015 22:28:17 +0800	[thread overview]
Message-ID: <BLU437-SMTP361E3BF850559A04BBD7B6B9EC0@phx.gbl> (raw)
In-Reply-To: <CAMk6uB=pZSMd1ADtMUq0gGHe0zxSYHDN2Fy_VFxw-xE4vr1weQ@mail.gmail.com>

On 4/24/15 16:20, Steven Miao wrote:
> On Thu, Apr 23, 2015 at 10:30 PM, Chen Gang <xili_gchen_5257@hotmail.com> wrote:
>>
>> OK, thanks. I guess your meaning is:
>>
>>  - If the kernel is too big, it may let the pc which wants to call L1
>>    space fail.
>>
>>  - So the kernel is too big to cause this issue, but it is nothing with
>>    'overwritten' in my original patch comments.
>>
> Yes, it is.

OK, thanks.

>>  - We can treat it as environments limitation, then can use COMPILE_TEST
>>    for it. So this patch is still OK, except the related comments need
>>    be improved (at least need to remove 'overwritten').
>>
> If pc-relative CALL will fail, there will be "relocation truncated to
> fit: R_BFIN_PCREL24" warnings.

OK, thanks. for me, we need to skip these warnings when COMPILE_TEST
is set, so can continue compiling (or will cause building break).

>>
>> I guess, what I said above is meaningless (although it is correct).
>>
>>>>  - if kernel is too big, the contents before l1.text (the other contents
>>>>    in .init.text) will override it, so ld reports issues.
>>
> Actually the kernel which is large the 16M could not happen, large
> size kernel image is not sugguested on a embedded system.
> 

OK, thanks. So for me, it should only happen when COMPILE_TEST is set,
should not happen in real world using.


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

  reply	other threads:[~2015-04-24 14:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 21:03 [PATCH] blackfin: Makefile: Skip reloc overflow issue when COMPILE_TEST enabled Chen Gang
2015-04-08 21:10 ` Chen Gang
2015-04-08 21:12   ` Richard Weinberger
2015-04-09 13:28     ` Chen Gang
2015-04-09 13:38       ` Richard Weinberger
2015-04-09 23:14         ` Chen Gang
2015-04-22  9:00 ` Steven Miao
2015-04-22 14:32   ` Chen Gang
2015-04-23  2:51     ` Steven Miao
2015-04-23 14:30       ` Chen Gang
2015-04-24  8:20         ` Steven Miao
2015-04-24 14:28           ` Chen Gang [this message]
     [not found] ` <5525994D.6090901@hotmail.com>
2015-07-01 15:31   ` Chen Gang
2015-07-01 15:36   ` Chen Gang
2015-04-08 21:05 Chen Gang
2015-04-08 21:10 ` Richard Weinberger
2015-04-08 21:16   ` Chen Gang
2015-04-08 21:19     ` Richard Weinberger
2015-04-09 13:15       ` Chen Gang
2015-04-08 21:05 Chen Gang
2015-04-08 21:07 Chen Gang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BLU437-SMTP361E3BF850559A04BBD7B6B9EC0@phx.gbl \
    --to=xili_gchen_5257@hotmail.com \
    --cc=adi-buildroot-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=realmz6@gmail.com \
    --cc=richard.weinberger@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.