All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Sudarshan Rajagopalan <sudaraja@codeaurora.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	David Hildenbrand <david@redhat.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-kernel@vger.kernel.org, Steven Price <steven.price@arm.com>,
	Suren Baghdasaryan <surenb@google.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Pratik Patel <pratikp@codeaurora.org>
Subject: Re: [RFC] depopulate_range_driver_managed() for removing page-table mappings for hot-added memory blocks
Date: Sat, 14 Nov 2020 10:28:53 +0000	[thread overview]
Message-ID: <20201114102853.GA8618@infradead.org> (raw)
In-Reply-To: <bb30aa44d367ad217e9c877eba7b0a12@codeaurora.org>

On Fri, Nov 13, 2020 at 06:41:22PM -0800, Sudarshan Rajagopalan wrote:
> 
> Hello,
> 
> When memory blocks are removed, along with removing the memmap entries,
> memory resource and memory block devices, the arch specific
> arch_remove_memory() is called which takes care of tearing down the
> page-tables.
> 
> Suppose there???s a usecase where the removed memory blocks will be added
> back into the system at later point,

Stop this crap.  If you have a use case post the actual use here,
including code and specs.  If you don't have that don't waste peoples
time on your pipe dream.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Sudarshan Rajagopalan <sudaraja@codeaurora.org>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
	David Hildenbrand <david@redhat.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Steven Price <steven.price@arm.com>,
	Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Suren Baghdasaryan <surenb@google.com>,
	Pratik Patel <pratikp@codeaurora.org>
Subject: Re: [RFC] depopulate_range_driver_managed() for removing page-table mappings for hot-added memory blocks
Date: Sat, 14 Nov 2020 10:28:53 +0000	[thread overview]
Message-ID: <20201114102853.GA8618@infradead.org> (raw)
In-Reply-To: <bb30aa44d367ad217e9c877eba7b0a12@codeaurora.org>

On Fri, Nov 13, 2020 at 06:41:22PM -0800, Sudarshan Rajagopalan wrote:
> 
> Hello,
> 
> When memory blocks are removed, along with removing the memmap entries,
> memory resource and memory block devices, the arch specific
> arch_remove_memory() is called which takes care of tearing down the
> page-tables.
> 
> Suppose there???s a usecase where the removed memory blocks will be added
> back into the system at later point,

Stop this crap.  If you have a use case post the actual use here,
including code and specs.  If you don't have that don't waste peoples
time on your pipe dream.

  reply	other threads:[~2020-11-14 10:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14  2:41 [RFC] depopulate_range_driver_managed() for removing page-table mappings for hot-added memory blocks Sudarshan Rajagopalan
2020-11-14  2:41 ` Sudarshan Rajagopalan
2020-11-14 10:28 ` Christoph Hellwig [this message]
2020-11-14 10:28   ` Christoph Hellwig
2020-11-17 14:58   ` David Hildenbrand
2020-11-17 14:58     ` 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=20201114102853.GA8618@infradead.org \
    --to=hch@infradead.org \
    --cc=anshuman.khandual@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=david@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pratikp@codeaurora.org \
    --cc=steven.price@arm.com \
    --cc=sudaraja@codeaurora.org \
    --cc=surenb@google.com \
    --cc=will@kernel.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.