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: <21d7e9970803310421k67f1a697s8ffb5a4eef71c605@mail.gmail.com>
Date:	Mon, 31 Mar 2008 21:21:19 +1000
From:	"Dave Airlie" <airlied@...il.com>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	"Dave Airlie" <airlied@...hat.com>, linux-kernel@...r.kernel.org,
	tglx@...utronix.de, mingo@...hat.com, arjan@...ux.intel.com,
	thomas@...gstengraphics.com
Subject: Re: [PATCH] x86: create array based interface to change page attribute

On Mon, Mar 31, 2008 at 5:25 PM, Andi Kleen <andi@...stfloor.org> wrote:
> Dave Airlie <airlied@...hat.com> writes:
>  >
>  > +#define CPA_FLUSHTLB 1
>  > +#define CPA_ARRAY 2
>
>  I don't think CPA_ARRAY should be a separate case. Rather single
>  page flushing should be an array with only a single entry. pageattr
>  is already very complex, no need to make add more special cases.

I thought about this but the current interface takes a start address
and number of pages from that point to cpa,
the array interface takes an array of page sized pages.

I don't really think we need to generate an array in the first case
with all the pages in it..

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ