public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Kevin O'Connor" <kevin@koconnor.net>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Stefan Reinauer <stepan@coresystems.de>,
	linux-kernel@vger.kernel.org, coreboot@coreboot.org
Subject: Re: [PATCH] x86: ioremap mptable -v2
Date: Mon, 02 Mar 2009 12:46:23 -0800	[thread overview]
Message-ID: <49AC459F.10606@kernel.org> (raw)
In-Reply-To: <20090302202918.GA14471@elte.hu>

Ingo Molnar wrote:
> * Yinghai Lu <yinghai@kernel.org> wrote:
> 
>> V3: according to Ingo, seperate get_mpc_size()
> 
> No, that was not my suggestion. My suggestion was to separate 
> this whole 'else if' branch:
> 
>>  	} else if (mpf->physptr) {
>> +		struct mpc_table *mpc;
>> +		unsigned long size;
>>  
>> +		size = get_mpc_size(mpf->physptr);
>> +		mpc = early_ioremap(mpf->physptr, size);
>>  		/*
>>  		 * Read the physical hardware table.  Anything here will
>>  		 * override the defaults.
>>  		 */
>> -		if (!smp_read_mpc(phys_to_virt(mpf->physptr), early)) {
>> +		if (!smp_read_mpc(mpc, early)) {
>>  #ifdef CONFIG_X86_LOCAL_APIC
>>  			smp_found_config = 0;
>>  #endif
> 
> ... into a helper function - if that improves the code.
oh, i missed it
> Your patch does early_ioremap, iounmap then ioremap and iounmap - 
> quite pointlessly.
try to get exact mpc size.
> 
> You should resist cleanup suggestions that make the code worse, 
> even if it comes from a maintainer :-)

we could do that later. to make __get_smp_config smaller and readable.

YH

  reply	other threads:[~2009-03-02 20:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <499DB40C.1060205@coresystems.de>
     [not found] ` <499DB480.1000909@coresystems.de>
     [not found]   ` <499DB6D8.5040706@coresystems.de>
     [not found]     ` <499DBDA0.2010606@coresystems.de>
     [not found]       ` <499DCE79.8020809@coresystems.de>
2009-02-22 15:25         ` MPTable can not be high-memory on Linux Kevin O'Connor
2009-02-22 17:06           ` Rafael J. Wysocki
2009-02-22 21:33             ` Yinghai Lu
2009-02-22 22:32               ` Kevin O'Connor
2009-02-22 22:58                 ` Ingo Molnar
2009-02-23  6:14                   ` Yinghai Lu
2009-02-23  6:42                     ` Ingo Molnar
2009-02-28 23:41                     ` Kevin O'Connor
2009-03-01  3:10                       ` Yinghai Lu
2009-03-01 18:04                         ` Kevin O'Connor
2009-03-02  3:23                           ` [PATCH] x86: ioremap mptable -v2 Yinghai Lu
2009-03-02 10:18                             ` Ingo Molnar
2009-03-02 10:19                               ` Ingo Molnar
2009-03-02 20:07                               ` Yinghai Lu
2009-03-02 20:29                                 ` Ingo Molnar
2009-03-02 20:46                                   ` Yinghai Lu [this message]
2009-03-02 20:57                                     ` Ingo Molnar
2009-02-22 17:53           ` MPTable can not be high-memory on Linux Andi Kleen

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=49AC459F.10606@kernel.org \
    --to=yinghai@kernel.org \
    --cc=coreboot@coreboot.org \
    --cc=kevin@koconnor.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=stepan@coresystems.de \
    /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