From: Pan Xinhui <xinhuix.pan@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org, bp@suse.de,
toshi.kani@hp.com, jgross@suse.com, mcgrof@suse.com,
"mnipxh@163.com" <mnipxh@163.com>,
"yanmin_zhang@linux.intel.com" <yanmin_zhang@linux.intel.com>
Subject: Re: [PATCH V3] x86/mm/pat: Do a small optimization and fix in reserve_memtype
Date: Wed, 22 Jul 2015 20:54:30 +0800 [thread overview]
Message-ID: <55AF9286.1020507@intel.com> (raw)
In-Reply-To: <20150722104624.GA26553@nazgul.tnic>
hi, Borislav
thanks for your reply. :)
On 2015年07月22日 18:46, Borislav Petkov wrote:
> On Wed, Jul 22, 2015 at 05:06:04PM +0800, Pan Xinhui wrote:
>> how about:
>> memtype_lock protects the rb-tree root and the rb-nodes which is a field of memtype from delete/add/lookup in a race.
>
> Use this:
>
> "All pat_rbtree operations need to be performed while holding the
> memtype_lock."
>
thanks!
>> Actually I have same questions. I find these output logs are added in
>> commit: 6997ab4982a29925e79f72c3a59823cf944c3529(x86: add PAT related
>> debug prints) In the past, *new_type == actual_type == new->type on
>> success. codes are below. author use actual_type there.
>
> So this function is one bit PITA. So req_type is used to compute actual
> type a bit higher:
>
> actual_type = pat_x_mtrr_type(start, end, req_type);
>
> and from then on actual_type is being used.
>
> BUT!, in order to have *all* debugging information, the last dprintk()
agree, output all debugging information.
> call should dump actual_type and req_type because this way we show what
then why not append "act %s" to the dprintk format string?
> pat_x_mtrr_type() did too. And we don't need to dump new->type because
> this is the !err case and in that case we assigned new_type to it, which
> we dump already.
yes, new->type is same with *new_type, and dump same value twice.
>
> Ok?
>
Let me think for a while. I wonder why there is not any comment that could tell developers what "track %s" mean.
In different places of this file, "track %s" can mean what type of memory it is now, or it used to be.
So I think this output filed "track %s" is just whatever people want to need to print out.
I prefer to dump all debugging information here, so I agree with your idea. thanks
> Btw, you could also simplify this:
>
> if (is_range_ram == 1) {
>
> err = reserve_ram_pages_type(start, end, req_type, new_type);
>
> return err;
> }
>
> to:
>
> if (is_range_ram == 1)
> return reserve_ram_pages_type(start, end, req_type, new_type);
>
seems better now, thanks!
> while at it.
>
> Thanks.
>
thanks
xinhui
prev parent reply other threads:[~2015-07-22 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 5:38 [PATCH V3] x86/mm/pat: Do a small optimization and fix in reserve_memtype Pan Xinhui
2015-07-22 7:46 ` Borislav Petkov
2015-07-22 9:06 ` Pan Xinhui
2015-07-22 10:46 ` Borislav Petkov
2015-07-22 12:54 ` Pan Xinhui [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=55AF9286.1020507@intel.com \
--to=xinhuix.pan@intel.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=mingo@redhat.com \
--cc=mnipxh@163.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.com \
--cc=x86@kernel.org \
--cc=yanmin_zhang@linux.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.