From: Toshi Kani <toshi.kani@hp.com>
To: Hush Bensen <hush.bensen@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, x86@kernel.org, dave@sr71.net,
kosaki.motohiro@gmail.com, isimatu.yasuaki@jp.fujitsu.com,
tangchen@cn.fujitsu.com, vasilis.liaskovitis@profitbricks.com
Subject: Re: [PATCH v2] mm/hotplug, x86: Disable ARCH_MEMORY_PROBE by default
Date: Thu, 25 Jul 2013 09:47:20 -0600 [thread overview]
Message-ID: <1374767240.16322.228.camel@misato.fc.hp.com> (raw)
In-Reply-To: <51F06E87.1060902@gmail.com>
On Thu, 2013-07-25 at 08:17 +0800, Hush Bensen wrote:
:
> Thanks for your explaination, very useful for me. ;-) Btw, what's the
> eject method done?
On bare metal, the eject method makes a target device electrically
isolated and physically removable. On virtualized environment, the
eject method makes a target device unassigned and released.
> Could you give me the calltrace of add_memory and remove_memory? I
> don't have machine support hotplug, but I hope to investigate how
> ACPI part works for memory hotplug. ;-)
Here you go.
[ 84.883517] [<ffffffff8153e8a4>] add_memory+0x24/0x185
[ 84.883525] [<ffffffff812ca331>] ? acpi_get_pxm+0x2b/0x4e
[ 84.883533] [<ffffffff81303418>] acpi_memory_device_add+0x144/0x274
[ 84.883539] [<ffffffff812c1b25>] acpi_bus_device_attach+0x80/0xd9
[ 84.883545] [<ffffffff812c2b65>] acpi_bus_scan+0x65/0x9f
[ 84.883551] [<ffffffff812c2c1d>] acpi_scan_bus_device_check
+0x7e/0x10f
[ 84.883556] [<ffffffff812c2cc1>] acpi_scan_device_check+0x13/0x15
[ 84.883562] [<ffffffff812bbdab>] acpi_os_execute_deferred+0x25/0x32
[ 84.883568] [<ffffffff81057cbc>] process_one_work+0x229/0x3d3
[ 84.883573] [<ffffffff81057bfa>] ? process_one_work+0x167/0x3d3
[ 84.883579] [<ffffffff81058248>] worker_thread+0x133/0x200
[ 84.883584] [<ffffffff81058115>] ? rescuer_thread+0x280/0x280
[ 84.883591] [<ffffffff8105e0c3>] kthread+0xb1/0xb9
[ 84.883598] [<ffffffff8105e012>] ? __kthread_parkme+0x65/0x65
[ 84.883604] [<ffffffff81556c9c>] ret_from_fork+0x7c/0xb0
[ 84.883610] [<ffffffff8105e012>] ? __kthread_parkme+0x65/0x65
[ 129.586622] [<ffffffff8153f4b1>] remove_memory+0x22/0x85
[ 129.586627] [<ffffffff813031c6>] acpi_memory_device_remove+0x77/0xa7
[ 129.586631] [<ffffffff812c0f95>] acpi_bus_device_detach+0x3d/0x5e
[ 129.586634] [<ffffffff812c0ff8>] acpi_bus_trim+0x42/0x7a
[ 129.586637] [<ffffffff812c1587>] acpi_scan_hot_remove+0x1ba/0x261
[ 129.586641] [<ffffffff812c16ce>] acpi_bus_device_eject+0xa0/0xd0
[ 129.586644] [<ffffffff812bbdab>] acpi_os_execute_deferred+0x25/0x32
[ 129.586648] [<ffffffff81057cbc>] process_one_work+0x229/0x3d3
[ 129.586652] [<ffffffff81057bfa>] ? process_one_work+0x167/0x3d3
[ 129.586655] [<ffffffff81058248>] worker_thread+0x133/0x200
[ 129.586658] [<ffffffff81058115>] ? rescuer_thread+0x280/0x280
[ 129.586663] [<ffffffff8105e0c3>] kthread+0xb1/0xb9
[ 129.586667] [<ffffffff8105e012>] ? __kthread_parkme+0x65/0x65
[ 129.586671] [<ffffffff81556c9c>] ret_from_fork+0x7c/0xb0
[ 129.586675] [<ffffffff8105e012>] ? __kthread_parkme+0x65/0x65
-Toshi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-07-25 15:48 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 17:47 Toshi Kani
2013-07-19 19:30 ` KOSAKI Motohiro
2013-07-19 19:35 ` Toshi Kani
2013-07-22 8:37 ` Ingo Molnar
2013-07-22 17:12 ` Toshi Kani
2013-07-22 20:57 ` KOSAKI Motohiro
2013-07-22 21:04 ` Dave Hansen
2013-07-23 0:34 ` Toshi Kani
2013-07-23 8:01 ` Ingo Molnar
2013-07-23 20:45 ` Toshi Kani
2013-07-23 20:59 ` Dave Hansen
2013-07-23 21:34 ` Toshi Kani
2013-07-24 0:18 ` Hush Bensen
2013-07-24 16:02 ` Toshi Kani
2013-07-25 0:17 ` Hush Bensen
2013-07-25 15:47 ` Toshi Kani [this message]
2013-07-25 0:44 ` Hush Bensen
2013-07-25 0:56 ` Hush Bensen
2013-07-25 3:08 ` Yasuaki Ishimatsu
2013-07-25 3:34 ` Hush Bensen
2013-07-25 4:55 ` Yasuaki Ishimatsu
2013-07-24 4:20 ` Ingo Molnar
2013-07-24 16:58 ` Toshi Kani
2013-07-25 21:38 ` Ingo Molnar
2013-07-25 22:36 ` Toshi Kani
2013-07-23 0:24 ` Yasuaki Ishimatsu
2013-07-23 0:45 ` Toshi Kani
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=1374767240.16322.228.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=akpm@linux-foundation.org \
--cc=dave@sr71.net \
--cc=hush.bensen@gmail.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=tangchen@cn.fujitsu.com \
--cc=vasilis.liaskovitis@profitbricks.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox