From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>,
virtualization <virtualization@lists.osdl.org>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
Ingo Molnar <mingo@elte.hu>
Subject: Per-cpu patches on top of PDA stuff...
Date: Tue, 19 Sep 2006 13:13:37 +1000 [thread overview]
Message-ID: <1158635617.21726.8.camel@localhost.localdomain> (raw)
Hi Jeremy, all,
Sorry this took so long, spent last week in Japan at OSDL conf then
netconf. After several false starts, I ended up with a very simple
implementation, which clashes significantly with your work since then
8(. I've pushed the patches anyway, but it's going to be significant
work for me to re-merge them, so I wanted your feedback first.
The first patch simply changes the GDTs to be a straight per-cpu
variable. I notice that you did a similar thing with your patches, but
this is simpler and avoids wasting space in the UP case. It's a bit
tricky since we've never referred to per-cpu vars from asm before, but
since we're only referring to the pre-setup versions, it's ok.
The second patch changes gs to be the per-cpu offset, and by
implication, avoids using it altogether on UP. This avoids a special
"pda" structure, instead allowing all per-cpu variables to be accessed
this way. It avoids __thread, which I gave up after creating a horribly
complicated patch which still didn't quite work, and was no more
efficient if we want the kernel to run under Xen anyway.
I really think this is the way to go, and I'll start work on merging
now.
Cheers!
Rusty.
--
Help! Save Australia from the worst of the DMCA: http://linux.org.au/law
next reply other threads:[~2006-09-19 3:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 3:13 Rusty Russell [this message]
2006-09-19 8:03 ` Per-cpu patches on top of PDA stuff Rusty Russell
2006-09-19 8:26 ` Andi Kleen
2006-09-19 20:39 ` Jeremy Fitzhardinge
2006-09-19 8:14 ` Jeremy Fitzhardinge
2006-09-19 21:03 ` Chris Wright
2006-09-19 22:36 ` Jeremy Fitzhardinge
2006-09-20 0:07 ` Rusty Russell
2006-09-20 7:00 ` Andi Kleen
2006-09-20 12:54 ` James Bottomley
2006-09-20 16:09 ` Andi Kleen
2006-09-20 16:15 ` James Bottomley
2006-09-20 16:22 ` Andi Kleen
2006-09-20 16:42 ` James Bottomley
2006-09-20 17:49 ` Andi Kleen
2006-09-20 18:10 ` James Bottomley
2006-09-20 18:42 ` Andi Kleen
2006-09-21 8:54 ` Rusty Russell
2006-09-19 20:37 ` Chris Wright
2006-09-19 20:40 ` Jeremy Fitzhardinge
2006-09-19 21:08 ` Chris Wright
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=1158635617.21726.8.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=jeremy@goop.org \
--cc=mingo@elte.hu \
--cc=virtualization@lists.osdl.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.