Hey all,
FYI, I've finished most part of the patch, but wish it can be tested a bit more
before I submit it to the repository. Since there are some deadlines coming, I
hope submitting it in late Aug or early Sept won't bother you much?
Thanks!
Jiayuan
> Date: Sat, 12 Jul 2008 10:29:17 -0700
> From: [EMAIL PROTECTED]
> To: m5-dev@m5sim.org
> Subject: Re: [m5-dev] submit patches: Mesh2D, directory coherence, and
> multithreading
>
> No, please base your patches on m5 (the development repo) rather than
> m5-stable, as that's where we'll want to integrate them.
>
> Thanks,
>
> Steve
>
> 2008/7/12 jiayuan meng <[EMAIL PROTECTED]>:
> > I'm going to pull the repository of m5_stable and base my patches upon this
> > version, will that be fine?
> >
> >
> > ________________________________
> >> Date: Fri, 11 Jul 2008 16:50:19 -0700
> >> From: [EMAIL PROTECTED]
> >> To: m5-dev@m5sim.org
> >> Subject: Re: [m5-dev] submit patches: Mesh2D, directory coherence, and
> >> multithreading
> >>
> >> Wow, that's fantastic. The best thing you can do is get your code
> >> working with the new repository using mercurial and mercurial queues.
> >> If you do that, then we can work with you to make sure that the code
> >> meets all of the requirements (doesn't break things, is reasonably
> >> organized, meets the style guidelines, etc.)
> >>
> >> Did you use a revision control system as you did your work?
> >>
> >> Thanks,
> >> Nate
> >>
> >> 2008/7/11 jiayuan meng <[EMAIL PROTECTED]>:
> >> > Dear all,
> >> >
> >> > I appreciate all your support to help me with M5. I really love it. I'm
> >> > a graduate student working with Prof. Kevin Skadron at University of
> >> > Virginia. And now,
> >> > I'd like to submit patches to M5 that enables it to simulate CMP
> >> > architecture.
> >> >
> >> > I have a mesh2D model that works well with an MSI directory coherence
> >> > protocol.
> >> > Both the interconnection and directory coherence models are extendable.
> >> > Another patch is to support multithreading for simple CPUs. The cpu can
> >> > switch to another HW thread context if it has a data access.
> >> >
> >> > However, atomic modes are not well tested. And I haven't considered
> >> > checkpoints.
> >> >
> >> > The mercurial patches are based on changeset 5291:456a50cf2a67, a
> >> > version
> >> > after 2.0beta4 but before 2.0beta5.
> >> > As an "external developer", how do you think I should submit the
> >> > patches? An
> >> > do you think it would be necessary to update the patches so they are
> >> > based
> >> > on a more recent changeset?
> >> > If so, which changeset?
> >> >
> >> > Just hope it might be useful.
> >> >
> >> > Thanks!
> >> >
> >> > Jiayuan Meng
> >> >
> >> > ________________________________
> >> > Need to know now? Get instant answers with Windows Live Messenger. IM on
> >> > your terms.
> >> > _______________________________________________
> >> > m5-dev mailing list
> >> > m5-dev@m5sim.org
> >> > http://m5sim.org/mailman/listinfo/m5-dev
> >> >
> >> >
> >> _______________________________________________
> >> m5-dev mailing list
> >> m5-dev@m5sim.org
> >> http://m5sim.org/mailman/listinfo/m5-dev
> >
> > ________________________________
> > It's a talkathon – but it's not just talk. Check out the i'm Talkathon.
> > _______________________________________________
> > m5-dev mailing list
> > m5-dev@m5sim.org
> > http://m5sim.org/mailman/listinfo/m5-dev
> >
> >
> _______________________________________________
> m5-dev mailing list
> m5-dev@m5sim.org
> http://m5sim.org/mailman/listinfo/m5-dev
_________________________________________________________________
Time for vacation? WIN what you need- enter now!
http://www.gowindowslive.com/summergiveaway/?ocid=tag_jlyhm
_______________________________________________
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
