From: David Hildenbrand <david@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Igor Mammedov <imammedo@redhat.com>,
Dave Young <dyoung@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v1 02/11] virtio-mem: Paravirtualized memory hotplug
Date: Tue, 3 Mar 2020 09:06:29 +0100 [thread overview]
Message-ID: <3851c1eb-92ee-7c85-088f-2adeef3272e6@redhat.com> (raw)
In-Reply-To: <202003031039.To18mcrC%lkp@intel.com>
On 03.03.20 03:24, kbuild test robot wrote:
> Hi David,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on pm/linux-next]
> [also build test ERROR on linus/master v5.6-rc4 next-20200302]
> [cannot apply to linux/master mmotm/master]
> [if your patch is applied to the wrong git tree, please drop us a note to help
> improve the system. BTW, we also suggest to use '--base' option to specify the
> base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
>
> url: https://github.com/0day-ci/linux/commits/David-Hildenbrand/virtio-mem-paravirtualized-memory/20200303-020852
> base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
> config: x86_64-randconfig-s1-20200303 (attached as .config)
> compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> In file included from <command-line>:1:0:
>>> ./usr/include/linux/virtio_mem.h:185:2: error: unknown type name 'uint32_t'
> uint32_t block_size;
> ^
>>> ./usr/include/linux/virtio_mem.h:187:2: error: unknown type name 'uint16_t'
> uint16_t node_id;
> ^
> ./usr/include/linux/virtio_mem.h:188:2: error: unknown type name 'uint16_t'
> uint16_t padding;
> ^
>>> ./usr/include/linux/virtio_mem.h:190:2: error: unknown type name 'uint64_t'
> uint64_t addr;
> ^
> ./usr/include/linux/virtio_mem.h:192:2: error: unknown type name 'uint64_t'
> uint64_t region_size;
> ^
> ./usr/include/linux/virtio_mem.h:198:2: error: unknown type name 'uint64_t'
> uint64_t usable_region_size;
> ^
> ./usr/include/linux/virtio_mem.h:203:2: error: unknown type name 'uint64_t'
> uint64_t plugged_size;
> ^
> ./usr/include/linux/virtio_mem.h:205:2: error: unknown type name 'uint64_t'
> uint64_t requested_size;
> ^
Right, these have to be __u64 and friends. Should really enable
CONFIG_UAPI_HEADER_TEST in my default config.
--
Thanks,
David / dhildenb
WARNING: multiple messages have this Message-ID (diff)
From: David Hildenbrand <david@redhat.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v1 02/11] virtio-mem: Paravirtualized memory hotplug
Date: Tue, 03 Mar 2020 09:06:29 +0100 [thread overview]
Message-ID: <3851c1eb-92ee-7c85-088f-2adeef3272e6@redhat.com> (raw)
In-Reply-To: <202003031039.To18mcrC%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2277 bytes --]
On 03.03.20 03:24, kbuild test robot wrote:
> Hi David,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on pm/linux-next]
> [also build test ERROR on linus/master v5.6-rc4 next-20200302]
> [cannot apply to linux/master mmotm/master]
> [if your patch is applied to the wrong git tree, please drop us a note to help
> improve the system. BTW, we also suggest to use '--base' option to specify the
> base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
>
> url: https://github.com/0day-ci/linux/commits/David-Hildenbrand/virtio-mem-paravirtualized-memory/20200303-020852
> base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
> config: x86_64-randconfig-s1-20200303 (attached as .config)
> compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> In file included from <command-line>:1:0:
>>> ./usr/include/linux/virtio_mem.h:185:2: error: unknown type name 'uint32_t'
> uint32_t block_size;
> ^
>>> ./usr/include/linux/virtio_mem.h:187:2: error: unknown type name 'uint16_t'
> uint16_t node_id;
> ^
> ./usr/include/linux/virtio_mem.h:188:2: error: unknown type name 'uint16_t'
> uint16_t padding;
> ^
>>> ./usr/include/linux/virtio_mem.h:190:2: error: unknown type name 'uint64_t'
> uint64_t addr;
> ^
> ./usr/include/linux/virtio_mem.h:192:2: error: unknown type name 'uint64_t'
> uint64_t region_size;
> ^
> ./usr/include/linux/virtio_mem.h:198:2: error: unknown type name 'uint64_t'
> uint64_t usable_region_size;
> ^
> ./usr/include/linux/virtio_mem.h:203:2: error: unknown type name 'uint64_t'
> uint64_t plugged_size;
> ^
> ./usr/include/linux/virtio_mem.h:205:2: error: unknown type name 'uint64_t'
> uint64_t requested_size;
> ^
Right, these have to be __u64 and friends. Should really enable
CONFIG_UAPI_HEADER_TEST in my default config.
--
Thanks,
David / dhildenb
WARNING: multiple messages have this Message-ID (diff)
From: David Hildenbrand <david@redhat.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Igor Mammedov <imammedo@redhat.com>,
Dave Young <dyoung@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org
Subject: [virtio-dev] Re: [PATCH v1 02/11] virtio-mem: Paravirtualized memory hotplug
Date: Tue, 3 Mar 2020 09:06:29 +0100 [thread overview]
Message-ID: <3851c1eb-92ee-7c85-088f-2adeef3272e6@redhat.com> (raw)
In-Reply-To: <202003031039.To18mcrC%lkp@intel.com>
On 03.03.20 03:24, kbuild test robot wrote:
> Hi David,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on pm/linux-next]
> [also build test ERROR on linus/master v5.6-rc4 next-20200302]
> [cannot apply to linux/master mmotm/master]
> [if your patch is applied to the wrong git tree, please drop us a note to help
> improve the system. BTW, we also suggest to use '--base' option to specify the
> base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
>
> url: https://github.com/0day-ci/linux/commits/David-Hildenbrand/virtio-mem-paravirtualized-memory/20200303-020852
> base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
> config: x86_64-randconfig-s1-20200303 (attached as .config)
> compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> In file included from <command-line>:1:0:
>>> ./usr/include/linux/virtio_mem.h:185:2: error: unknown type name 'uint32_t'
> uint32_t block_size;
> ^
>>> ./usr/include/linux/virtio_mem.h:187:2: error: unknown type name 'uint16_t'
> uint16_t node_id;
> ^
> ./usr/include/linux/virtio_mem.h:188:2: error: unknown type name 'uint16_t'
> uint16_t padding;
> ^
>>> ./usr/include/linux/virtio_mem.h:190:2: error: unknown type name 'uint64_t'
> uint64_t addr;
> ^
> ./usr/include/linux/virtio_mem.h:192:2: error: unknown type name 'uint64_t'
> uint64_t region_size;
> ^
> ./usr/include/linux/virtio_mem.h:198:2: error: unknown type name 'uint64_t'
> uint64_t usable_region_size;
> ^
> ./usr/include/linux/virtio_mem.h:203:2: error: unknown type name 'uint64_t'
> uint64_t plugged_size;
> ^
> ./usr/include/linux/virtio_mem.h:205:2: error: unknown type name 'uint64_t'
> uint64_t requested_size;
> ^
Right, these have to be __u64 and friends. Should really enable
CONFIG_UAPI_HEADER_TEST in my default config.
--
Thanks,
David / dhildenb
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2020-03-03 8:06 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 13:49 [PATCH v1 00/11] virtio-mem: paravirtualized memory David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-02 13:49 ` David Hildenbrand
2020-03-02 13:49 ` [PATCH v1 01/11] ACPI: NUMA: export pxm_to_node David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-02 14:03 ` Michal Hocko
2020-03-02 14:09 ` David Hildenbrand
2020-03-02 14:09 ` [virtio-dev] " David Hildenbrand
2020-03-02 13:49 ` [PATCH v1 02/11] virtio-mem: Paravirtualized memory hotplug David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-03 2:24 ` kbuild test robot
2020-03-03 2:24 ` kbuild test robot
2020-03-03 2:24 ` kbuild test robot
2020-03-03 8:06 ` David Hildenbrand [this message]
2020-03-03 8:06 ` [virtio-dev] " David Hildenbrand
2020-03-03 8:06 ` David Hildenbrand
2020-03-02 13:49 ` [PATCH v1 03/11] virtio-mem: Paravirtualized memory hotunplug part 1 David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-02 13:49 ` [PATCH v1 04/11] mm: Export alloc_contig_range() / free_contig_range() David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-02 14:05 ` Michal Hocko
2020-03-02 14:17 ` David Hildenbrand
2020-03-02 14:17 ` [virtio-dev] " David Hildenbrand
2020-03-02 13:49 ` [PATCH v1 05/11] virtio-mem: Paravirtualized memory hotunplug part 2 David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-02 13:49 ` [PATCH v1 06/11] mm: Allow to offline unmovable PageOffline() pages via MEM_GOING_OFFLINE David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-02 17:40 ` Alexander Duyck
2020-03-02 17:40 ` [virtio-dev] " Alexander Duyck
2020-03-02 17:40 ` Alexander Duyck
2020-03-02 17:40 ` Alexander Duyck
2020-03-02 18:41 ` David Hildenbrand
2020-03-02 18:41 ` [virtio-dev] " David Hildenbrand
2020-03-10 11:47 ` Michal Hocko
2020-03-10 11:47 ` Michal Hocko
2020-03-10 11:48 ` David Hildenbrand
2020-03-10 11:48 ` [virtio-dev] " David Hildenbrand
2020-03-10 11:48 ` David Hildenbrand
2020-03-02 13:49 ` [PATCH v1 07/11] virtio-mem: Allow to offline partially unplugged memory blocks David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-10 11:43 ` Michal Hocko
2020-03-10 11:46 ` David Hildenbrand
2020-03-10 11:46 ` [virtio-dev] " David Hildenbrand
2020-03-10 11:59 ` Michal Hocko
2020-03-10 12:09 ` David Hildenbrand
2020-03-10 12:09 ` [virtio-dev] " David Hildenbrand
2020-03-02 13:49 ` [PATCH v1 08/11] mm/memory_hotplug: Introduce offline_and_remove_memory() David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-02 14:27 ` Michal Hocko
2020-03-02 13:49 ` [PATCH v1 09/11] virtio-mem: Offline and remove completely unplugged memory blocks David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-02 13:49 ` [PATCH v1 10/11] virtio-mem: Better retry handling David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-02 13:49 ` [PATCH v1 11/11] MAINTAINERS: Add myself as virtio-mem maintainer David Hildenbrand
2020-03-02 13:49 ` [virtio-dev] " David Hildenbrand
2020-03-02 18:15 ` [PATCH v1 00/11] virtio-mem: paravirtualized memory David Hildenbrand
2020-03-02 18:15 ` [virtio-dev] " David Hildenbrand
2020-03-02 18:15 ` David Hildenbrand
2020-03-02 18:29 ` Michal Hocko
2020-03-02 18:29 ` Michal Hocko
2020-03-02 18:41 ` David Hildenbrand
2020-03-02 18:41 ` [virtio-dev] " David Hildenbrand
2020-03-02 18:41 ` David Hildenbrand
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=3851c1eb-92ee-7c85-088f-2adeef3272e6@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dyoung@redhat.com \
--cc=imammedo@redhat.com \
--cc=jasowang@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=kvm@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mhocko@kernel.org \
--cc=mst@redhat.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=rjw@rjwysocki.net \
--cc=stefanha@redhat.com \
--cc=vbabka@suse.cz \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.