From: Andi Kleen <ak@muc.de>
To: Roland McGrath <roland@redhat.com>
Cc: Daniel Jacobowitz <dan@debian.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Cagney <cagney@redhat.com>
Subject: Re: More trouble with i386 EFLAGS and ptrace
Date: Mon, 07 Mar 2005 20:13:17 +0100 [thread overview]
Message-ID: <m1hdjnmfqq.fsf@muc.de> (raw)
In-Reply-To: <200503062122.j26LMP5F021846@magilla.sf.frob.com> (Roland McGrath's message of "Sun, 6 Mar 2005 13:22:25 -0800")
Roland McGrath <roland@redhat.com> writes:
>
> I note, btw, that the x86_64 code is still at that prior stage. So I think
> it doesn't have this new wrinkle, but it also doesn't have the advantages
> of the more recent i386 changes. Once we're sure about the i386 state, we
> should update the x86_64 code to match.
I have it fixed in my tree, but not pushed out yet because of lack of
testing.
In general I track all i386 changes that make sense for modern systems
and 64bit, but sometimes merging takes some time.
However given the flood of bugs in the i386 code I'm starting to have
doubts again if all these changes were really a good idea.
However x86-64 has to be bug-to-bug compatible to i386, so there
is not much choice.
-Andi
next prev parent reply other threads:[~2005-03-07 19:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 19:38 More trouble with i386 EFLAGS and ptrace Daniel Jacobowitz
2005-03-06 20:03 ` Linus Torvalds
2005-03-06 21:14 ` Daniel Jacobowitz
2005-03-07 0:46 ` Linus Torvalds
2005-03-06 21:22 ` Roland McGrath
2005-03-06 22:13 ` Daniel Jacobowitz
[not found] ` <200503070316.j273Gb4G027048@magilla.sf.frob.com>
2005-03-07 4:49 ` Daniel Jacobowitz
2005-03-07 21:29 ` Roland McGrath
2005-03-09 0:12 ` Daniel Jacobowitz
2005-03-13 8:27 ` Roland McGrath
2005-03-13 20:06 ` Daniel Jacobowitz
2005-03-07 19:13 ` Andi Kleen [this message]
2005-03-06 20:26 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2005-03-14 4:06 Jesse Allen
2005-03-14 4:12 Jesse Allen
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=m1hdjnmfqq.fsf@muc.de \
--to=ak@muc.de \
--cc=cagney@redhat.com \
--cc=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox