From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Git pull request.
Date: Fri, 10 Apr 2009 14:32:24 +0200 [thread overview]
Message-ID: <49DF3C58.2070207@domain.hid> (raw)
In-Reply-To: <49DF36CE.6020105@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 2611 bytes --]
Gilles Chanteperdrix wrote:
> Philippe Gerum wrote:
>> On Fri, 2009-04-10 at 11:23 +0200, Gilles Chanteperdrix wrote:
>>> Hi Philippe,
>>>
>>> I got some changes ready for head. What we want to include in the stable
>>> branch remains to be discussed, once we agree, I will prepare another
>>> branch for v2.4.x patches.
>>>
>> No objection to merge back FPU fixes to 2.4.x before we close that
>> branch, when 2.5 is out. This would give us some time to make sure
>> everything is fine while running the -rc series.
>
> Ok. I was thinking that it may be dangerous to merge the "Optimize x86
> fpu switches" patch, since it is not strictly necessary. But from the
> point of view of getting it tested ASAP by users, you are right. The
> concern about switchtest is that the changes once again break the driver
> ABI.
>
>>> The following changes since commit bbbaec33689d8e82b604745bb55209a83d79a4bc:
>>> Philippe Gerum (1):
>>> Test for self-deletion in a safer way
>>>
>>> are available in the git repository at:
>>>
>>> git://git.xenomai.org/xenomai-gch.git for-upstream
>>>
>>> Gilles Chanteperdrix (4):
>>> Improve switchtest coverage.
>>> x86 FPU fixes
>>> Optimize x86 fpu switches.
>>> Fix rt_task_trampoline and rt_task_shadow error paths.
>> I'm generally ok with the patches, but the last one still leaves an
>> issue open: if the child thread dies upon -ENOMEM, the creator won't be
>> unblocked from pending on the completion sync in rt_task_create(). We
>> could live with this for a while (lacking memory at that point is a
>> clear sign that things are going to turn ugly very soon anyway), but
>> would we want to fix this, we would have to either fire the
>> __rt_task_create syscall with some NULL args and let it notice them,
>> then signal the completion block with an error status, or have something
>> like __xn_sys_sigcompletion to unblock the waiter directly from
>> userland.
>
> I just reused the "fail" label of rt_task_trampoline without thinking
> about the consequences. Will try to see which idea is simpler to
> implement. In any case, I am afraid we will get yet another ABI change.
>
> A question about git now: can I "git reset" or "git branch -D" a remote
> branch ?
Just add '-f' to your push command if you have dropped or updated some
patch that is already present in the remote repos (I'm always doing this
when pushing my stgit-managed patch queues).
Deleting a branch remotely is something I haven't tried yet, but the
examples in 'man git-push' claim it works.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-04-10 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-10 9:23 [Xenomai-core] Git pull request Gilles Chanteperdrix
2009-04-10 10:23 ` Philippe Gerum
2009-04-10 12:08 ` Gilles Chanteperdrix
2009-04-10 12:32 ` Jan Kiszka [this message]
2009-04-10 13:23 ` Philippe Gerum
2009-04-11 16:23 ` 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=49DF3C58.2070207@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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.