From: Dave Hansen <haveblue@us.ibm.com>
To: Sourav Sen <souravs@india.hp.com>
Cc: 'Greg KH' <greg@kroah.com>,
Matt_Domsch@dell.com,
Matthew E Tolentino <matthew.e.tolentino@intel.com>,
linux-ia64@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: [2.6.6 PATCH] Exposing EFI memory map
Date: Tue, 11 May 2004 15:42:01 +0000 [thread overview]
Message-ID: <1084290121.1091.62.camel@nighthawk> (raw)
In-Reply-To: <00b201c43766$7646a670$39624c0f@india.hp.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Sourav Sen <souravs@india.hp.com>
Cc: "'Greg KH'" <greg@kroah.com>,
Matt_Domsch@dell.com,
Matthew E Tolentino <matthew.e.tolentino@intel.com>,
linux-ia64@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: [2.6.6 PATCH] Exposing EFI memory map
Date: Tue, 11 May 2004 08:42:01 -0700 [thread overview]
Message-ID: <1084290121.1091.62.camel@nighthawk> (raw)
In-Reply-To: <00b201c43766$7646a670$39624c0f@india.hp.com>
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
next prev parent reply other threads:[~2004-05-11 15:42 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-06 8:52 [2.6.6 PATCH] Exposing EFI memory map Sourav Sen
2004-05-06 8:53 ` Sourav Sen
2004-05-06 10:44 ` Christoph Hellwig
2004-05-06 10:44 ` Christoph Hellwig
2004-05-06 11:59 ` Matthew Wilcox
2004-05-06 11:59 ` Matthew Wilcox
2004-05-06 12:18 ` Arjan van de Ven
2004-05-06 12:18 ` Arjan van de Ven
2004-05-06 13:27 ` Matthew Wilcox
2004-05-06 13:27 ` Matthew Wilcox
2004-05-06 14:00 ` Dave Hansen
2004-05-06 14:00 ` Dave Hansen
2004-05-06 14:09 ` Arjan van de Ven
2004-05-06 14:09 ` Arjan van de Ven
2004-05-06 14:09 ` Christoph Hellwig
2004-05-06 14:09 ` Christoph Hellwig
2004-05-06 12:46 ` Matt Domsch
2004-05-06 12:46 ` Matt Domsch
2004-05-06 13:20 ` Sourav Sen
2004-05-06 13:32 ` Sourav Sen
2004-05-06 15:08 ` Bjorn Helgaas
2004-05-06 15:08 ` Bjorn Helgaas
2004-05-06 16:25 ` Sourav Sen
2004-05-06 16:37 ` Sourav Sen
2004-05-06 16:49 ` Dave Hansen
2004-05-06 16:49 ` Dave Hansen
2004-05-06 13:23 ` Luck, Tony
2004-05-06 13:23 ` Luck, Tony
2004-05-06 16:14 ` Tolentino, Matthew E
2004-05-06 16:14 ` Tolentino, Matthew E
2004-05-06 16:40 ` Greg KH
2004-05-06 16:40 ` Greg KH
2004-05-07 9:45 ` Sourav Sen
2004-05-07 9:57 ` Sourav Sen
2004-05-07 21:49 ` Greg KH
2004-05-07 21:49 ` Greg KH
2004-05-11 14:44 ` Sourav Sen
2004-05-11 14:56 ` Sourav Sen
2004-05-11 15:42 ` Dave Hansen [this message]
2004-05-11 15:42 ` Dave Hansen
2004-05-12 10:24 ` Sourav Sen
2004-05-12 10:36 ` Sourav Sen
2004-05-12 16:15 ` Dave Hansen
2004-05-12 16:15 ` Dave Hansen
2004-05-13 14:10 ` Sourav Sen
2004-05-13 14:22 ` Sourav Sen
2004-05-13 15:32 ` Dave Hansen
2004-05-13 15:32 ` Dave Hansen
2004-05-06 18:47 ` Tolentino, Matthew E
2004-05-06 18:47 ` Tolentino, Matthew E
2004-05-06 18:57 ` Dave Hansen
2004-05-06 18:57 ` Dave Hansen
2004-05-06 20:54 ` Tolentino, Matthew E
2004-05-06 20:54 ` Tolentino, Matthew E
2004-05-06 21:44 ` [Lhms-devel] " Dave Hansen
2004-05-06 21:44 ` Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2004-05-06 9:18 Sourav Sen
2004-05-06 9:30 ` Sourav Sen
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=1084290121.1091.62.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=Matt_Domsch@dell.com \
--cc=greg@kroah.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.e.tolentino@intel.com \
--cc=souravs@india.hp.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
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.