From: "Tyler BIRD" <birdty@uvsc.edu>
To: <aneesh.kumar@digital.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Alpha - how to fill the PC
Date: Sun, 16 Dec 2001 12:47:37 -0700 [thread overview]
Message-ID: <sc1c97f4.074@mail-smtp.uvsc.edu> (raw)
One thing I thought of is the process on lets say node2 have exactly the same
address space as on node 1 when it is migrated. You could be trying to return from a syscall
to an address space of a process that doesn't exist on the node or hasn't migrated yet.
Just a thought
>>> "Aneesh Kumar K.V" <aneesh.kumar@digital.com> 12/16/01 06:19AM >>>
Hi,
I am trying to do process migration between nodes using alpha
architecture. For explaining what is happening I will take the process
getting migrated from node1 to node2. I am using struct pt_regs for
rebuilding the process on node2.I am getting the same value of struct
pt_regs on node1 and on node2 ( I print is using dik_show_regs) Now I
want to set the value of registers including the program counter with
the value i got from node1. Right now I am doing
ret_from_sys_call(®s). But then i am getting a Oops . The Oops
message contain all the register values same as that I got from node1
except pc and ra
Any idea where I went wrong ?
-aneesh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-12-16 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 19:47 Tyler BIRD [this message]
[not found] <sc1c97f4.073@mail-smtp.uvsc.edu>
2001-12-17 4:03 ` Alpha - how to fill the PC Aneesh Kumar K.V
-- strict thread matches above, loose matches on Subject: below --
2001-12-16 13:19 Aneesh Kumar K.V
2001-12-28 23:59 ` Richard Henderson
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=sc1c97f4.074@mail-smtp.uvsc.edu \
--to=birdty@uvsc.edu \
--cc=aneesh.kumar@digital.com \
--cc=linux-kernel@vger.kernel.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.