From: Ingo Molnar <mingo@kernel.org>
To: Toshi Kani <toshi.kani@hp.com>
Cc: akpm@linux-foundation.org, hpa@zytor.com, tglx@linutronix.de,
mingo@redhat.com, linux-mm@kvack.org, x86@kernel.org,
linux-kernel@vger.kernel.org, dave.hansen@intel.com,
Elliott@hp.com, pebolle@tiscali.nl
Subject: Re: [PATCH v3 4/5] mtrr, x86: Clean up mtrr_type_lookup()
Date: Mon, 16 Mar 2015 08:58:21 +0100 [thread overview]
Message-ID: <20150316075821.GA16062@gmail.com> (raw)
In-Reply-To: <1426282421-25385-5-git-send-email-toshi.kani@hp.com>
* Toshi Kani <toshi.kani@hp.com> wrote:
> MTRRs contain fixed and variable entries. mtrr_type_lookup()
> may repeatedly call __mtrr_type_lookup() to handle a request
> that overlaps with variable entries. However,
> __mtrr_type_lookup() also handles the fixed entries, which
> do not have to be repeated. Therefore, this patch creates
> separate functions, mtrr_type_lookup_fixed() and
> mtrr_type_lookup_variable(), to handle the fixed and variable
> ranges respectively.
>
> The patch also updates the function headers to clarify the
> return values and output argument. It updates comments to
> clarify that the repeating is necessary to handle overlaps
> with the default type, since overlaps with multiple entries
> alone can be handled without such repeating.
>
> There is no functional change in this patch.
Nice cleanup!
I also suggest adding a small table to the comments before the
function, that lists the fixed purpose MTRRs and their address ranges
- to make it more obvious what the magic hexadecimal constants within
the code are doing.
> +static u8 mtrr_type_lookup_fixed(u64 start, u64 end)
> +{
> + int idx;
> +
> + if (start >= 0x100000)
> + return 0xFF;
Btw., as a separate cleanup patch, we should probably also change
'0xFF' (which is sometimes written as 0xff) to be some sufficiently
named constant, and explain its usage somewhere?
> + if (!(mtrr_state.have_fixed) ||
> + !(mtrr_state.enabled & MTRR_STATE_MTRR_FIXED_ENABLED))
Btw., can MTRR_STATE_MTRR_FIXED_ENABLED ever be set in
mtrr_state.enabled, without mtrr_state.have_fixed being set?
AFAICS get_mtrr_state() will only ever fill in mtrr_state with fixed
MTRRs if mtrr_state.have_fixed != 0 - but I might be mis-reading the
(rather convoluted) flow of code ...
Thanks,
Ingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Toshi Kani <toshi.kani@hp.com>
Cc: akpm@linux-foundation.org, hpa@zytor.com, tglx@linutronix.de,
mingo@redhat.com, linux-mm@kvack.org, x86@kernel.org,
linux-kernel@vger.kernel.org, dave.hansen@intel.com,
Elliott@hp.com, pebolle@tiscali.nl
Subject: Re: [PATCH v3 4/5] mtrr, x86: Clean up mtrr_type_lookup()
Date: Mon, 16 Mar 2015 08:58:21 +0100 [thread overview]
Message-ID: <20150316075821.GA16062@gmail.com> (raw)
In-Reply-To: <1426282421-25385-5-git-send-email-toshi.kani@hp.com>
* Toshi Kani <toshi.kani@hp.com> wrote:
> MTRRs contain fixed and variable entries. mtrr_type_lookup()
> may repeatedly call __mtrr_type_lookup() to handle a request
> that overlaps with variable entries. However,
> __mtrr_type_lookup() also handles the fixed entries, which
> do not have to be repeated. Therefore, this patch creates
> separate functions, mtrr_type_lookup_fixed() and
> mtrr_type_lookup_variable(), to handle the fixed and variable
> ranges respectively.
>
> The patch also updates the function headers to clarify the
> return values and output argument. It updates comments to
> clarify that the repeating is necessary to handle overlaps
> with the default type, since overlaps with multiple entries
> alone can be handled without such repeating.
>
> There is no functional change in this patch.
Nice cleanup!
I also suggest adding a small table to the comments before the
function, that lists the fixed purpose MTRRs and their address ranges
- to make it more obvious what the magic hexadecimal constants within
the code are doing.
> +static u8 mtrr_type_lookup_fixed(u64 start, u64 end)
> +{
> + int idx;
> +
> + if (start >= 0x100000)
> + return 0xFF;
Btw., as a separate cleanup patch, we should probably also change
'0xFF' (which is sometimes written as 0xff) to be some sufficiently
named constant, and explain its usage somewhere?
> + if (!(mtrr_state.have_fixed) ||
> + !(mtrr_state.enabled & MTRR_STATE_MTRR_FIXED_ENABLED))
Btw., can MTRR_STATE_MTRR_FIXED_ENABLED ever be set in
mtrr_state.enabled, without mtrr_state.have_fixed being set?
AFAICS get_mtrr_state() will only ever fill in mtrr_state with fixed
MTRRs if mtrr_state.have_fixed != 0 - but I might be mis-reading the
(rather convoluted) flow of code ...
Thanks,
Ingo
next prev parent reply other threads:[~2015-03-16 7:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 21:33 [PATCH v3 0/5] mtrr, mm, x86: Enhance MTRR checks for huge I/O mapping Toshi Kani
2015-03-13 21:33 ` Toshi Kani
2015-03-13 21:33 ` [PATCH v3 1/5] mm, x86: Document return values of mapping funcs Toshi Kani
2015-03-13 21:33 ` Toshi Kani
2015-03-13 21:33 ` [PATCH v3 2/5] mtrr, x86: Fix MTRR lookup to handle inclusive entry Toshi Kani
2015-03-13 21:33 ` Toshi Kani
2015-03-16 7:49 ` Ingo Molnar
2015-03-16 7:49 ` Ingo Molnar
2015-03-16 21:03 ` Kani, Toshimitsu
2015-03-16 21:03 ` Kani, Toshimitsu
2015-03-13 21:33 ` [PATCH v3 3/5] mtrr, x86: Fix MTRR state checks in mtrr_type_lookup() Toshi Kani
2015-03-13 21:33 ` Toshi Kani
2015-03-16 7:51 ` Ingo Molnar
2015-03-16 7:51 ` Ingo Molnar
2015-03-16 21:08 ` Kani, Toshimitsu
2015-03-16 21:08 ` Kani, Toshimitsu
2015-03-13 21:33 ` [PATCH v3 4/5] mtrr, x86: Clean up mtrr_type_lookup() Toshi Kani
2015-03-13 21:33 ` Toshi Kani
2015-03-16 7:58 ` Ingo Molnar [this message]
2015-03-16 7:58 ` Ingo Molnar
2015-03-16 21:24 ` Kani, Toshimitsu
2015-03-16 21:24 ` Kani, Toshimitsu
2015-03-23 19:27 ` Toshi Kani
2015-03-23 19:27 ` Toshi Kani
2015-03-13 21:33 ` [PATCH v3 5/5] mtrr, mm, x86: Enhance MTRR checks for KVA huge page mapping Toshi Kani
2015-03-13 21:33 ` Toshi Kani
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=20150316075821.GA16062@gmail.com \
--to=mingo@kernel.org \
--cc=Elliott@hp.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=pebolle@tiscali.nl \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.com \
--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 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.