All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Wolfgang Mauerer <wolfgang.mauerer@domain.hid>
Cc: adeos-main@gna.org, "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Fwd: Re: [RFC][PATCH] x86: Fix root domain state restoring on exception return
Date: Mon, 25 Jan 2010 09:45:08 +0100	[thread overview]
Message-ID: <4B5D5A14.3030909@domain.hid> (raw)
In-Reply-To: <4B5D58E2.60603@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]

Wolfgang Mauerer wrote:
> (sorry if you get this twice, the cc addresses were screwed up
> by copy and paste last time)
> 
> Kiszka, Jan wrote:
> 
>> If we enter __ipipe_handle_exception over a non-root domain and leave it
>> due to migration in the event handler over root, we must not restore the
>> root domain state so far saved on entry. This caused subtle pipeline
>> state corruptions. Actually, we only need to save the state if we enter
>> over the root domain and have to align its state to the hardware
>> interrupt mask.
>>
>> Moreover, the x86-32 regs.eflags fix-up must happen based on the current
>> root domain state to avoid more spurious corruptions.
> 
> unfortunately, this won't boot on x86-32: During CPU bug checking
> in check_hlt, the kernel will really go into the halt state and
> never recover. By modifying __ipipe_handle_exception to use
> raw_irqs_disabled_flags as argument to __fixup_if instead of
> raw_irqs_disabled, everything is back to normal again. However,

That would reintroduce the bug we saw on 64 bit to 32 bit (in a slight
variation). So we need to understand what goes wrong here. Can you
generate an ipipe panic trace?

> I'm not sure if this is a) the proper solution or b) won't cause
> problems somewhere else, so a discussion would be highly welcome...
> 
> Cheers, Wolfgang
> 

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2010-01-25  8:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25  8:40 [Xenomai-core] Fwd: Re: [RFC][PATCH] x86: Fix root domain state restoring on exception return Wolfgang Mauerer
2010-01-25  8:45 ` Jan Kiszka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-25 18:33 Wolfgang Mauerer

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=4B5D5A14.3030909@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=wolfgang.mauerer@domain.hid \
    --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.