public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Xiong Zhang <xiong.y.zhang@intel.com>, kvm@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, weijiang.yang@intel.com,
	seanjc@google.com, like.xu.linux@gmail.com, zhiyuan.lv@intel.com,
	zhenyu.z.wang@intel.com, kan.liang@intel.com,
	Xiong Zhang <xiong.y.zhang@intel.com>
Subject: Re: [PATCH v2] Documentation: KVM: Add vPMU implementaion and gap document
Date: Wed, 2 Aug 2023 09:14:56 +0800	[thread overview]
Message-ID: <202308020931.XkEOeIFg-lkp@intel.com> (raw)
In-Reply-To: <20230801035836.1048879-1-xiong.y.zhang@intel.com>

Hi Xiong,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 88bb466c9dec4f70d682cf38c685324e7b1b3d60]

url:    https://github.com/intel-lab-lkp/linux/commits/Xiong-Zhang/Documentation-KVM-Add-vPMU-implementaion-and-gap-document/20230801-120150
base:   88bb466c9dec4f70d682cf38c685324e7b1b3d60
patch link:    https://lore.kernel.org/r/20230801035836.1048879-1-xiong.y.zhang%40intel.com
patch subject: [PATCH v2] Documentation: KVM: Add vPMU implementaion and gap document
reproduce: (https://download.01.org/0day-ci/archive/20230802/202308020931.XkEOeIFg-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308020931.XkEOeIFg-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Documentation/virt/kvm/x86/pmu.rst:45: WARNING: Inline emphasis start-string without end-string.

vim +45 Documentation/virt/kvm/x86/pmu.rst

    44	
  > 45	Perf event is created by perf_event_open() system call:
    46	int syscall(SYS_perf_event_open, struct perf_event_attr *attr,
    47		    pid_t pid, int cpu, int roup_fd, unsigned long flags)
    48	
    49	    struct perf_event_attr {
    50		    ......
    51		    /* Major type: hardware/software/tracepoint/etc. */
    52		    __u32   type;
    53		    /* Type specific configuration information. */
    54		    __u64   config;
    55		    union {
    56			    __u64      sample_period;
    57			    __u64      sample_freq;
    58		    }
    59		   __u64   disabled :1;
    60		           pinned   :1;
    61			   exclude_user  :1;
    62			   exclude_kernel :1;
    63			   exclude_host   :1;
    64		           exclude_guest  :1;
    65		    ......
    66	    }
    67	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-08-02  1:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01  3:58 [PATCH v2] Documentation: KVM: Add vPMU implementaion and gap document Xiong Zhang
2023-08-02  1:14 ` kernel test robot [this message]
2023-08-02  5:57 ` Mi, Dapeng
2023-08-03  0:52   ` Zhang, Xiong Y

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=202308020931.XkEOeIFg-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kan.liang@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=like.xu.linux@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=seanjc@google.com \
    --cc=weijiang.yang@intel.com \
    --cc=xiong.y.zhang@intel.com \
    --cc=zhenyu.z.wang@intel.com \
    --cc=zhiyuan.lv@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