All of lore.kernel.org
 help / color / mirror / Atom feed
From: gilles.chanteperdrix@xenomai.org (Gilles Chanteperdrix)
To: linux-arm-kernel@lists.infradead.org
Subject: Loading handle_arch_irq with a PC relative load
Date: Fri, 13 Jul 2012 21:51:15 +0200	[thread overview]
Message-ID: <50007C33.4000105@xenomai.org> (raw)
In-Reply-To: <alpine.LFD.2.02.1207131536260.14068@xanadu.home>

On 07/13/2012 09:40 PM, Nicolas Pitre wrote:
> On Fri, 13 Jul 2012, Gilles Chanteperdrix wrote:
> 
>>
>> I do not know if it is really useful, but it seems it would be possible 
>> to reduce the number of memory accesses to just one in the irq_handler 
>> macro in the case where CONFIG_MULTI_IRQ_HANDLER is enabled, by using a 
>> PC relative load, with something like the following patch:
> 
> To be strict with ccode sections, you can't do this.  The 
> handle_arch_irq symbol identifies a variable and with your patch you're 
> moving it from the .data section to the .text section.  The .text 
> section is meant to be read only, and this is even more true when using 
> a XIP kernel where .text is in ROM, or if we could make the access 
> protection of the kernel ro.

I understand that but, XIP kernel aside, the handle_arch_irq variable is
set only once very early during the boot process, so, almost read-only.
Is not Linux using self-modifying code in some cases anyway (booting an
SMP kernel on an UP processor for instance).

-- 
                                                                Gilles.

  reply	other threads:[~2012-07-13 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13 19:05 Loading handle_arch_irq with a PC relative load Gilles Chanteperdrix
2012-07-13 19:40 ` Nicolas Pitre
2012-07-13 19:51   ` Gilles Chanteperdrix [this message]
2012-07-13 20:09     ` Nicolas Pitre
2012-07-13 20:13       ` Gilles Chanteperdrix
2012-07-14 10:39       ` Gilles Chanteperdrix

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=50007C33.4000105@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=linux-arm-kernel@lists.infradead.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 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.