From: kernel test robot <lkp@intel.com>
To: Aaron Lewis <aaronlewis@google.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Sean Christopherson <seanjc@google.com>,
linux-doc@vger.kernel.org
Subject: [linux-next:master 5972/6912] htmldocs: Documentation/virt/kvm/api.rst:5070: WARNING: Unexpected indentation.
Date: Fri, 20 Jan 2023 20:36:48 +0800 [thread overview]
Message-ID: <202301202042.herfGxx6-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: d514392f17fd4d386cfadde7f849d97db4ca1fb0
commit: 651daa44b11c0ea916dee075c8acad002d1b50a2 [5972/6912] kvm: x86/pmu: Introduce masked events to the pmu event filter
reproduce:
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=651daa44b11c0ea916dee075c8acad002d1b50a2
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 651daa44b11c0ea916dee075c8acad002d1b50a2
make menuconfig
# enable CONFIG_COMPILE_TEST, CONFIG_WARN_MISSING_DOCUMENTS, CONFIG_WARN_ABI_ERRORS
make htmldocs
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> Documentation/virt/kvm/api.rst:5070: WARNING: Unexpected indentation.
vim +5070 Documentation/virt/kvm/api.rst
5057
5058 Bits Description
5059 ---- -----------
5060 7:0 event select (low bits)
5061 15:8 umask match
5062 31:16 unused
5063 35:32 event select (high bits)
5064 36:54 unused
5065 55 exclude bit
5066 63:56 umask mask
5067
5068 When the guest attempts to program the PMU, these steps are followed in
5069 determining if the guest should have access:
> 5070 1. Match the event select from the guest against the filter events.
5071 2. If a match is found, match the guest's unit mask to the mask and match
5072 values of the included filter events.
5073 I.e. (unit mask & mask) == match && !exclude.
5074 3. If a match is found, match the guest's unit mask to the mask and match
5075 values of the excluded filter events.
5076 I.e. (unit mask & mask) == match && exclude.
5077 4.
5078 a. If an included match is found and an excluded match is not found, filter
5079 the event.
5080 b. For everything else, do not filter the event.
5081 5.
5082 a. If the event is filtered and it's an allow list, allow the guest to
5083 program the event.
5084 b. If the event is filtered and it's a deny list, do not allow the guest to
5085 program the event.
5086
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-01-20 12:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202301202042.herfGxx6-lkp@intel.com \
--to=lkp@intel.com \
--cc=aaronlewis@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seanjc@google.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).