public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Rui <ray.huang@amd.com>
To: Borislav Petkov <bp@suse.de>
Cc: "Andy Lutomirski" <luto@amacapital.net>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"Len Brown" <lenb@kernel.org>,
	"John Stultz" <john.stultz@linaro.org>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"Fengguang Wu" <fengguang.wu@intel.com>,
	"Aaron Lu" <aaron.lu@intel.com>,
	"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
	"Li, Tony" <Tony.Li@amd.com>, "Xue, Ken" <Ken.Xue@amd.com>
Subject: Re: [PATCH v2 2/4] x86, mwaitt: make delay method configurable
Date: Tue, 9 Jun 2015 18:03:10 +0800	[thread overview]
Message-ID: <20150609100309.GB17030@hr-slim.amd.com> (raw)
In-Reply-To: <20150609090543.GA22105@pd.tnic>

On Tue, Jun 09, 2015 at 05:05:43PM +0800, Borislav Petkov wrote:
> On Tue, Jun 09, 2015 at 11:13:39AM +0800, Huang Rui wrote:
> > This patch introduces a kernel parameter (delay), user is able to configure
> > it at boot loader to choose different types of delay method.
> > 
> > Default schema is to use TSC delay. This update can be more flexiable to
> > add new delay method.
> > 
> > Suggested-by: Suravee Suthikulanit <suravee.suthikulpanit@amd.com>
> > Signed-off-by: Huang Rui <ray.huang@amd.com>
> > ---
> >  arch/x86/include/asm/delay.h |    7 +++++++
> >  arch/x86/kernel/setup.c      |   19 +++++++++++++++++++
> >  arch/x86/lib/delay.c         |   12 +++++++++++-
> >  3 files changed, 37 insertions(+), 1 deletion(-)
> > 
> > diff --git a/arch/x86/include/asm/delay.h b/arch/x86/include/asm/delay.h
> > index 9b3b4f2..99873ec 100644
> > --- a/arch/x86/include/asm/delay.h
> > +++ b/arch/x86/include/asm/delay.h
> > @@ -5,4 +5,11 @@
> >  
> >  void use_tsc_delay(void);
> >  
> > +extern unsigned long boot_option_delay;
> > +
> > +enum delay_type {
> > +	DELAY_LOOP=0,
> > +	DELAY_TSC,
> > +};
> > +
> >  #endif /* _ASM_X86_DELAY_H */
> > diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
> > index 0b10698..cc2886d 100644
> > --- a/arch/x86/kernel/setup.c
> > +++ b/arch/x86/kernel/setup.c
> > @@ -111,6 +111,7 @@
> >  #include <asm/mce.h>
> >  #include <asm/alternative.h>
> >  #include <asm/prom.h>
> > +#include <asm/delay.h>
> >  
> >  /*
> >   * max_low_pfn_mapped: highest direct mapped pfn under 4GB
> > @@ -844,6 +845,24 @@ dump_kernel_offset(struct notifier_block *self, unsigned long v, void *p)
> >  	return 0;
> >  }
> >  
> > +static int __init delay_setup(char *str)
> > +{
> > +	if (!str)
> > +		return -EINVAL;
> > +
> > +	if (!strcmp(str, "tsc")) {
> > +		pr_info("using tsc delay\n");
> > +		boot_option_delay = DELAY_TSC;
> > +	} else if (!strcmp(str, "loop")) {
> > +		pr_info("using loop delay\n");
> > +		boot_option_delay = DELAY_LOOP;
> > +	} else
> > +		return -1;
> 
> What Peter said.
> 
> And we did talk about this already in the last review. You guys want to
> drop all those kernel parameters and use MWAITX delay by default when:
> 
> 1. HW supports MWAITX
> 
> *and*
> 
> 2. delay fits in u32.
> 
> Kernel parameters is a bad bad idea.
> 

Sorry, I am suggested to make the mwaitx delay configurable firstly by
our guys...
Why do you think that method is bad?

Thanks,
Rui

  parent reply	other threads:[~2015-06-09 10:04 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09  3:13 [PATCH v2 0/4] x86, mwaitt: introduce AMD mwaitt support Huang Rui
2015-06-09  3:13 ` [PATCH v2 1/4] x86, mwaitt: add monitorx and mwaitx instruction Huang Rui
2015-06-09  8:23   ` Peter Zijlstra
2015-06-09  9:48     ` Huang Rui
2015-06-09 10:05       ` Borislav Petkov
2015-06-09 16:44         ` Andy Lutomirski
2015-06-09 17:06           ` Borislav Petkov
2015-06-10  2:40             ` Huang Rui
2015-06-09  3:13 ` [PATCH v2 2/4] x86, mwaitt: make delay method configurable Huang Rui
2015-06-09  9:05   ` Borislav Petkov
2015-06-09  9:31     ` Peter Zijlstra
2015-06-09 10:03     ` Huang Rui [this message]
2015-06-09 10:08       ` Peter Zijlstra
2015-06-09 10:15         ` Huang Rui
2015-06-09 10:08       ` Borislav Petkov
2015-06-09  3:13 ` [PATCH v2 3/4] x86, mwaitt: introduce mwaix delay with a configurable timer Huang Rui
2015-06-09  8:31   ` Peter Zijlstra
2015-06-09 10:10     ` Huang Rui
2015-06-09  9:29   ` Peter Zijlstra
2015-06-09 10:59     ` Huang Rui
2015-06-09 16:46     ` Andy Lutomirski
2015-06-09 17:13       ` Peter Zijlstra
2015-06-09 17:55         ` Andy Lutomirski
2015-06-09 18:43           ` Borislav Petkov
2015-06-09 18:55             ` Andy Lutomirski
2015-06-12  8:42       ` Borislav Petkov
2015-06-12 23:15         ` Andy Lutomirski
2015-06-13  8:48           ` Borislav Petkov
2015-06-09  3:13 ` [PATCH v2 4/4] x86, mwaitt: add documents of delay option Huang Rui

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=20150609100309.GB17030@hr-slim.amd.com \
    --to=ray.huang@amd.com \
    --cc=Ken.Xue@amd.com \
    --cc=Suravee.Suthikulpanit@amd.com \
    --cc=Tony.Li@amd.com \
    --cc=aaron.lu@intel.com \
    --cc=bp@suse.de \
    --cc=fengguang.wu@intel.com \
    --cc=fweisbec@gmail.com \
    --cc=john.stultz@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=x86@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