From: "Michal Suchánek" <msuchanek@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
Rich Felker <dalias@libc.org>,
linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Michal Hocko <mhocko@kernel.org>,
linux-mm@kvack.org, Paul Mackerras <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Rashmica Gupta <rashmica.g@gmail.com>,
Dan Williams <dan.j.williams@intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Michael Neuling <mikey@neuling.org>,
Stephen Hemminger <sthemmin@microsoft.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-acpi@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
xen-devel@lists.xenproject.org, Len Brown <lenb@kernel.org>,
Pavel Tatashin <pavel.tatashin@microsoft.com>,
Rob Herring <robh@kernel.org>,
mike.travis@hpe.com
Subject: Re: [PATCH RFC] mm/memory_hotplug: Introduce memory block types
Date: Thu, 4 Oct 2018 19:50:10 +0200 [thread overview]
Message-ID: <20181004195010.3616fc40@kitsune.suse.cz> (raw)
In-Reply-To: <14992b68-5402-9168-0050-b3c6ac4a8c90@redhat.com>
On Thu, 4 Oct 2018 17:45:13 +0200
David Hildenbrand <david@redhat.com> wrote:
> On 04/10/2018 17:28, Michal Suchánek wrote:
> >
> > The state of the art is to determine what to do with hotplugged
> > memory in userspace based on platform and virtualization type.
>
> Exactly.
>
> >
> > Changing the default to depend on the driver that added the memory
> > rather than platform type should solve the issue of VMs growing
> > different types of memory device emulation.
>
> Yes, my original proposal (this patch) was to handle it in the kernel
> for known types. But as we learned, there might be some use cases that
> might still require to make a decision in user space.
>
> So providing the user space either with some type hint (auto-online
> vs. standby) or the driver that added it (system vs. hyper-v ...)
> would solve the issue.
Is that not available in the udev event?
Thanks
Michal
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Michal Suchánek" <msuchanek@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: "Kate Stewart" <kstewart@linuxfoundation.org>,
"Rich Felker" <dalias@libc.org>,
linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
"Peter Zijlstra" <peterz@infradead.org>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Heiko Carstens" <heiko.carstens@de.ibm.com>,
"Michal Hocko" <mhocko@kernel.org>,
linux-mm@kvack.org, "Paul Mackerras" <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Rashmica Gupta" <rashmica.g@gmail.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Michael Neuling" <mikey@neuling.org>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
"Yoshinori Sato" <ysato@users.sourceforge.jp>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
linux-acpi@vger.kernel.org, "Ingo Molnar" <mingo@redhat.com>,
xen-devel@lists.xenproject.org, "Rob Herring" <robh@kernel.org>,
"Len Brown" <lenb@kernel.org>,
"Pavel Tatashin" <pavel.tatashin@microsoft.com>,
linux-s390@vger.kernel.org,
"mike.travis@hpe.com" <mike.travis@hpe.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Joe Perches" <joe@perches.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Mike Rapoport" <rppt@linux.vnet.ibm.com>,
"Borislav Petkov" <bp@alien8.de>,
"Andy Lutomirski" <luto@kernel.org>,
"Dan Williams" <dan.j.williams@intel.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Oscar Salvador" <osalvador@suse.de>,
"Juergen Gross" <jgross@suse.com>,
"Tony Luck" <tony.luck@intel.com>,
"Mathieu Malaterre" <malat@debian.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, "Fenghua Yu" <fenghua.yu@intel.com>,
"Mauricio Faria de Oliveira" <mauricfo@linux.vnet.ibm.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Philippe Ombredanne" <pombredanne@nexb.com>,
"Martin Schwidefsky" <schwidefsky@de.ibm.com>,
devel@linuxdriverproject.org,
"Joonsoo Kim" <iamjoonsoo.kim@lge.com>,
linuxppc-dev@lists.ozlabs.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH RFC] mm/memory_hotplug: Introduce memory block types
Date: Thu, 4 Oct 2018 19:50:10 +0200 [thread overview]
Message-ID: <20181004195010.3616fc40@kitsune.suse.cz> (raw)
In-Reply-To: <14992b68-5402-9168-0050-b3c6ac4a8c90@redhat.com>
On Thu, 4 Oct 2018 17:45:13 +0200
David Hildenbrand <david@redhat.com> wrote:
> On 04/10/2018 17:28, Michal Suchánek wrote:
> >
> > The state of the art is to determine what to do with hotplugged
> > memory in userspace based on platform and virtualization type.
>
> Exactly.
>
> >
> > Changing the default to depend on the driver that added the memory
> > rather than platform type should solve the issue of VMs growing
> > different types of memory device emulation.
>
> Yes, my original proposal (this patch) was to handle it in the kernel
> for known types. But as we learned, there might be some use cases that
> might still require to make a decision in user space.
>
> So providing the user space either with some type hint (auto-online
> vs. standby) or the driver that added it (system vs. hyper-v ...)
> would solve the issue.
Is that not available in the udev event?
Thanks
Michal
WARNING: multiple messages have this Message-ID (diff)
From: "Michal Suchánek" <msuchanek@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: "Kate Stewart" <kstewart@linuxfoundation.org>,
"Rich Felker" <dalias@libc.org>,
linux-ia64@vger.kernel.org, linux-sh@vger.kernel.org,
"Peter Zijlstra" <peterz@infradead.org>,
"Joonsoo Kim" <iamjoonsoo.kim@lge.com>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"Heiko Carstens" <heiko.carstens@de.ibm.com>,
"Michal Hocko" <mhocko@kernel.org>,
linux-mm@kvack.org, "Paul Mackerras" <paulus@samba.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Rashmica Gupta" <rashmica.g@gmail.com>,
"Dan Williams" <dan.j.williams@intel.com>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Michael Neuling" <mikey@neuling.org>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
"Yoshinori Sato" <ysato@users.sourceforge.jp>,
linux-acpi@vger.kernel.org, "Ingo Molnar" <mingo@redhat.com>,
xen-devel@lists.xenproject.org, "Len Brown" <lenb@kernel.org>,
"Pavel Tatashin" <pavel.tatashin@microsoft.com>,
"Rob Herring" <robh@kernel.org>,
"mike.travis@hpe.com" <mike.travis@hpe.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"Philippe Ombredanne" <pombredanne@nexb.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Martin Schwidefsky" <schwidefsky@de.ibm.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Mike Rapoport" <rppt@linux.vnet.ibm.com>,
"Borislav Petkov" <bp@alien8.de>,
"Andy Lutomirski" <luto@kernel.org>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Oscar Salvador" <osalvador@suse.de>,
"Juergen Gross" <jgross@suse.com>,
"Tony Luck" <tony.luck@intel.com>,
"Mathieu Malaterre" <malat@debian.org>,
linux-s390@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, "Fenghua Yu" <fenghua.yu@intel.com>,
"Mauricio Faria de Oliveira" <mauricfo@linux.vnet.ibm.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Joe Perches" <joe@perches.com>,
devel@linuxdriverproject.org,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
linuxppc-dev@lists.ozlabs.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH RFC] mm/memory_hotplug: Introduce memory block types
Date: Thu, 4 Oct 2018 19:50:10 +0200 [thread overview]
Message-ID: <20181004195010.3616fc40@kitsune.suse.cz> (raw)
In-Reply-To: <14992b68-5402-9168-0050-b3c6ac4a8c90@redhat.com>
On Thu, 4 Oct 2018 17:45:13 +0200
David Hildenbrand <david@redhat.com> wrote:
> On 04/10/2018 17:28, Michal Suchánek wrote:
> >
> > The state of the art is to determine what to do with hotplugged
> > memory in userspace based on platform and virtualization type.
>
> Exactly.
>
> >
> > Changing the default to depend on the driver that added the memory
> > rather than platform type should solve the issue of VMs growing
> > different types of memory device emulation.
>
> Yes, my original proposal (this patch) was to handle it in the kernel
> for known types. But as we learned, there might be some use cases that
> might still require to make a decision in user space.
>
> So providing the user space either with some type hint (auto-online
> vs. standby) or the driver that added it (system vs. hyper-v ...)
> would solve the issue.
Is that not available in the udev event?
Thanks
Michal
next prev parent reply other threads:[~2018-10-04 17:50 UTC|newest]
Thread overview: 144+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 15:03 [PATCH RFC] mm/memory_hotplug: Introduce memory block types David Hildenbrand
2018-09-28 15:03 ` David Hildenbrand
2018-09-28 15:03 ` David Hildenbrand
2018-09-28 17:02 ` Dave Hansen
2018-09-28 17:02 ` Dave Hansen
2018-09-28 17:02 ` Dave Hansen
2018-10-01 9:13 ` David Hildenbrand
2018-10-01 9:13 ` David Hildenbrand
2018-10-01 9:13 ` David Hildenbrand
2018-10-01 9:13 ` David Hildenbrand
2018-10-01 16:24 ` Dave Hansen
2018-10-01 16:24 ` Dave Hansen
2018-10-01 16:24 ` Dave Hansen
2018-10-01 16:24 ` Dave Hansen
2018-10-04 7:48 ` David Hildenbrand
2018-10-04 7:48 ` David Hildenbrand
2018-10-04 7:48 ` David Hildenbrand
2018-10-04 7:48 ` David Hildenbrand
2018-09-28 17:02 ` Dave Hansen
2018-10-01 8:40 ` Michal Hocko
2018-10-01 8:40 ` Michal Hocko
2018-10-01 8:40 ` Michal Hocko
2018-10-01 9:34 ` David Hildenbrand
2018-10-01 9:34 ` David Hildenbrand
2018-10-01 9:34 ` David Hildenbrand
2018-10-02 13:47 ` Michal Hocko
2018-10-02 13:47 ` Michal Hocko
2018-10-02 13:47 ` Michal Hocko
2018-10-02 13:47 ` Michal Hocko
2018-10-02 15:25 ` David Hildenbrand
2018-10-02 15:25 ` David Hildenbrand
2018-10-02 15:25 ` David Hildenbrand
2018-10-02 15:25 ` David Hildenbrand
2018-10-03 13:38 ` Vitaly Kuznetsov
2018-10-03 13:38 ` Vitaly Kuznetsov
2018-10-03 13:38 ` Vitaly Kuznetsov
2018-10-03 13:38 ` Vitaly Kuznetsov
2018-10-03 13:44 ` Michal Hocko
2018-10-03 13:44 ` Michal Hocko
2018-10-03 13:44 ` Michal Hocko
2018-10-03 13:44 ` Michal Hocko
2018-10-03 13:52 ` Vitaly Kuznetsov
2018-10-03 13:52 ` Vitaly Kuznetsov
2018-10-03 13:52 ` Vitaly Kuznetsov
2018-10-03 14:07 ` Dave Hansen
2018-10-03 14:07 ` Dave Hansen
2018-10-03 14:07 ` Dave Hansen
2018-10-03 14:34 ` Vitaly Kuznetsov
2018-10-03 14:34 ` Vitaly Kuznetsov
2018-10-03 14:34 ` Vitaly Kuznetsov
2018-10-03 14:34 ` Vitaly Kuznetsov
2018-10-03 17:14 ` David Hildenbrand
2018-10-03 17:14 ` David Hildenbrand
2018-10-03 17:14 ` David Hildenbrand
2018-10-04 6:19 ` Michal Hocko
2018-10-04 6:19 ` Michal Hocko
2018-10-04 6:19 ` Michal Hocko
2018-10-04 8:13 ` David Hildenbrand
2018-10-04 8:13 ` David Hildenbrand
2018-10-04 8:13 ` David Hildenbrand
2018-10-04 8:13 ` David Hildenbrand
2018-10-04 15:28 ` Michal Suchánek
2018-10-04 15:28 ` Michal Suchánek
2018-10-04 15:28 ` Michal Suchánek
2018-10-04 15:28 ` Michal Suchánek
2018-10-04 15:45 ` David Hildenbrand
2018-10-04 15:45 ` David Hildenbrand
2018-10-04 15:45 ` David Hildenbrand
2018-10-04 15:45 ` David Hildenbrand
2018-10-04 17:50 ` Michal Suchánek [this message]
2018-10-04 17:50 ` Michal Suchánek
2018-10-04 17:50 ` Michal Suchánek
2018-10-05 7:37 ` David Hildenbrand
2018-10-05 7:37 ` David Hildenbrand
2018-10-05 7:37 ` David Hildenbrand
2018-10-05 7:37 ` David Hildenbrand
2018-10-04 17:50 ` Michal Suchánek
2018-10-04 6:19 ` Michal Hocko
2018-10-03 17:14 ` David Hildenbrand
2018-10-03 14:07 ` Dave Hansen
2018-10-03 14:24 ` Michal Hocko
2018-10-03 14:24 ` Michal Hocko
2018-10-03 14:24 ` Michal Hocko
2018-10-03 14:24 ` Michal Hocko
2018-10-03 17:06 ` David Hildenbrand
2018-10-03 17:06 ` David Hildenbrand
2018-10-03 17:06 ` David Hildenbrand
2018-10-03 17:06 ` David Hildenbrand
2018-10-04 8:12 ` David Hildenbrand
2018-10-04 8:12 ` David Hildenbrand
2018-10-04 8:12 ` David Hildenbrand
2018-10-04 8:12 ` David Hildenbrand
2018-10-03 13:52 ` Vitaly Kuznetsov
2018-10-03 13:54 ` Michal Hocko
2018-10-03 13:54 ` Michal Hocko
2018-10-03 13:54 ` Michal Hocko
2018-10-03 13:54 ` Michal Hocko
2018-10-03 17:00 ` David Hildenbrand
2018-10-03 17:00 ` David Hildenbrand
2018-10-03 17:00 ` David Hildenbrand
2018-10-04 6:28 ` Michal Hocko
2018-10-04 6:28 ` Michal Hocko
2018-10-04 6:28 ` Michal Hocko
2018-10-04 7:40 ` David Hildenbrand
2018-10-04 7:40 ` David Hildenbrand
2018-10-04 7:40 ` David Hildenbrand
2018-10-04 7:40 ` David Hildenbrand
2018-10-04 6:28 ` Michal Hocko
2018-10-03 17:00 ` David Hildenbrand
2018-10-01 9:34 ` David Hildenbrand
2018-10-01 8:40 ` Michal Hocko
2018-11-23 11:13 ` David Hildenbrand
2018-11-23 11:13 ` David Hildenbrand
2018-11-23 11:13 ` David Hildenbrand
2018-11-23 18:06 ` Michal Suchánek
2018-11-23 18:06 ` Michal Suchánek
2018-11-23 18:06 ` Michal Suchánek
2018-11-23 18:06 ` Michal Suchánek
2018-11-26 12:30 ` David Hildenbrand
2018-11-26 12:30 ` David Hildenbrand
2018-11-26 12:30 ` David Hildenbrand
2018-11-26 13:33 ` David Hildenbrand
2018-11-26 13:33 ` David Hildenbrand
2018-11-26 13:33 ` David Hildenbrand
2018-11-26 14:20 ` Michal Suchánek
2018-11-26 14:20 ` Michal Suchánek
2018-11-26 14:20 ` Michal Suchánek
2018-11-26 15:59 ` David Hildenbrand
2018-11-26 15:59 ` David Hildenbrand
2018-11-26 15:59 ` David Hildenbrand
2018-11-26 15:59 ` David Hildenbrand
2018-11-27 16:32 ` Michal Suchánek
2018-11-27 16:32 ` Michal Suchánek
2018-11-27 16:32 ` Michal Suchánek
2018-11-27 16:32 ` Michal Suchánek
2018-11-27 16:47 ` David Hildenbrand
2018-11-27 16:47 ` David Hildenbrand
2018-11-27 16:47 ` David Hildenbrand
2018-11-27 16:47 ` David Hildenbrand
2018-11-26 14:20 ` Michal Suchánek
2018-11-26 13:33 ` David Hildenbrand
2018-11-26 12:30 ` David Hildenbrand
2018-11-23 11:13 ` David Hildenbrand
-- strict thread matches above, loose matches on Subject: below --
2018-09-28 15:03 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=20181004195010.3616fc40@kitsune.suse.cz \
--to=msuchanek@suse.de \
--cc=dalias@libc.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kstewart@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-sh@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=mike.travis@hpe.com \
--cc=mikey@neuling.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=pavel.tatashin@microsoft.com \
--cc=peterz@infradead.org \
--cc=rashmica.g@gmail.com \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sthemmin@microsoft.com \
--cc=xen-devel@lists.xenproject.org \
--cc=ysato@users.sourceforge.jp \
/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.