Re: [PATCH] [RESEND] x86_64: add memory hotremove config option

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Andi Kleen
Date: Friday, September 5, 2008 - 11:04 am

Gary Hade <garyhade@us.ibm.com> writes:

You forgot to describe how you tested it? Does it actually work.
And why do you want to do it it? What's the use case?

The general understanding was that it doesn't work very well on a real
machine at least because it cannot be controlled how that memory maps
to real pluggable hardware (and you cannot completely empty a node at runtime)
and a Hypervisor would likely use different interfaces anyways.

-Andi
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] [RESEND] x86_64: add memory hotremove config o ..., Andi Kleen, (Fri Sep 5, 11:04 am)
[PATCH] Cleanup to make remove_memory() arch neutral, Badari Pulavarty, (Mon Sep 8, 2:52 pm)
[PATCH] x86: add memory hotremove config option, Badari Pulavarty, (Mon Sep 8, 2:56 pm)
Re: [PATCH] Cleanup to make remove_memory() arch neutral, Badari Pulavarty, (Tue Sep 9, 8:12 am)