From: Michal Hocko <mhocko@kernel.org>
To: David Hildenbrand <david@redhat.com>
Cc: "Roger Pau Monné" <roger.pau@citrix.com>,
"Jürgen Groß" <jgross@suse.com>,
linux-kernel@vger.kernel.org,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
xen-devel@lists.xenproject.org, linux-mm@kvack.org
Subject: Re: [PATCH 3/3] memory: introduce an option to force onlining of hotplug memory
Date: Fri, 24 Jul 2020 09:28:21 +0200 [thread overview]
Message-ID: <20200724072821.GD4061@dhcp22.suse.cz> (raw)
In-Reply-To: <4ff380e9-4b16-4cd0-7753-c2b89bd8ac6b@redhat.com>
On Thu 23-07-20 19:39:54, David Hildenbrand wrote:
[...]
> Yeah, might require some code churn. It just feels wrong to involve
> buddy concepts (e.g., onlining pages, calling memory notifiers, exposing
> memory block devices) and introducing hacks (forced onlining) just to
> get a memmap+identity mapping+iomem resource. I think reserving such a
> region during boot as suggested is the easiest approach, but I am
> *absolutely* not an expert on all these XEN-specific things :)
I am late to the discussion but FTR I completely agree.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2020-07-24 7:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200723084523.42109-1-roger.pau@citrix.com>
2020-07-23 8:45 ` [PATCH 3/3] memory: introduce an option to force onlining of hotplug memory Roger Pau Monne
2020-07-23 11:37 ` David Hildenbrand
2020-07-23 11:52 ` David Hildenbrand
2020-07-23 12:23 ` Roger Pau Monné
2020-07-23 12:28 ` Jürgen Groß
2020-07-23 12:31 ` David Hildenbrand
2020-07-23 13:08 ` Roger Pau Monné
2020-07-23 13:14 ` David Hildenbrand
2020-07-23 13:25 ` Roger Pau Monné
2020-07-23 13:20 ` Jürgen Groß
2020-07-23 13:39 ` Roger Pau Monné
2020-07-23 13:49 ` Jürgen Groß
2020-07-23 13:22 ` David Hildenbrand
2020-07-23 13:47 ` David Hildenbrand
2020-07-23 13:53 ` Jürgen Groß
2020-07-23 13:59 ` Roger Pau Monné
2020-07-23 15:10 ` Jürgen Groß
2020-07-23 16:03 ` Andrew Cooper
2020-07-23 16:22 ` Roger Pau Monné
2020-07-23 17:39 ` David Hildenbrand
2020-07-24 7:28 ` Michal Hocko [this message]
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=20200724072821.GD4061@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=david@redhat.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).