From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Adeos-main] [BUG] Interrupt recursion with libata-sff
Date: Thu, 20 May 2010 12:16:10 +0200 [thread overview]
Message-ID: <4BF50BEA.4030208@domain.hid> (raw)
In-Reply-To: <4BF50124.20801@domain.hid>
Jan Kiszka wrote:
> Looks like your problem is x86-32 returning from interrupts with hard
> IRQs enabled (and therefore flushing the pipeline already over the
> interrupt handler). That should ideally be unified with x86-64 now, also
> as x86-64 may already gain better testing than 32 bit.
I may have not understood right, but from my understanding, the big
difference between x86_32 and x86_64 is that interrupts flags are
virtualized in x86_32's entry.S. To unify x86_32 and x86_64 would
basically mean rewrite this. And the the two entry.S are separated, so
x86_32 has to be tested separately from x86_64.
--
Gilles.
next prev parent reply other threads:[~2010-05-20 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 9:25 [Adeos-main] [BUG] Interrupt recursion with libata-sff Sebastian Smolorz
2010-05-20 9:30 ` Jan Kiszka
2010-05-20 10:16 ` Gilles Chanteperdrix [this message]
2010-05-20 10:23 ` Jan Kiszka
2010-05-21 21:15 ` Philippe Gerum
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=4BF50BEA.4030208@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=adeos-main@gna.org \
--cc=jan.kiszka@domain.hid \
/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.