Linux-HyperV Archive on lore.kernel.org
 help / color / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: lantianyu1986@gmail.com, dan.j.williams@intel.com,
	dave.hansen@linux.intel.com, mingo@kernel.org,
	mpe@ellerman.id.au, pasha.tatashin@soleen.com, osalvador@suse.de,
	richardw.yang@linux.intel.com, Tianyu.Lan@microsoft.com,
	christophe.leroy@c-s.fr, bp@suse.de, rdunlap@infradead.org,
	michael.h.kelley@microsoft.com, kys@microsoft.com,
	sashal@kernel.org
Cc: linux-kernel@vger.kernel.org, vkuznets@redhat.com,
	linux-hyperv@vger.kernel.org
Subject: Re: [PATCH] mm/resource: Move child to new resource when release mem region.
Date: Thu, 10 Oct 2019 07:29:36 -0700
Message-ID: <77e08231-0687-8d8d-0faf-c490a8b510d4@intel.com> (raw)
In-Reply-To: <20191010072856.20079-1-Tianyu.Lan@microsoft.com>

On 10/10/19 12:28 AM, lantianyu1986@gmail.com wrote:
> When release mem region, old mem region may be splited to
> two regions. Current allocate new struct resource for high
> end mem region but not move child resources whose ranges are
> in the high end range to new resource. When adjust old mem
> region's range, adjust_resource() detects child region's range
> is out of new range and return error. Move child resources to
> high end resource before adjusting old mem range.

From the comment, it appears the old code intended to have the behavior
that you are changing.  Could you explain _why_ this has become a
problem for you?


  reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10  7:28 lantianyu1986
2019-10-10 14:29 ` Dave Hansen [this message]
2019-10-11 14:53   ` Tianyu Lan

Reply instructions:

You may reply publically 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=77e08231-0687-8d8d-0faf-c490a8b510d4@intel.com \
    --to=dave.hansen@intel.com \
    --cc=Tianyu.Lan@microsoft.com \
    --cc=bp@suse.de \
    --cc=christophe.leroy@c-s.fr \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=kys@microsoft.com \
    --cc=lantianyu1986@gmail.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.h.kelley@microsoft.com \
    --cc=mingo@kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=osalvador@suse.de \
    --cc=pasha.tatashin@soleen.com \
    --cc=rdunlap@infradead.org \
    --cc=richardw.yang@linux.intel.com \
    --cc=sashal@kernel.org \
    --cc=vkuznets@redhat.com \
    /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

Linux-HyperV Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-hyperv/0 linux-hyperv/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-hyperv linux-hyperv/ https://lore.kernel.org/linux-hyperv \
		linux-hyperv@vger.kernel.org
	public-inbox-index linux-hyperv

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-hyperv


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git