From: Stephen Hemminger <stephen@networkplumber.org>
To: Drocula <quzeyao@gmail.com>
Cc: maxime.coquelin@redhat.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] bus/pci: check if 5-level paging is enabled when testing IOMMU address width
Date: Thu, 9 Aug 2018 10:03:44 -0700 [thread overview]
Message-ID: <20180809100344.15af7e9c@xeon-e3> (raw)
In-Reply-To: <1533494497-16253-1-git-send-email-quzeyao@gmail.com>
Thanks for the patch, there are some minor style/cleanups that
could be done.
> #if defined(RTE_ARCH_X86)
Isn't this going to apply to 64 bit only?
> +/*
> + * Try to detect whether the system uses 5-level page table.
> + */
> +static bool
> +system_uses_PML5(void)
> +{
> + void *page_4k, *mask = (void *)0xf0000000000000;
Magic constants expressed like this seem wrong. Why not use
shift to make it obvious.
Also, you are assuming a particular layout of memory on
Linux which might be problematic. Plus if there is already
some memory in use there, it won't work.
> + page_4k = mmap(mask, 4096, PROT_READ | PROT_WRITE,
> + MAP_PRIVATE | MAP_ANONYMOUS, -1, 0);
Since you are probing maybe MAP_FIXED is what you want.
> +
> + if (page_4k == (void *) -1)
> + return false;
Use MMAP_FAILED here.
> + munmap(page_4k, 4096);
> +
> + if ((unsigned long)page_4k & (unsigned long)mask)
> + return true;
> + return false;
Wouldn't this work the same for what you expect?
return page_4k == mask;
I.e you expect kernel to put page where you want.
next prev parent reply other threads:[~2018-08-09 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 18:41 Drocula
2018-08-09 10:49 ` Burakov, Anatoly
2018-08-10 7:51 ` Drocula
2018-08-09 17:03 ` Stephen Hemminger [this message]
2018-08-10 8:35 ` Drocula
2018-08-10 9:18 ` Burakov, Anatoly
2018-08-13 12:57 ` [dpdk-dev] [PATCH v2] " Drocula
2018-10-28 18:22 ` Thomas Monjalon
2023-06-09 16:31 ` [PATCH] " Stephen Hemminger
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=20180809100344.15af7e9c@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=quzeyao@gmail.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;
as well as URLs for NNTP newsgroup(s).