Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of nikolay.kuznetsov@gmail.com
 designates 66.249.92.168 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=n9jL4RhT1vMdWYRlJqtjb/b5hJhMB+da8Pm93QygrR8jSezwYoBaycDVmgRgUIqTHH5H0r28HtSKcc2RO3FC9xwZqTd4VNbSny/o2y4JbNyuNYbUaIIf2bhKO70zTUTHXZuBwQeRTD6NHVrr4CTcTZeaZAUxXsuEBvtP46J8aAQ=
Message-ID: <8ce6aa550610300642y2e911b6eh91ea9ecdde3b8c9c@mail.gmail.com>
Date: Mon, 30 Oct 2006 18:42:21 +0400
From: "Nikolay Kuznetsov" <nikolay.kuznetsov@gmail.com>
To: harmony-dev@incubator.apache.org
Subject: Re: [drlvm] what's the difference between the structure VM_thread and
 HyThread?
In-Reply-To: <005a01c6fc30$a17c1050$2700030a@ictbfan>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <005001c6fc20$927c98f0$2700030a@ictbfan>
	 <8ce6aa550610300513p1159f684w466c26288f36e29c@mail.gmail.com>
	 <005a01c6fc30$a17c1050$2700030a@ictbfan>

Yes, this data is non threading and separate fields of VM_thread
structure should be replaced with independent values (data structures)
stored in TLS under separate keys.

Nik.

On 10/30/06, Fan Bin <fanbin23@gmail.com> wrote:
> Thanks,  so you mean that there is only non threading data currently in VM_thread block, and maybe the VM_thread block will be replaced by TLS in HyThread, right?
>
> Bin
>
> ----- Original Message -----
> From: "Nikolay Kuznetsov" <nikolay.kuznetsov@gmail.com>
> To: <harmony-dev@incubator.apache.org>
> Sent: Monday, October 30, 2006 9:13 PM
> Subject: Re: [drlvm] what's the difference between the structure VM_thread and HyThread?
>
>
> > Hello,
> >
> > this is legacy thread structure. You're right, there was no HyThread
> > at first, but VM_thread structure. Also different DRLVM modules used
> > to have dedicated fields in this structure. Further it was decided to
> > make threading module independent and make usage model of threading
> > module the same for all other modules(i.e use thread local storage for
> > module specific data). But since VM_thread structure usage was very
> > heavy it was also decided to leave all non threading data in VM_thread
> > and put it in TLS till better times (I mean, till this data will be
> > divided into module depended parts and also put into TLS under
> > different keys).
> >
> > Nik.
> >
> > On 10/30/06, Fan Bin <fanbin23@gmail.com> wrote:
> >> Hi all,
> >>
> >> I'm now reading the lastest version of drlvm. Now I have a question about the thread management module. I see that there are three kinds of control blocks: HyThread, JVMTIThread and VM_thread. What's the difference of their rols? Especially HyThread and VM_thread. As far as I know, there is no HyThread at first.
> >>
> >> Thanks,
> >> Fan Bin