public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Tejun Heo <tj@kernel.org>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@amd.com>,
	"Richter, Robert" <robert.richter@amd.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	"Rosenfeld, Hans" <Hans.Rosenfeld@amd.com>,
	Alok N Kataria <akataria@vmware.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	"Hans J. Koch" <hjk@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Move llc_shared_map out of cpu_info
Date: Sat, 22 Jan 2011 11:14:03 +0100	[thread overview]
Message-ID: <20110122101403.GB23987@aftab> (raw)
In-Reply-To: <4D3A16E8.5020608@kernel.org>

On Fri, Jan 21, 2011 at 06:29:44PM -0500, Yinghai Lu wrote:
> 
> cpu_info is already with per_cpu, We can take llc_shared_map out of cpu_info,
> and declare it as per_cpu variable directly.
> 
> So later referencing could be simple and directly instead of diving to find
> cpu_info at first.
> 
> Also could make smp_store_cpu_info() much simple to avoid to do save and restore trick.
> 
> 
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>

Yep, it's only natural to do that.

Acked-by: Borislav Petkov <borislav.petkov@amd.com>

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2011-01-22 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-21 23:29 [PATCH] x86: Move llc_shared_map out of cpu_info Yinghai Lu
2011-01-22 10:14 ` Borislav Petkov [this message]
2011-01-26 10:59 ` [tip:x86/cpu] " tip-bot for Yinghai Lu

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=20110122101403.GB23987@aftab \
    --to=bp@amd64.org \
    --cc=Andreas.Herrmann3@amd.com \
    --cc=Hans.Rosenfeld@amd.com \
    --cc=akataria@vmware.com \
    --cc=hjk@linutronix.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=robert.richter@amd.com \
    --cc=shemminger@vyatta.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=yinghai@kernel.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