mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: rohitseth@google.com
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH]x86_64: moving phys_proc_id and cpu_core_id to cpuinfo_x86
Date: Wed, 24 May 2006 01:21:39 +0200	[thread overview]
Message-ID: <200605240121.39667.ak@suse.de> (raw)
In-Reply-To: <1148424226.5959.18.camel@galaxy.corp.google.com>

On Wednesday 24 May 2006 00:43, Rohit Seth wrote:
> 
> Most of the fields of cpuinfo are defined in cpuinfo_x86 structure.
> This patch moves the phys_proc_id and cpu_core_id for each processor to
> cpuinfo_x86 structure as well.

Added thanks. At some point it'll probably change again because
I hope to eventually move cpuinfo into the x86-64 PDA, but not right now.

For symmetry it might be a good idea to do a similar patch for i386 too.

-Andi

  reply	other threads:[~2006-05-23 23:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23 22:43 Rohit Seth
2006-05-23 23:21 ` Andi Kleen [this message]
2006-05-23 23:25   ` Rohit Seth

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=200605240121.39667.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rohitseth@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome