From: Alex Shi <alex.shi@linux.alibaba.com> To: David Hildenbrand <david@redhat.com>, linux-kernel@vger.kernel.org Cc: 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>, Sebastien Boeuf <sebastien.boeuf@intel.com>, Samuel Ortiz <samuel.ortiz@intel.com>, Robert Bradford <robert.bradford@intel.com>, Luiz Capitulino <lcapitulino@redhat.com>, Alexander Duyck <alexander.h.duyck@linux.intel.com>, Alexander Potapenko <glider@google.com>, Alexander Viro <viro@zeniv.linux.org.uk>, Anshuman Khandual <anshuman.khandual@arm.com>, Anthony Yznaga <anthony.yznaga@oracle.com>, Dan Williams <dan.j.williams@intel.com>, Dave Young <dyoung@redhat.com>, Igor Mammedov <imammedo@redhat.com>, Jason Wang <jasowang@redhat.com>, Johannes Weiner <hannes@cmpxchg.org>, Juergen Gross <jgross@suse.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>, Len Brown <lenb@kernel.org>, Mel Gorman <mgorman@techsingularity.net>, Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@linux.ibm.com>, Oscar Salvador <osalvador@suse.com>, Oscar Salvador <osalvador@suse.de>, Pavel Tatashin <pasha.tatashin@soleen.com>, Pavel Tatashin <pavel.tatashin@microsoft.com>, Pingfan Liu <kernelfans@gmail.com>, Qian Cai <cai@lca.pw>, "Rafael J. Wysocki" <rjw@rjwysocki.net>, Stefan Hajnoczi <stefanha@redhat.com>, Vlastimil Babka <vbabka@suse.cz>, Wei Yang <richard.weiyang@gmail.com> Subject: Re: [PATCH RFC v4 00/13] virtio-mem: paravirtualized memory Date: Fri, 5 Jun 2020 18:06:10 +0800 [thread overview] Message-ID: <fe476535-3e98-0682-559c-73adde22e7ab@linux.alibaba.com> (raw) In-Reply-To: <d6cd1870-1012-cb3d-7d29-8e5ad2703717@redhat.com> 在 2020/6/5 下午5:08, David Hildenbrand 写道: > Please use the virtio-mem-v4 branch for now, v5 is still under > construction (and might be scrapped completely if v4 goes upstream as is). > > Looks like a DMA issue. Your're hotplugging 1GB, which should not really > eat too much memory. There was a similar issue reported by Hui in [1], > which boiled down to wrong usage of the swiotlb parameter. I have no swiotbl=noforce set, and sometime no swiotlb error reported, like (qemu) [ 41.591308] e1000 0000:00:03.0: dma_direct_map_page: overflow 0x000000011fd470da+54 of device mask ffffffff [ 41.592431] e1000 0000:00:03.0: TX DMA map failed [ 41.593031] e1000 0000:00:03.0: dma_direct_map_page: overflow 0x000000011fd474da+54 of device mask ffffff ... [ 63.049464] ata_piix 0000:00:01.1: dma_direct_map_sg: overflow 0x0000000107db2000+4096 of device mask ffffffff [ 63.068297] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 63.069057] ata1.00: failed command: READ DMA [ 63.069580] ata1.00: cmd c8/00:20:40:bd:d2/00:00:00:00:00/e0 tag 0 dma 16384 in [ 63.069580] res 50/00:00:3f:30:80/00:00:00:00:00/a0 Emask 0x40 (internal error) > > In such cases you should always try to reproduce with hotplug of a > sam-sized DIMM. E.g., hotplugging a 1GB DIMM should result in the same > issue. > > What does your .config specify for CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE? Yes, it's set. I had tried the v2/v4 version, which has the same issue. Is this related with virtio-mem start address too low? Thanks a lot! > > I'll try to reproduce with v4 briefly. > > [1] > https://lkml.kernel.org/r/9708F43A-9BD2-4377-8EE8-7FB1D95C6F69@linux.alibaba.com
WARNING: multiple messages have this Message-ID (diff)
From: Alex Shi <alex.shi@linux.alibaba.com> To: David Hildenbrand <david@redhat.com>, linux-kernel@vger.kernel.org Cc: 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>, Sebastien Boeuf <sebastien.boeuf@intel.com>, Samuel Ortiz <samuel.ortiz@intel.com>, Robert Bradford <robert.bradford@intel.com>, Luiz Capitulino <lcapitulino@redhat.com>, Alexander Duyck <alexander.h.duyck@linux.intel.com>, Alexander Potapenko <glider@google.com>, Alexander Viro <viro@zeniv.linux.org.uk>, Anshuman Khandual <anshuman.khandual@arm.com>, Anthony Yznaga <anthony.yznaga@oracle.com>, Dan Williams <dan.j.williams@intel.com>, Dave Young <dyoung@redhat.com>, Igor Mammedov <imammedo@redhat.com>, Jason Wang <jasowa> Subject: Re: [PATCH RFC v4 00/13] virtio-mem: paravirtualized memory Date: Fri, 5 Jun 2020 18:06:10 +0800 [thread overview] Message-ID: <fe476535-3e98-0682-559c-73adde22e7ab@linux.alibaba.com> (raw) In-Reply-To: <d6cd1870-1012-cb3d-7d29-8e5ad2703717@redhat.com> 在 2020/6/5 下午5:08, David Hildenbrand 写道: > Please use the virtio-mem-v4 branch for now, v5 is still under > construction (and might be scrapped completely if v4 goes upstream as is). > > Looks like a DMA issue. Your're hotplugging 1GB, which should not really > eat too much memory. There was a similar issue reported by Hui in [1], > which boiled down to wrong usage of the swiotlb parameter. I have no swiotbl=noforce set, and sometime no swiotlb error reported, like (qemu) [ 41.591308] e1000 0000:00:03.0: dma_direct_map_page: overflow 0x000000011fd470da+54 of device mask ffffffff [ 41.592431] e1000 0000:00:03.0: TX DMA map failed [ 41.593031] e1000 0000:00:03.0: dma_direct_map_page: overflow 0x000000011fd474da+54 of device mask ffffff ... [ 63.049464] ata_piix 0000:00:01.1: dma_direct_map_sg: overflow 0x0000000107db2000+4096 of device mask ffffffff [ 63.068297] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [ 63.069057] ata1.00: failed command: READ DMA [ 63.069580] ata1.00: cmd c8/00:20:40:bd:d2/00:00:00:00:00/e0 tag 0 dma 16384 in [ 63.069580] res 50/00:00:3f:30:80/00:00:00:00:00/a0 Emask 0x40 (internal error) > > In such cases you should always try to reproduce with hotplug of a > sam-sized DIMM. E.g., hotplugging a 1GB DIMM should result in the same > issue. > > What does your .config specify for CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE? Yes, it's set. I had tried the v2/v4 version, which has the same issue. Is this related with virtio-mem start address too low? Thanks a lot! > > I'll try to reproduce with v4 briefly. > > [1] > https://lkml.kernel.org/r/9708F43A-9BD2-4377-8EE8-7FB1D95C6F69@linux.alibaba.com
next prev parent reply other threads:[~2020-06-05 10:06 UTC|newest] Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-12-12 17:11 [PATCH RFC v4 00/13] virtio-mem: paravirtualized memory David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 01/13] ACPI: NUMA: export pxm_to_node David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2019-12-12 21:43 ` Rafael J. Wysocki 2019-12-13 9:41 ` David Hildenbrand 2019-12-13 9:41 ` David Hildenbrand 2019-12-13 9:41 ` [virtio-dev] " David Hildenbrand 2019-12-13 9:47 ` Rafael J. Wysocki 2019-12-13 9:47 ` Rafael J. Wysocki 2019-12-13 9:47 ` Rafael J. Wysocki 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 02/13] virtio-mem: Paravirtualized memory hotplug David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 03/13] virtio-mem: Paravirtualized memory hotunplug part 1 David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 04/13] mm: Export alloc_contig_range() / free_contig_range() David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 05/13] virtio-mem: Paravirtualized memory hotunplug part 2 David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 06/13] mm: Allow to offline unmovable PageOffline() pages via MEM_GOING_OFFLINE David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2020-02-25 18:26 ` Alexander Duyck 2020-02-25 18:26 ` [virtio-dev] " Alexander Duyck 2020-02-25 18:26 ` Alexander Duyck 2020-02-25 18:49 ` David Hildenbrand 2020-02-25 18:49 ` [virtio-dev] " David Hildenbrand 2020-02-25 18:49 ` David Hildenbrand 2020-02-25 21:46 ` Alexander Duyck 2020-02-25 21:46 ` [virtio-dev] " Alexander Duyck 2020-02-25 21:46 ` Alexander Duyck 2020-02-25 22:19 ` David Hildenbrand 2020-02-25 22:19 ` [virtio-dev] " David Hildenbrand 2020-02-25 22:19 ` David Hildenbrand 2020-02-26 16:27 ` Alexander Duyck 2020-02-26 16:27 ` [virtio-dev] " Alexander Duyck 2020-02-26 16:27 ` Alexander Duyck 2019-12-12 17:11 ` [PATCH RFC v4 07/13] virtio-mem: Allow to offline partially unplugged memory blocks David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 08/13] mm/memory_hotplug: Introduce offline_and_remove_memory() David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2020-02-25 14:11 ` Michal Hocko 2020-02-25 14:27 ` David Hildenbrand 2020-02-25 14:27 ` [virtio-dev] " David Hildenbrand 2020-03-02 12:48 ` Michal Hocko 2020-03-02 12:53 ` David Hildenbrand 2020-03-02 12:53 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 09/13] virtio-mem: Offline and remove completely unplugged memory blocks David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 10/13] virtio-mem: Better retry handling David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 11/13] mm/vmscan: Move count_vm_event(DROP_SLAB) into drop_slab() David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2020-02-25 14:13 ` Michal Hocko 2019-12-12 17:11 ` [PATCH RFC v4 12/13] mm/vmscan: Export drop_slab() and drop_slab_node() David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2020-02-25 14:58 ` Michal Hocko 2020-02-25 15:09 ` David Hildenbrand 2020-02-25 15:09 ` [virtio-dev] " David Hildenbrand 2020-02-25 17:06 ` Michal Hocko 2020-02-25 17:23 ` David Hildenbrand 2020-02-25 17:23 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-12 17:11 ` [PATCH RFC v4 13/13] virtio-mem: Drop slab objects when unplug continues to fail David Hildenbrand 2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand 2019-12-12 17:11 ` David Hildenbrand 2019-12-13 20:15 ` [PATCH RFC v4 00/13] virtio-mem: paravirtualized memory Konrad Rzeszutek Wilk 2019-12-13 20:15 ` Konrad Rzeszutek Wilk 2019-12-16 11:03 ` David Hildenbrand 2019-12-16 11:03 ` David Hildenbrand 2019-12-16 11:03 ` [virtio-dev] " David Hildenbrand 2019-12-24 6:58 ` teawater 2019-12-24 9:28 ` David Hildenbrand 2019-12-24 9:28 ` [virtio-dev] " David Hildenbrand 2019-12-24 9:28 ` David Hildenbrand 2020-01-09 13:48 ` David Hildenbrand 2020-01-09 13:48 ` [virtio-dev] " David Hildenbrand 2020-01-29 9:41 ` David Hildenbrand 2020-01-29 9:41 ` [virtio-dev] " David Hildenbrand 2020-01-29 9:41 ` David Hildenbrand 2020-02-25 9:58 ` David Hildenbrand 2020-02-25 9:58 ` [virtio-dev] " David Hildenbrand 2020-02-25 9:58 ` David Hildenbrand 2020-06-05 8:55 ` Alex Shi 2020-06-05 8:55 ` Alex Shi 2020-06-05 9:08 ` David Hildenbrand 2020-06-05 9:08 ` [virtio-dev] " David Hildenbrand 2020-06-05 9:08 ` David Hildenbrand 2020-06-05 9:36 ` David Hildenbrand 2020-06-05 9:36 ` [virtio-dev] " David Hildenbrand 2020-06-05 9:36 ` David Hildenbrand 2020-06-05 10:05 ` David Hildenbrand 2020-06-05 10:05 ` [virtio-dev] " David Hildenbrand 2020-06-05 10:05 ` David Hildenbrand 2020-06-05 10:46 ` Alex Shi 2020-06-05 10:46 ` Alex Shi 2020-06-05 12:18 ` David Hildenbrand 2020-06-05 12:18 ` [virtio-dev] " David Hildenbrand 2020-06-05 12:18 ` David Hildenbrand 2020-06-09 3:05 ` Alex Shi 2020-06-09 3:05 ` Alex Shi 2020-06-05 10:08 ` Alex Shi 2020-06-05 10:08 ` Alex Shi 2020-06-05 10:06 ` Alex Shi [this message] 2020-06-05 10:06 ` Alex Shi 2020-01-09 13:48 ` David Hildenbrand -- strict thread matches above, loose matches on Subject: below -- 2019-12-12 17:11 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=fe476535-3e98-0682-559c-73adde22e7ab@linux.alibaba.com \ --to=alex.shi@linux.alibaba.com \ --cc=akpm@linux-foundation.org \ --cc=alexander.h.duyck@linux.intel.com \ --cc=anshuman.khandual@arm.com \ --cc=anthony.yznaga@oracle.com \ --cc=cai@lca.pw \ --cc=dan.j.williams@intel.com \ --cc=david@redhat.com \ --cc=dyoung@redhat.com \ --cc=glider@google.com \ --cc=hannes@cmpxchg.org \ --cc=imammedo@redhat.com \ --cc=jasowang@redhat.com \ --cc=jgross@suse.com \ --cc=kernelfans@gmail.com \ --cc=konrad.wilk@oracle.com \ --cc=kvm@vger.kernel.org \ --cc=lcapitulino@redhat.com \ --cc=lenb@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mgorman@techsingularity.net \ --cc=mhocko@kernel.org \ --cc=mhocko@suse.com \ --cc=mst@redhat.com \ --cc=osalvador@suse.com \ --cc=osalvador@suse.de \ --cc=pasha.tatashin@soleen.com \ --cc=pavel.tatashin@microsoft.com \ --cc=richard.weiyang@gmail.com \ --cc=rjw@rjwysocki.net \ --cc=robert.bradford@intel.com \ --cc=rppt@linux.ibm.com \ --cc=samuel.ortiz@intel.com \ --cc=sebastien.boeuf@intel.com \ --cc=stefanha@redhat.com \ --cc=vbabka@suse.cz \ --cc=viro@zeniv.linux.org.uk \ --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: linkBe 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.