public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: David Howells <dhowells@redhat.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [QUESTION] FRV: linking error?
Date: Wed, 20 Feb 2008 20:51:45 +0300	[thread overview]
Message-ID: <20080220175145.GA6733@cvg> (raw)
In-Reply-To: <20080220131442.GA18790@uranus.ravnborg.org>

[Sam Ravnborg - Wed, Feb 20, 2008 at 02:14:42PM +0100]
| On Wed, Feb 20, 2008 at 01:01:05PM +0000, David Howells wrote:
| > Cyrill Gorcunov <gorcunov@gmail.com> wrote:
| > 
| > > being see over vmlinux.lds for FRV architecture I found the string:
| > > 
| > > 	. = ALIGN(4096);
| > > 	.data.page_aligned : { *(.data.idt) }
| > > 
| > > though the PAGE_SIZE is 16K. Can't figure out why is that...
| > > Do you have a few spare minutes to explain, please?
| > 
| > Ummm...  Good question.  Probably a legacy thing.  I think the .data.idt
| > section is also an x86-only thing and should be dispensed with for FRV.
| > Leastways, the section has nothing in it according to the link map.
| 
| A quick grep agree with you.
| I see it used only in x86 in traps_32 for the F0 0F bug.
| It exist in several .lds files - including frv.
| 
| 	Sam
| 

Sam, maybe we should just eliminate this section at least for FRV?

		- Cyrill -

  reply	other threads:[~2008-02-20 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 20:03 [QUESTION] FRV: linking error? Cyrill Gorcunov
2008-02-20 13:01 ` David Howells
2008-02-20 13:14   ` Sam Ravnborg
2008-02-20 17:51     ` Cyrill Gorcunov [this message]
2008-02-20 18:13       ` David Howells
2008-02-20 18:15         ` Cyrill Gorcunov
2008-02-20 19:19           ` Sam Ravnborg
2008-02-20 19:21             ` Cyrill Gorcunov
2008-02-20 17:52   ` Cyrill Gorcunov

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=20080220175145.GA6733@cvg \
    --to=gorcunov@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox