virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andrew Morton <akpm@osdl.org>,
	virtualization <virtualization@lists.osdl.org>,
	Ingo Molnar <mingo@elte.hu>,
	James.Bottomley@steeleye.com, Andi Kleen <ak@muc.de>
Subject: Re: Per-cpu patches on top of PDA stuff...
Date: Wed, 20 Sep 2006 10:07:02 +1000	[thread overview]
Message-ID: <1158710822.2480.14.camel@localhost.localdomain> (raw)
In-Reply-To: <450FA6FB.9020100@goop.org>

On Tue, 2006-09-19 at 01:14 -0700, Jeremy Fitzhardinge wrote:
> Rusty Russell wrote:
> > 	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 current mechanism was specifically introduced by James Bottomley a 
> while back; I guess to deal with Voyager strangeness.

(James CC'd).  I dislike the gratuitous copy: we have three gdts, the
boot GDT, the master GDT (cpu_gdt_table), then the per-cpu GDT.  Using
the per-cpu mechanisms already in place makes it simple, avoids manual
allocation, and the extra master GDT.  The extra GDT is particularly
embarrassing on UP, which doesn't want a per-cpu GDT anyway...

Seems that we can't assume boot CPU == 0.  I think I've removed the two
places where I assumed that, but will need testing.

> Hm, now is not really a good time.  I'm still trying to get Xen 
> basically working, and the percpu PDA stuff isn't really necessary for 
> that.  The PDA stuff was enough of a problem in itself...
> 
> Also, the PDA patches are in -mm, so that's probably a better base for 
> your patches.

Yes, it turned out to be easier to go straight to -mm anyway.  I'll redo
them as Andi requested....

Rusty.
-- 
Help! Save Australia from the worst of the DMCA: http://linux.org.au/law

  parent reply	other threads:[~2006-09-20  0:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19  3:13 Per-cpu patches on top of PDA stuff Rusty Russell
2006-09-19  8:03 ` 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 [this message]
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=1158710822.2480.14.camel@localhost.localdomain \
    --to=rusty@rustcorp.com.au \
    --cc=James.Bottomley@steeleye.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).