linux-kernel - Re: [patch 3/9] Guest page hinting: volatile page cache.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1157122667.28577.69.camel@localhost.localdomain>
Date:	Fri, 01 Sep 2006 07:57:47 -0700
From:	Dave Hansen <haveblue@...ibm.com>
To:	Martin Schwidefsky <schwidefsky@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org,
	akpm@...l.org, nickpiggin@...oo.com.au, frankeh@...son.ibm.com,
	rhim@...gateh.edu, Andy Whitcroft <apw@...dowen.org>
Subject: Re: [patch 3/9] Guest page hinting: volatile page cache.

On Fri, 2006-09-01 at 13:09 +0200, Martin Schwidefsky wrote:
> +#define PG_state_change                21      /* HV page state is changing. */
> +#define PG_discarded           22      /* HV page has been discarded. */ 

We're already desperately short on page flags on 32-bit architectures.
It seems a wee bit silly to add two arch-generic flags for what is a
very specialized arch-specific feature at this point.

I know that there are 32-bit s390 kernels, but would this be a
reasonable feature to restrict to only 64-bit kernels?  That might be a
decent compromise.

-- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/