From: "Chen, Gong" <gong.chen@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: hpa@zytor.com, tony.luck@intel.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org
Subject: Re: [PATCH] x86, MCE: Clean get_cpu_xxx with this_cpu_xxx
Date: Tue, 15 Apr 2014 21:34:59 -0400 [thread overview]
Message-ID: <20140416013459.GA4399@gchen.bj.intel.com> (raw)
In-Reply-To: <20140415090347.GA31409@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
On Tue, Apr 15, 2014 at 11:03:48AM +0200, Ingo Molnar wrote:
> Date: Tue, 15 Apr 2014 11:03:48 +0200
> From: Ingo Molnar <mingo@kernel.org>
> To: "Chen, Gong" <gong.chen@linux.intel.com>
> Cc: hpa@zytor.com, tony.luck@intel.com, tglx@linutronix.de,
> linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org
> Subject: Re: [PATCH] x86, MCE: Clean get_cpu_xxx with this_cpu_xxx
> User-Agent: Mutt/1.5.21 (2010-09-15)
>
>
> * Chen, Gong <gong.chen@linux.intel.com> wrote:
>
> > This is a cleanup patch suggested by Peter. Use new
> > this_cpu_xxx to improve operation speed. Meanwhile,
> > it fixes an issue introduced in commit 27f6c573e0. I
> > forget to execute put_cpu_var operation after get_cpu_var.
>
> What 'issue'? Is it a bug? If yes, what are the symptoms to the user?
I forget put_cpu_var after get_cpu_var.
>
> Also, fixes must be separate from cleanups.
OK, I will.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-04-16 2:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 7:13 [PATCH] x86, MCE: Clean get_cpu_xxx with this_cpu_xxx Chen, Gong
2014-04-15 9:03 ` Ingo Molnar
2014-04-16 1:34 ` Chen, Gong [this message]
2014-04-16 2:55 ` [PATCH 1/2 v2] x86, MCE: Fix a bug in CMCI handler Chen, Gong
2014-04-16 2:55 ` [PATCH 2/2 v2] x86, MCE: Clean get_cpu_xxx with this_cpu_xxx Chen, Gong
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=20140416013459.GA4399@gchen.bj.intel.com \
--to=gong.chen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.