The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Willy Tarreau <willy@w.ods.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
	Herbert Rosmanith <kernel@wildsau.enemy.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.31 & latest binutils: asm-problems still there
Date: Sun, 5 Jun 2005 16:49:21 -0700	[thread overview]
Message-ID: <20050605234921.GA23960@lucon.org> (raw)
In-Reply-To: <20050605233459.GB28759@alpha.home.local>

On Mon, Jun 06, 2005 at 01:34:59AM +0200, Willy Tarreau wrote:
> On Sun, Jun 05, 2005 at 03:16:32PM -0300, Marcelo Tosatti wrote:
> > On Sat, Jun 04, 2005 at 05:29:31AM +0200, Herbert Rosmanith wrote:
> (...)
> > > alessandro suardi told me that this problem is solved using the
> > > patch from:
> > >   http://www.kernel.org/pub/linux/devel/binutils/linux-2.4-seg-4.patch
> > > 
> > > which are dated from march (2005-03-27) and therefore, about 3 months
> > > old.
> > > 
> > > it's about time this gets into the official kernel. who is in charge
> > > of it? (it's obviously not sufficient to report to lkml).
> > 
> > Looks OK except that one "movl" conversion was forgotten in 
> > the x86-64 diff:
> > 
> > @@ -609,7 +609,7 @@ struct task_struct *__switch_to(struct t
> >  	}
> >  	{
> >  		unsigned gsindex;
> > -		asm volatile("movl %%gs,%0" : "=g" (gsindex)); 
> > +		asm volatile("movl %%gs,%0" : "=r" (gsindex)); 
> >  		if (unlikely((gsindex | next->gsindex) || prev->gs)) {
> > 
> > Who wrote the patch? 
> 
> I believe it's H.J. Lu (CC'd).
> 

Is there a problem?


H.J.

      reply	other threads:[~2005-06-05 23:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-04  3:29 2.4.31 & latest binutils: asm-problems still there Herbert Rosmanith
2005-06-05 18:16 ` Marcelo Tosatti
2005-06-05 23:34   ` Willy Tarreau
2005-06-05 23:49     ` H. J. Lu [this message]

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=20050605234921.GA23960@lucon.org \
    --to=hjl@lucon.org \
    --cc=kernel@wildsau.enemy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=willy@w.ods.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