From: Elizeu Santos-Neto <elizeu@cs.uchicago.edu>
To: xen-devel@lists.xensource.com
Subject: Re: Patch question (Hyper-Threading support)
Date: Mon, 27 Mar 2006 18:52:19 -0600 [thread overview]
Message-ID: <1143507139.7733.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20060324191540.1306291c.tfreeman@mcs.anl.gov>
Hi all,
Well, based on some quick inspections on the that I checked out from
the mercurial repository this afternoon, it seems that the HT support
has been already implemented. :-)
Thus, here is a suggestion, it would be nice to make more details
available about who is doing what and in which phase of development
things are, this information could avoid duplicated efforts.
Thanks,
Eli
On Fri, 2006-03-24 at 19:15 -0600, Tim Freeman wrote:
> On Fri, 24 Mar 2006 13:30:18 -0600
> Elizeu Santos-Neto <elizeu@cs.uchicago.edu> wrote:
>
> >
> > Hi community,
> >
> > I've been working on modifying Xen and the Xen-Linux kernel to make
> > vCPU better represent Hyper-Threading physical CPUs, as I mentioned in a
> > previous post.
> >
> > http://lists.xensource.com/archives/html/xen-devel/2006-01/msg00853.html
> >
> > I produced some performance measurements and patches that might be
> > useful for some Hyper-Threading friendly workloads running on Xen. I'll
> > make the performance measurement report available soon.
> >
> > Basically, the modified files were:
> >
> > xen/common/domain.c
> > xen/common/sched_bvt.c
> > xen/common/sched_sedf.c
> > xen/common/schedule.c
> > xen/include/public/vcpu.h
> > xen/include/xen/sched.h
> > xen/arch/x86/smpboot.c
> >
> > How should I proceed to send the patch?
>
>
> There is a guide here:
>
> http://wiki.xensource.com/xenwiki/SubmittingXenPatches
>
> For examples, see:
>
> http://lists.xensource.com/archives/html/xen-devel/
>
> Also see these guidelines:
>
> http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
> http://linux.yyz.us/patch-format.html
>
> I would think replying to your patch email with the performance measurement
> report would help keep them together for people.
>
> Tim
>
>
>
next prev parent reply other threads:[~2006-03-28 0:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 19:30 Patch question (Hyper-Threading support) Elizeu Santos-Neto
2006-03-25 1:15 ` Tim Freeman
2006-03-25 8:52 ` Elizeu Santos-Neto
2006-03-28 0:52 ` Elizeu Santos-Neto [this message]
2006-03-28 7:32 ` Keir Fraser
2006-03-28 8:28 ` Elizeu Santos-Neto
2006-03-28 8:55 ` Keir Fraser
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=1143507139.7733.10.camel@localhost.localdomain \
--to=elizeu@cs.uchicago.edu \
--cc=xen-devel@lists.xensource.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 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.