From: kernel test robot <lkp@intel.com>
To: Chao Peng <chao.p.peng@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Isaku Yamahata <isaku.yamahata@intel.com>,
Yu Zhang <yu.c.zhang@linux.intel.com>,
linux-doc@vger.kernel.org
Subject: [intel-tdx:kvm-upstream-workaround 296/418] htmldocs: Documentation/virt/kvm/api.rst:6679: WARNING: Definition list ends without a blank line; unexpected unindent.
Date: Sun, 10 Jul 2022 08:52:14 +0800 [thread overview]
Message-ID: <202207100806.ymoTKohh-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git kvm-upstream-workaround
head: c2b43d6ee32b2f2de54395e7b2d7ba9bfa727608
commit: e11dbdbae913817716494fb41eb22aa88e1464e0 [296/418] KVM: Add KVM_EXIT_MEMORY_FAULT exit
reproduce: 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:6679: WARNING: Definition list ends without a blank line; unexpected unindent.
vim +6679 Documentation/virt/kvm/api.rst
6667
6668 };
6669
6670 ::
6671 /* KVM_EXIT_MEMORY_FAULT */
6672 struct {
6673 #define KVM_MEMORY_EXIT_FLAG_PRIVATE (1 << 0)
6674 __u32 flags;
6675 __u32 padding;
6676 __u64 gpa;
6677 __u64 size;
6678 } memory;
> 6679 If exit reason is KVM_EXIT_MEMORY_FAULT then it indicates that the VCPU has
6680 encountered a memory error which is not handled by KVM kernel module and
6681 userspace may choose to handle it. The 'flags' field indicates the memory
6682 properties of the exit.
6683
6684 - KVM_MEMORY_EXIT_FLAG_PRIVATE - indicates the memory error is caused by
6685 private memory access when the bit is set otherwise the memory error is
6686 caused by shared memory access when the bit is clear.
6687
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-10 0:52 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=202207100806.ymoTKohh-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=isaku.yamahata@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yu.c.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 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®