* Re: [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Fix mode of mayday syscall [not found] <E1Z6JYL-0001WU-7T@sd-51317.xenomai.org> @ 2015-06-20 14:41 ` Gilles Chanteperdrix 2015-06-22 8:19 ` Jan Kiszka 0 siblings, 1 reply; 2+ messages in thread From: Gilles Chanteperdrix @ 2015-06-20 14:41 UTC (permalink / raw) To: xenomai git repository hosting wrote: > Module: xenomai-jki > Branch: for-forge > Commit: c806b60eaf505aafd4dbeeaf59cd3fc6d68703fa > URL: > http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=c806b60eaf505aafd4dbeeaf59cd3fc6d68703fa > > Author: Jan Kiszka <jan.kiszka@siemens.com> > Date: Fri Jun 19 15:59:15 2015 +0200 > > cobalt/kernel: Fix mode of mayday syscall > > The oneway mode meant norestart, thus return -EINTR instead of retrying > the syscall after signal processing. But this caused damaged to the > register state of the mayday-interrupted thread, most visible on x86-64 > where RAX is holding the RIP. And this can not be fixed, because ? -- Gilles. https://click-hack.org ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Fix mode of mayday syscall 2015-06-20 14:41 ` [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Fix mode of mayday syscall Gilles Chanteperdrix @ 2015-06-22 8:19 ` Jan Kiszka 0 siblings, 0 replies; 2+ messages in thread From: Jan Kiszka @ 2015-06-22 8:19 UTC (permalink / raw) To: Gilles Chanteperdrix, xenomai On 2015-06-20 16:41, Gilles Chanteperdrix wrote: > > git repository hosting wrote: >> Module: xenomai-jki >> Branch: for-forge >> Commit: c806b60eaf505aafd4dbeeaf59cd3fc6d68703fa >> URL: >> http://git.xenomai.org/?p=xenomai-jki.git;a=commit;h=c806b60eaf505aafd4dbeeaf59cd3fc6d68703fa >> >> Author: Jan Kiszka <jan.kiszka@siemens.com> >> Date: Fri Jun 19 15:59:15 2015 +0200 >> >> cobalt/kernel: Fix mode of mayday syscall >> >> The oneway mode meant norestart, thus return -EINTR instead of retrying >> the syscall after signal processing. But this caused damaged to the >> register state of the mayday-interrupted thread, most visible on x86-64 >> where RAX is holding the RIP. > > And this can not be fixed, because ? There are probably more ways to fix it. One I played with as well was manipulating the mayday page's stack from the kernel, thus its return address (in the hope it would fix the backtrace too, but it didn't). But this patch is obsolete if the mayday simplification patch pushed yesterday can be merged for all archs. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-06-22 8:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <E1Z6JYL-0001WU-7T@sd-51317.xenomai.org>
2015-06-20 14:41 ` [Xenomai] [Xenomai-git] Jan Kiszka : cobalt/kernel: Fix mode of mayday syscall Gilles Chanteperdrix
2015-06-22 8:19 ` Jan Kiszka
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.