From: Pau Aliagas <linuxnow@newtral.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: "H. J. Lu" <hjl@lucon.org>, Andi Kleen <ak@muc.de>,
binutils@sources.redhat.com
Subject: Re: i386/x86_64 segment register issuses (Re: PATCH: Fix x86 segment register access)
Date: Thu, 31 Mar 2005 15:05:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.62.0503310253180.7060@pau.intranet.ct> (raw)
In-Reply-To: <20050331003437.GB19573@lucon.org>
On Wed, 30 Mar 2005, H. J. Lu wrote:
>>> That is what the assembler generates, and should have generated, for
>>> "movw %ds,(%eax)" since Nov. 4, 2004.
>>
>> Could this be the reason for the reported slowdown in the last six months?
>
> Can you elaborate?
There's an unexplained slowdown of kernel 2.6 detailed in this thread:
http://kerneltrap.org/node/4940
I don't want at all to justify it with the change you talk about in gas,
but maybe it is worth to check if it has anything to do with it. The
slowdown happened in this last six months.
--
Pau
next prev parent reply other threads:[~2005-03-31 0:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 23:31 PATCH: Fix x86 segment register access H. J. Lu
2005-03-28 10:21 ` i386/x86_64 segment register issuses (Re: PATCH: Fix x86 segment register access) H. J. Lu
2005-03-30 9:46 ` PATCH: i386/x86_64 segment register access update H. J. Lu
[not found] ` <m14qev3h8l.fsf@muc.de>
[not found] ` <Pine.LNX.4.58.0503291618520.6036@ppc970.osdl.org>
[not found] ` <20050330015312.GA27309@lucon.org>
[not found] ` <Pine.LNX.4.58.0503291815570.6036@ppc970.osdl.org>
[not found] ` <20050330040017.GA29523@lucon.org>
2005-03-30 22:19 ` i386/x86_64 segment register issuses (Re: PATCH: Fix x86 segment register access) Linus Torvalds
2005-03-30 23:24 ` linux-os
2005-03-31 12:00 ` H. J. Lu
2005-03-31 8:55 ` H. J. Lu
2005-03-31 13:27 ` Pau Aliagas
2005-03-31 15:05 ` H. J. Lu
2005-03-31 15:05 ` Pau Aliagas [this message]
2005-03-31 15:07 ` H. J. Lu
2005-03-31 15:37 ` Andi Kleen
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=Pine.LNX.4.62.0503310253180.7060@pau.intranet.ct \
--to=linuxnow@newtral.org \
--cc=ak@muc.de \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).