All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jocelyn Mayer <l_indien@magic.fr>
To: thayne@c2.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu linux-user/qemu.h linux-user/signal.c linu...
Date: Thu, 27 Sep 2007 18:41:51 +0200	[thread overview]
Message-ID: <1190911311.29748.12.camel@jma4.dev.netgem.com> (raw)
In-Reply-To: <1190908428.27143.7.camel@phantasm.home.enterpriseandprosperity.com>

On Thu, 2007-09-27 at 09:53 -0600, Thayne Harbaugh wrote:
> On Thu, 2007-09-27 at 16:08 +0200, Jocelyn Mayer wrote:
> > On Thu, 2007-09-27 at 13:57 +0000, Thiemo Seufer wrote:
> > > CVSROOT:	/sources/qemu
> > > Module name:	qemu
> > > Changes by:	Thiemo Seufer <ths>	07/09/27 13:57:58
> > > 
> > > Modified files:
> > > 	linux-user     : qemu.h signal.c syscall.c 
> > > 	target-alpha   : cpu.h 
> > > 	target-arm     : cpu.h 
> > > 	target-i386    : cpu.h 
> > > 	target-mips    : cpu.h 
> > > 	target-ppc     : cpu.h 
> > 
> >  static inline target_ulong get_sp_from_cpustate(CPUPPCState *state)
> > {
> >   return state->gpr[1];
> > }
> > 
> > This is no way related to CPU emulation then has nothing to do in cpu.h.
> > Furthermore, there no notion of sigaltstack or even stack pointer in the
> > PowerPC specification.
> > Revert this patch immediatly, please, and stop breaking others code...
> 
> My apologies.  I put get_sp_from_cpustate() in cpu.h because it is a
> generic function that isn't exclusive to sigaltstack().  If it's
> preferred it can be exclusive to sigaltstack().
> 
> > How should we say "don't do weird things in others code" ??? Again, and
> > again and again...
> 
> My hope was that these types of comments would be made prior to the
> patch being committed.  Is there a developer document that describes the
> intentions of code layout, design philosophy, etc. so that I'm not
> guessing?

Then, I'm sorry, I did not notice this when you submitted your patch.
And I even did not imagine that it could touch anything out of
linux-user. Please apologize, I've been reading your submission too
fast, not being directly interressed by the patch...

> Please send me additional comments so that I can rework the patch for
> resubmission.

I don't know in which header you should define those ABI specific stuff.
Maybe a header may be added in the linux-user target subdirectories for
those kind of definitions; it may help avoiding too many #ifdef
everywhere...

  reply	other threads:[~2007-09-27 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27 13:57 [Qemu-devel] qemu linux-user/qemu.h linux-user/signal.c linu Thiemo Seufer
2007-09-27 14:08 ` Jocelyn Mayer
2007-09-27 15:26   ` Thiemo Seufer
2007-09-27 15:53   ` Thayne Harbaugh
2007-09-27 16:41     ` Jocelyn Mayer [this message]
2007-09-27 16:47     ` Thiemo Seufer

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=1190911311.29748.12.camel@jma4.dev.netgem.com \
    --to=l_indien@magic.fr \
    --cc=qemu-devel@nongnu.org \
    --cc=thayne@c2.net \
    /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.