public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Robert Richter <robert.richter@amd.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/10] x86, xsave: some code cleanups and reworks
Date: Wed, 21 Jul 2010 21:37:23 +0400	[thread overview]
Message-ID: <20100721173723.GG8009@lenovo> (raw)
In-Reply-To: <20100721172428.GS26154@erda.amd.com>

On Wed, Jul 21, 2010 at 07:24:28PM +0200, Robert Richter wrote:
> On 21.07.10 13:17:18, Cyrill Gorcunov wrote:
> > On Wed, Jul 21, 2010 at 10:11:56AM -0700, H. Peter Anvin wrote:
> > > On 07/21/2010 10:01 AM, Cyrill Gorcunov wrote:
> > > > 
> > > > Peter, also I think such tuning must be done at merge window time only,
> > > > just to not break other's patch queues.
> > > > 
> > > 
> > > Realistically it should be done right after the merge window for the
> > > *next* merge window.
> > > 
> > > 	-hpa
> > >
> > 
> > ok, which means Robert should use old conventional test at the moment
> > instead of introducing is_boot_cpu I suppose.
> 
> Yes, I am just using:
> 
> if (!smp_processor_id())
> 	...

ok, I see

> 
> Cyrill, if you like, I will leave it up to you to introduce the
> is_boot_cpu() macro.

ok Robert, I may handle it, notes below

> 
> I still have patch 7/7 in my new posting in that removes the
> boot_cpu_id. If your patch comes soon this will be obsolete as all
> places will have the macro then.
> 

I guess I can make it in a hour or so (since need to check all possible
places) but it might break other's queue I fear. That is why hpa noted
such things should go after merge window.

So I don't know Robert what would be preferred. If Peter pick up your
patch for now -- I may just keep it somewhere localy to not loose the traces of
boot_cpu_id and use this patch as helper. I just fear I can forget
about this promise to introduce is_boot_cpu helper later ;)

Another option could be -- introduce it now and send to trivial@ ML
so it'll be picked up there and pushed upstream after merge window.

> Thanks,
> 
> -Robert
> 
> -- 
> Advanced Micro Devices, Inc.
> Operating System Research Center
> 
	-- Cyrill

  reply	other threads:[~2010-07-21 17:37 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 18:50 [PATCH 00/10] x86, xsave: some code cleanups and reworks Robert Richter
2010-07-20 18:50 ` [PATCH 01/10] x86, xsave: do not include asm/i387.h in asm/xsave.h Robert Richter
2010-07-20 21:46   ` Suresh Siddha
2010-07-20 18:50 ` [PATCH 02/10] x86, xsave: 32/64 bit boot cpu check unification in initialization Robert Richter
2010-07-20 21:47   ` Suresh Siddha
2010-07-21  0:40   ` [tip:x86/xsave] " tip-bot for Robert Richter
2010-07-20 18:50 ` [PATCH 03/10] x86: removing boot_cpu_id variable Robert Richter
2010-07-20 18:50 ` [PATCH 04/10] x86, xsave: moving boot cpu initialization to xsave_init() Robert Richter
2010-07-20 21:48   ` Suresh Siddha
2010-07-21  0:40   ` [tip:x86/xsave] x86, xsave: Move " tip-bot for Robert Richter
2010-07-20 18:50 ` [PATCH 05/10] x86, xsave: make xsave_cntxt_init() static Robert Richter
2010-07-20 22:20   ` Suresh Siddha
2010-07-21 13:48     ` Robert Richter
2010-07-21 16:15       ` H. Peter Anvin
2010-07-20 18:50 ` [PATCH 06/10] x86, xsave: do not initialize xsave in fpu_init() Robert Richter
2010-07-20 22:21   ` Suresh Siddha
2010-07-20 18:50 ` [PATCH 07/10] x86, xsave: reduce cpu_has_xsave checks Robert Richter
2010-07-20 22:22   ` Suresh Siddha
2010-07-20 18:50 ` [PATCH 08/10] x86, xsave: introduce xstate enable functions Robert Richter
2010-07-20 22:23   ` Suresh Siddha
2010-07-20 18:50 ` [PATCH 09/10] x86, xsave: check cpuid level for XSTATE_CPUID (0x0d) Robert Richter
2010-07-20 22:26   ` Suresh Siddha
2010-07-20 22:45     ` H. Peter Anvin
2010-07-20 22:51     ` H. Peter Anvin
2010-07-20 18:50 ` [PATCH 10/10] x86, xsave: make init_xstate_buf static Robert Richter
2010-07-20 22:26   ` Suresh Siddha
2010-07-20 19:27 ` [PATCH 00/10] x86, xsave: some code cleanups and reworks Cyrill Gorcunov
2010-07-20 19:46   ` Robert Richter
2010-07-20 20:05     ` Suresh Siddha
2010-07-20 20:07     ` Cyrill Gorcunov
2010-07-20 20:17       ` Cyrill Gorcunov
2010-07-21 16:16         ` Robert Richter
2010-07-21 16:29           ` Cyrill Gorcunov
2010-07-21 16:32         ` H. Peter Anvin
2010-07-21 16:52           ` Cyrill Gorcunov
2010-07-21 17:01             ` Cyrill Gorcunov
2010-07-21 17:11               ` H. Peter Anvin
2010-07-21 17:17                 ` Cyrill Gorcunov
2010-07-21 17:24                   ` Robert Richter
2010-07-21 17:37                     ` Cyrill Gorcunov [this message]
2010-07-21 19:14                     ` Cyrill Gorcunov
2010-07-20 20:22 ` H. Peter Anvin

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=20100721173723.GG8009@lenovo \
    --to=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=robert.richter@amd.com \
    --cc=suresh.b.siddha@intel.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