Messages in this thread | | | Date | Mon, 18 Apr 2005 01:59:54 -0700 | From | Chris Wedgwood <> | Subject | Re: [PATCH x86_64] Live Patching Function on 2.6.11.7 |
| |
On Mon, Apr 18, 2005 at 05:37:09PM +0900, Takashi Ikebe wrote:
> As you said, if we can migrate the data to new process without > stopping service, it is OK, but the real applications need to > takeover data very much(sometimes it's over gigabyte....depends on > service, and causes service disruption...).
man mmap man 5 ipc
> So, live patching seems reasonable to us.
That still doesn't tell me why it's necessary to do something so complicated
> 2. Activate the patch modules with pannus -a command. > - stop the target process and check current instruction not to conflict. > - if it is not conflict, overwrite the jump assembly to function's > entrypoiny where you want to fix, to patch module's one. > - restart the process.
there is a still a stop/start here
why not just hand the state of to a different process? how is that slower?
> Will this be answer??
maybe, but i'm far from convinced it's necessary and therefore warrants a big ugly kernel patch
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |