public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: frysk-core/frysk proc/BankRegister.java proc/C ...
Date: Wed, 10 Oct 2007 13:36:00 -0000	[thread overview]
Message-ID: <470CD4FD.90202@redhat.com> (raw)
In-Reply-To: <470C75FD.3080803@redhat.com>

Phil Muldoon wrote:
> 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?

The only place where a String->Register lookup (e.g., "eax" -> 
frysk.isa.IA32Registers.EAX) is needed is in the expression evaluator 
where it interprets << $eax >>.  Every where else constant object, such 
as frysk.isa.IA32Registers.EAX can be used: these objects are efficient 
(better with HashMap) and second having defined constants prevents typos 
such as a register being called "foo" in one place and "fos" in a second.

> 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.
>

I'm not sure what you mean, the offset/length are for within the 
specified register, and start is an offset into the byte buffer.  Two 
things change: tThe code that implements register accesses isn't being 
moved to the task; but the way to access registers is now simpler, contrast:
    Task.getRegister(IA32Register.XIP)
with:
    Task.getIsa().getBankRegister("xip").getRegister(task)
the internals, though cleaned up will still be very similar.

Andrew


> Regards
>
> Phil
>

  reply	other threads:[~2007-10-10 13:36 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
2007-10-10 13:36       ` Andrew Cagney [this message]
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=470CD4FD.90202@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).