All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Roland McGrath <roland@redhat.com>
Cc: akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org,
	jparadis@redhat.com, cagney@redhat.com, discuss@x86-64.org
Subject: Re: [PATCH] x86-64 singlestep through sigreturn system call
Date: Fri, 16 Jul 2004 00:06:18 +0200	[thread overview]
Message-ID: <20040716000618.0441d268.ak@suse.de> (raw)
In-Reply-To: <200407152113.i6FLDFfB013246@magilla.sf.frob.com>

On Thu, 15 Jul 2004 14:13:15 -0700
Roland McGrath <roland@redhat.com> wrote:

> > Anyways, I don't have any plans to change the 64bit behaviour. gdb will
> > have to live with a few minor inconsistencies as price for faster system
> > calls. 
> 
> My patch doesn't slow anything down beyond one comparison and branch not
> taken in the rt_sigreturn system call.  Does that negligible meaning of
> "faster" really warrant the inconsistent user behavior?

I meant as a general side effect of using SYSRET and not always IRET.
In the later case it would be consistently like i386.

Anyways, even if I applied your patch there would be still inconsistency
because there are several other system calls that use IRET. So I don't
see much advantage in adding a special case just for sigreturn.

-Andi

  reply	other threads:[~2004-07-15 22:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13  0:22 [PATCH] x86-64 singlestep through sigreturn system call Roland McGrath
2004-07-13  7:23 ` Andi Kleen
2004-07-15  0:56   ` Roland McGrath
2004-07-15  5:46     ` Andi Kleen
2004-07-15 21:13       ` Roland McGrath
2004-07-15 22:06         ` Andi Kleen [this message]
2004-07-15 23:57           ` Roland McGrath
     [not found] <2imAA-4n7-49@gated-at.bofh.it>
     [not found] ` <2iosE-5Kb-17@gated-at.bofh.it>
2004-07-17 11:12   ` Andi Kleen
2004-07-22  2:16     ` Roland McGrath
2004-07-22  6:11       ` Andrew Morton
2004-07-22 22:58         ` Roland McGrath

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=20040716000618.0441d268.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=cagney@redhat.com \
    --cc=discuss@x86-64.org \
    --cc=jparadis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=torvalds@osdl.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.