From: "Yang, Bin" <bin.yang@intel.com>
To: "tglx@linutronix.de" <tglx@linutronix.de>
Cc: "mingo@kernel.org" <mingo@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"Gross, Mark" <mark.gross@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"Hansen, Dave" <dave.hansen@intel.com>
Subject: Re: [PATCH v3 4/5] x86/mm: optimize static_protection() by using overlap()
Date: Fri, 7 Sep 2018 01:14:33 +0000 [thread overview]
Message-ID: <82fc8d80749f920c4a5107469924205d92037785.camel@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1809041413070.3395@nanos.tec.linutronix.de>
On Tue, 2018-09-04 at 14:22 +0200, Thomas Gleixner wrote:
> On Tue, 21 Aug 2018, Bin Yang wrote:
> >
> > +static inline bool
> > +overlap(unsigned long start1, unsigned long end1,
> > + unsigned long start2, unsigned long end2)
> > +{
> > + /* Is 'start2' within area 1? */
> > + if (start1 <= start2 && end1 > start2)
> > + return true;
> > +
> > + /* Is 'start1' within area 2? */
> > + if (start2 <= start1 && end2 > start1)
> > + return true;
> > +
> > + return false;
> > static inline unsigned long highmap_start_pfn(void)
> > @@ -293,7 +308,7 @@ static void cpa_flush_array(unsigned long *start, int numpages, int cache,
> > * checks and fixes these known static required protection bits.
> > */
> > static inline pgprot_t static_protections(pgprot_t prot, unsigned long address,
> > - unsigned long pfn)
> > + unsigned long len, unsigned long pfn)
> > {
> > pgprot_t forbidden = __pgprot(0);
> >
> > @@ -302,7 +317,9 @@ static inline pgprot_t static_protections(pgprot_t prot, unsigned long address,
> > * PCI BIOS based config access (CONFIG_PCI_GOBIOS) support.
> > */
> > #ifdef CONFIG_PCI_BIOS
> > - if (pcibios_enabled && within(pfn, BIOS_BEGIN >> PAGE_SHIFT, BIOS_END >> PAGE_SHIFT))
> > + if (pcibios_enabled &&
> > + overlap(pfn, pfn + PFN_DOWN(len),
> > + PFN_DOWN(BIOS_BEGIN), PFN_DOWN(BIOS_END)))
>
> This is completely unreadable and aside of that it is wrong. You cannot do
> an overlap check with the following constraints:
>
> range1_end = range1_start + size;
> range2_end = range2_start + size;
>
> See the definition of BIOS_END. It's 0x100000, i.e. 1MB, so the following
> overlap check will give you the false result:
>
> overlap(256, 258, 0x000a0000 >> 12, 0x0010000 >> 12)
>
> because
>
> 0x0010000 >> 12 = 256
>
> ergo will overlap return true. All of your overlap checks are broken.
>
> Oh well.
I just write a test.c to compare the result between overlap() and
original within().
8<--------- test.c ----------------
#include <stdio.h>
#define bool int
#define true 1
#define false 0
#define PAGE_SHIFT 12
#define BIOS_BEGIN 0x000a0000
#define BIOS_END 0x00100000
static inline int
within(unsigned long addr, unsigned long start, unsigned long end)
{
printf("addr=%ld, start=%ld, end=%ld\n",
addr, start, end);
return addr >= start && addr < end;
}
static inline bool
overlap(unsigned long start1, unsigned long end1,
unsigned long start2, unsigned long end2)
{
printf("start1=%ld, end1=%ld, start2=%ld, end2=%ld\n",
start1, end1, start2, end2);
/* Is 'start2' within area 1? */
if (start1 <= start2 && end1 > start2)
return true;
/* Is 'start1' within area 2? */
if (start2 <= start1 && end2 > start1)
return true;
return false;
}
int main(void)
{
int ret;
int pfn;
for (pfn = 256; pfn < 258; pfn ++) {
ret = within(pfn, BIOS_BEGIN >> PAGE_SHIFT, BIOS_END >>
PAGE_SHIFT);
printf("pfn = %d, within() return: %d\n", pfn, ret);
}
ret = overlap(256, 258, BIOS_BEGIN >> PAGE_SHIFT, BIOS_END >>
PAGE_SHIFT);
printf("overlap() return: %d\n", ret);
}
8<------ output ------
addr=256, start=160, end=256
pfn = 256, within() return: 0
addr=257, start=160, end=256
pfn = 257, within() return: 0
start1=256, end1=258, start2=160, end2=256
overlap() return: 0
it looks the overlap() result is same as original one.
>
> Thanks,
>
> tglx
>
>
next prev parent reply other threads:[~2018-09-07 1:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 1:16 [PATCH v3 0/5] x86/mm: fix cpu stuck issue in __change_page_attr_set_clr Bin Yang
2018-08-21 1:16 ` [PATCH v3 1/5] x86/mm: avoid redundant checking if pgprot has no change Bin Yang
2018-09-03 21:57 ` Thomas Gleixner
2018-09-04 7:01 ` Yang, Bin
2018-09-04 7:49 ` Thomas Gleixner
2018-09-04 9:12 ` Yang, Bin
2018-09-04 9:22 ` Yang, Bin
2018-08-21 1:16 ` [PATCH v3 2/5] x86/mm: avoid static_protection() checking if not whole large page attr change Bin Yang
2018-08-21 1:16 ` [PATCH v3 3/5] x86/mm: add help function to check specific protection flags in range Bin Yang
2018-09-03 22:10 ` Thomas Gleixner
2018-09-04 6:22 ` Yang, Bin
2018-08-21 1:16 ` [PATCH v3 4/5] x86/mm: optimize static_protection() by using overlap() Bin Yang
2018-09-04 12:22 ` Thomas Gleixner
2018-09-07 1:14 ` Yang, Bin [this message]
2018-09-07 7:49 ` Thomas Gleixner
2018-09-07 8:04 ` Yang, Bin
2018-09-07 8:21 ` Thomas Gleixner
2018-09-07 8:26 ` Yang, Bin
2018-08-21 1:16 ` [PATCH v3 5/5] x86/mm: add WARN_ON_ONCE() for wrong large page mapping Bin Yang
2018-09-03 22:27 ` Thomas Gleixner
2018-09-04 6:32 ` Yang, Bin
2018-09-04 7:41 ` Thomas Gleixner
2018-09-04 16:52 ` Thomas Gleixner
2018-09-07 2:12 ` Yang, Bin
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=82fc8d80749f920c4a5107469924205d92037785.camel@intel.com \
--to=bin.yang@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®