All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS asm/mman.h and MADV_HWPOISON
Date: Thu, 26 Nov 2009 18:30:07 +0000	[thread overview]
Message-ID: <20091126183007.GA19853@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0911252356300.31853@digraph.polyomino.org.uk>

On Wed, Nov 25, 2009 at 11:57:07PM +0000, Joseph S. Myers wrote:

> In the course of updating glibc ports's bits/mman.h files for new MADV_* 
> definitions, I noticed that arch/mips/include/asm/mman.h does not define 
> MADV_HWPOISON, although architectures using asm-generic/mman.h get that 
> definition automatically.  Should I take it that this is an oversight and 
> that a definition of MADV_HWPOISON will be added with value 100, or is 
> there some reason for it not to be defined for MIPS or for it to have a 
> different value?

Just an omission.  Thanks for reporting.  I've just checked in below
patch.

  Ralf

From: Ralf Baechle <ralf@linux-mips.org>

MIPS: Add missing definition for MADV_HWPOISON.

Signed-off-by: Ralf Baechle <ralf@linux-mips.org>

diff --git a/arch/mips/include/asm/mman.h b/arch/mips/include/asm/mman.h
index a2250f3..c892bfb 100644
--- a/arch/mips/include/asm/mman.h
+++ b/arch/mips/include/asm/mman.h
@@ -75,6 +75,7 @@
 
 #define MADV_MERGEABLE   12		/* KSM may merge identical pages */
 #define MADV_UNMERGEABLE 13		/* KSM may not merge identical pages */
+#define MADV_HWPOISON    100		/* poison a page for testing */
 
 /* compatibility flags */
 #define MAP_FILE	0

      reply	other threads:[~2009-11-26 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 23:57 MIPS asm/mman.h and MADV_HWPOISON Joseph S. Myers
2009-11-26 18:30 ` Ralf Baechle [this message]

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=20091126183007.GA19853@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=joseph@codesourcery.com \
    --cc=linux-mips@linux-mips.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.