Messages in this thread | | | Subject | RE: [2.6.6 PATCH] Exposing EFI memory map | From | Dave Hansen <> | Date | Tue, 11 May 2004 08:42:01 -0700 |
| |
On Tue, 2004-05-11 at 07:44, Sourav Sen wrote: > + I think you should address the other issues in this thread before > + worrying about the sysfs interface (why have this at all, incorrect > + data for hotplug mem, etc.) > + > I did not hear whether the idea of updating efi memory map on a > hotplug is good or bad. In any case, can somebody tell me to how do > I get the available physical range map (only the ranges that VM is > using at a given point in time) from userland. I believe I outlined > a legitimate requirement earlier in this thread :-)
Let me paraphrase: exporting generic information in an architecture or firmware-specific way in sysfs is bad.
I apologize, but I think I missed yout legitimate requirements earlier in the thread. Could you briefly remind me?
-- Dave
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |