From: Phil Muldoon <pmuldoon@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: frysk-core/frysk proc/BankRegister.java proc/C ...
Date: Wed, 10 Oct 2007 06:49:00 -0000 [thread overview]
Message-ID: <470C75FD.3080803@redhat.com> (raw)
In-Reply-To: <470C4BC2.7000306@redhat.com>
Andrew Cagney wrote:
> Phil Muldoon wrote:
>> Andrew,
>>
>> I know this work is ongoing, so should I sit tight regarding the
>> FIXME notifications? I'm not sure how to fix the gpr registers
>> access. If it is work ongoing, I'll just wait until you give the
>> signal with an explanation regarding how a Task accesses it's own
>> registers.
>>
> The function to look at is Task.accessRegister(Register register,int
> offset, int length, byte[] buffer, int start, boolean write) which
> will does a direct/raw byte copy of the data into a buffer.
>
> However, yes, perhaps hold off a little until I've got all the
> register code in frysk.proc resolved.
> Andrew
>
Ok will do, will wait and see. As a rhetorical question, what is wrong
with task.getSomeRegisterFunctionName("eax") as a general helper
function? Why do I need to know (ptrace buffer?) offset and length to
access a register? Is this because register access is being move to the
task from the ISA? Just trying to get a sense of where this refactor is
going.
Regards
Phil
next prev parent reply other threads:[~2007-10-10 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071009194630.3523.qmail@sourceware.org>
2007-10-09 20:05 ` Phil Muldoon
2007-10-10 3:51 ` Andrew Cagney
2007-10-10 6:49 ` Phil Muldoon [this message]
2007-10-10 13:36 ` Andrew Cagney
2007-10-10 13:49 ` Phil Muldoon
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=470C75FD.3080803@redhat.com \
--to=pmuldoon@redhat.com \
--cc=cagney@redhat.com \
--cc=frysk@sourceware.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).