All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Chris Wright <chrisw@osdl.org>,
	Zwane Mwaikambo <zwane@arm.linux.org.uk>,
	zach@vmware.com, akpm@osdl.org, chrisl@vmware.com,
	Keir.Fraser@cl.cam.ac.uk, linux-kernel@vger.kernel.org,
	m+Ian.Pratt@cl.cam.ac.uk, mbligh@mbligh.org, pratap@vmware.com,
	virtualization@lists.osdl.org
Subject: Re: [PATCH 8/14] i386 / Add a per cpu gdt accessor
Date: Wed, 10 Aug 2005 22:54:53 -0700	[thread overview]
Message-ID: <20050811055453.GV7762@shell0.pdx.osdl.net> (raw)
In-Reply-To: <42FAE59F.8070009@zytor.com>

* H. Peter Anvin (hpa@zytor.com) wrote:
> Chris Wright wrote:
> >* Zwane Mwaikambo (zwane@arm.linux.org.uk) wrote:
> >>On Wed, 10 Aug 2005 zach@vmware.com wrote:
> >>>Add an accessor function for getting the per-CPU gdt.  Callee must 
> >>>already
> >>>have the CPU.
> >>
> >>This one seems superfluous to me, does accessing it indirectly generate 
> >>better code too?
> >
> >It's prepratory for other work.
> 
> I am assuming it has no change on the code, right?  (If it does, 
> something is wrong...)

That's correct, should be no change.

thanks,
-chris

  reply	other threads:[~2005-08-11  5:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11  4:56 [PATCH 8/14] i386 / Add a per cpu gdt accessor zach
2005-08-11  5:45 ` Zwane Mwaikambo
2005-08-11  5:40   ` Chris Wright
2005-08-11  5:43     ` H. Peter Anvin
2005-08-11  5:54       ` Chris Wright [this message]
2005-08-11  5:53   ` Zachary Amsden
2005-08-11  6:06     ` Zwane Mwaikambo
2005-08-16 23:47 ` Andi Kleen
2005-08-16 23:49   ` H. Peter Anvin
2005-08-17  0:07   ` Chris Wright
2005-08-17  0:16     ` Andi Kleen
2005-08-17  0:24       ` 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=20050811055453.GV7762@shell0.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=akpm@osdl.org \
    --cc=chrisl@vmware.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=mbligh@mbligh.org \
    --cc=pratap@vmware.com \
    --cc=virtualization@lists.osdl.org \
    --cc=zach@vmware.com \
    --cc=zwane@arm.linux.org.uk \
    /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.