linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Otte <cotte@de.ibm.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Arnd Bergmann <arnd@arndb.de>,
	coywolf@lovecn.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, schwidefsky@de.ibm.com,
	akpm@osdl.org
Subject: Re: [RFC/PATCH 0/5] add execute in place support
Date: Wed, 01 Jun 2005 16:03:45 +0200	[thread overview]
Message-ID: <429DC041.6070001@de.ibm.com> (raw)
In-Reply-To: <20050601133938.GB29116@wohnheim.fh-wedel.de>

Jörn Engel wrote:

>On Wed, 1 June 2005 14:06:03 +0200, Arnd Bergmann wrote:
>  
>
>>On Middeweken 01 Juni 2005 12:12, Coywolf Qi Hunt wrote:
>>    
>>
>>>>As I'd like to aim for integration into -mm and vanilla later on,
>>>>I'd like to encourage everyone to give it a read and provide
>>>>feedback. All patches apply against git-head as of today.
>>>>        
>>>>
>>>I feel the name "execute in place" misleading. This is not the real
>>>XIP, IMHO. Invent another term or be tolerant?
>>>      
>>>
>>If this is not real execute in place, then what is? The term seems to
>>describe the patch rather well and we don't have this ability for Linux
>>applications anywhere else, at least not in official kernels.
>>    
>>
>
>We can execute the kernel in place, thanks to Nicolas Pitre.  For
>userspace I have seen to preparation patches, but nothing serious.
>  
>
Given that execute in place describes the ability to run code at
the very same location where it is permanently stored, and that
this is exactly what the patch enables, I think the wording is
correct.


-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2005-06-01 14:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 14:29 [RFC/PATCH 0/5] add execute in place support Carsten Otte
2005-05-11 16:19 ` David Woodhouse
2005-05-11 16:35   ` Carsten Otte
2005-05-12  8:57     ` Jörn Engel
2005-05-12  9:10       ` Carsten Otte
2005-05-12  9:43       ` David Woodhouse
2005-06-01  9:33         ` Coywolf Qi Hunt
2005-06-01 11:31           ` Jörn Engel
2005-06-01 10:12 ` Coywolf Qi Hunt
2005-06-01 12:06   ` Arnd Bergmann
2005-06-01 13:39     ` Jörn Engel
2005-06-01 14:03       ` Carsten Otte [this message]
2005-06-01 14:10         ` Jörn Engel

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=429DC041.6070001@de.ibm.com \
    --to=cotte@de.ibm.com \
    --cc=akpm@osdl.org \
    --cc=arnd@arndb.de \
    --cc=cotte@freenet.de \
    --cc=coywolf@lovecn.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).