linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>,
	Len Brown <lenb@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>, X86 ML <x86@kernel.org>,
	Linux PM list <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 0/1] speeding up cpu_up()
Date: Tue, 5 May 2015 09:15:11 +0200	[thread overview]
Message-ID: <20150505071510.GA3910@pd.tnic> (raw)
In-Reply-To: <5547F67D.2080307@amd.com>

On Mon, May 04, 2015 at 05:45:17PM -0500, Aravind Gopalakrishnan wrote:
> Tested a delay of 0 on Fam10h and Fam15h Model 30h-3fh and both work fine.

Cool, thanks for testing.

> Feedback from asking internally about this is that we should be OK to move
> to a no-delay default from K8 onwards.

Also cool :-)

@Len: So everything with X86_VENDOR_AMD and c->x86 >= 0xf should be fine.

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

      reply	other threads:[~2015-05-05  7:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19  0:53 [PATCH 0/1] speeding up cpu_up() Len Brown
2015-04-19  0:53 ` [PATCH 1/1] x86: replace cpu_up hard-coded mdelay with variable Len Brown
2015-04-20  7:13   ` Ingo Molnar
2015-04-20 12:37     ` Brown, Len
2015-04-20 17:45       ` Ingo Molnar
2015-04-22  5:40   ` Paul Gortmaker
2015-04-22  6:07     ` Ingo Molnar
2015-05-01 21:02       ` Len Brown
2015-04-20  7:15 ` [PATCH 0/1] speeding up cpu_up() Ingo Molnar
2015-05-01 21:42   ` Len Brown
2015-05-01 22:47     ` Borislav Petkov
2015-05-02  0:42       ` Aravind Gopalakrishnan
2015-05-03 16:13         ` Aravind Gopalakrishnan
2015-05-04 22:45           ` Aravind Gopalakrishnan
2015-05-05  7:15             ` Borislav Petkov [this message]

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=20150505071510.GA3910@pd.tnic \
    --to=bp@alien8.de \
    --cc=aravind.gopalakrishnan@amd.com \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).