All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Mark Gross <mgross@linux.intel.com>
Cc: linux-mm@kvack.org, mark.gross@intel.com,
	linux-pm@lists.osdl.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, neelam.chandwani@intel.com
Subject: Re: [RFC] [PATCH] Power Managed memory base enabling
Date: Mon, 26 Mar 2007 12:48:46 +0000	[thread overview]
Message-ID: <20070326124846.GC11088@ucw.cz> (raw)
In-Reply-To: <20070305181826.GA21515@linux.intel.com>

Hi!

> It implements a convention on the 4 bytes of "Proximity Domain ID"
> within the SRAT memory affinity structure as defined in ACPI3.0a.  If
> bit 31 is set, then the memory range represented by that PXM is assumed
> to be power managed.  We are working on defining a "standard" for
> identifying such memory areas as power manageable and progress committee
> based.  
...
> More will be done, but for now we would like to get this base enabling
> into the upstream kernel as an initial step.

I'm not sure if the hack above does not disqualify it from
mainstream...

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Mark Gross <mgross@linux.intel.com>
Cc: linux-mm@kvack.org, linux-pm@lists.osdl.org,
	mark.gross@intel.com, akpm@linux-foundation.org,
	torvalds@linux-foundation.org, neelam.chandwani@intel.com
Subject: Re: [linux-pm] [RFC] [PATCH] Power Managed memory base enabling
Date: Mon, 26 Mar 2007 12:48:46 +0000	[thread overview]
Message-ID: <20070326124846.GC11088@ucw.cz> (raw)
In-Reply-To: <20070305181826.GA21515@linux.intel.com>

Hi!

> It implements a convention on the 4 bytes of "Proximity Domain ID"
> within the SRAT memory affinity structure as defined in ACPI3.0a.  If
> bit 31 is set, then the memory range represented by that PXM is assumed
> to be power managed.  We are working on defining a "standard" for
> identifying such memory areas as power manageable and progress committee
> based.  
...
> More will be done, but for now we would like to get this base enabling
> into the upstream kernel as an initial step.

I'm not sure if the hack above does not disqualify it from
mainstream...

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

--
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>

  parent reply	other threads:[~2007-03-26 12:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05 18:18 [RFC] [PATCH] Power Managed memory base enabling Mark Gross
2007-03-05 18:18 ` Mark Gross
2007-03-06  1:26 ` KAMEZAWA Hiroyuki
2007-03-06  1:26   ` KAMEZAWA Hiroyuki
2007-03-06 15:54   ` Mark Gross
2007-03-06 15:54     ` Mark Gross
2007-03-06 15:09 ` David Rientjes
2007-03-06 15:09   ` David Rientjes
2007-03-06 16:47   ` Mark Gross
2007-03-06 16:47     ` Mark Gross
2007-03-06 17:12     ` David Rientjes
2007-03-06 17:12       ` David Rientjes
2007-03-06 17:20       ` Mark Gross
2007-03-06 17:20         ` Mark Gross
2007-03-06 17:33         ` David Rientjes
2007-03-06 17:33           ` David Rientjes
2007-03-07  2:40     ` David Rientjes
2007-03-07  2:40       ` David Rientjes
2007-03-09 20:53       ` Mark Gross
2007-03-09 20:53         ` Mark Gross
2007-03-09 21:27         ` David Rientjes
2007-03-09 21:27           ` David Rientjes
2007-03-09 21:26           ` Mark Gross
2007-03-09 21:26             ` Mark Gross
2007-03-26 12:48 ` Pavel Machek [this message]
2007-03-26 12:48   ` [linux-pm] " Pavel Machek

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=20070326124846.GC11088@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=mark.gross@intel.com \
    --cc=mgross@linux.intel.com \
    --cc=neelam.chandwani@intel.com \
    --cc=torvalds@linux-foundation.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 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.