Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] gdbserver fetch/store registers problem on s390x
Date: Wed, 13 Jul 2005 12:03:00 -0000	[thread overview]
Message-ID: <OF8EC0F8E2.F28CDFAE-ON4225703D.00404BA1-4225703D.00410806@de.ibm.com> (raw)
In-Reply-To: <20050713013548.GA17999@nevyn.them.org>

Hi Daniel,

> When you access the acrs, it looks like we are actually peeking/poking
> two of them at once.  I didn't see any sign of the "rest must be
> zeroed" you mentioned.  Is this in code not currently contributed to
> kernel.org?

OK, this only applies to the FPC register.  For the ACRs we're indeed
always transferring two at the same time, except when trying to read
the last one (%a15), in which case we get zeros in the low word on
peeking, and on poking the low word is ignored.

> In the current code the ACR we want to be poking at is the
> low-memory-address end of the buffer, i.e. leftmost in a big endian
> system (which all supported s390 appears to be).  Is that right?

Yes, that's correct.

> This is unfortunate... it means I need another target knob, since the
> PPC64 FPSCR is definitively in the rightmost 32 bits of the ptrace
> xfer.

Hmm ...


Mit freundlichen Gruessen / Best Regards

Ulrich Weigand

--
  Dr. Ulrich Weigand
  Linux for S/390 Design & Development
  IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032 Boeblingen
  Phone: +49-7031/16-3727   ---   Email: Ulrich.Weigand@de.ibm.com


      reply	other threads:[~2005-07-13 12:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10 19:48 Ulrich Weigand
2005-05-15 19:39 ` Daniel Jacobowitz
2005-07-13  1:35 ` Daniel Jacobowitz
2005-07-13 12:03   ` Ulrich Weigand [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=OF8EC0F8E2.F28CDFAE-ON4225703D.00404BA1-4225703D.00410806@de.ibm.com \
    --to=ulrich.weigand@de.ibm.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.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