netdev - Re: [PATCH 1/1] eHEA: Introducing support vor DLPAR memory add

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] [day] [month] [year] [list]

Message-ID: <469BEA5F.5050508@garzik.org>
Date:	Mon, 16 Jul 2007 17:59:59 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Thomas Klein <osstklei@...ibm.com>
CC:	Christoph Raisch <raisch@...ibm.com>,
	Jan-Bernd Themann <ossthema@...ibm.com>,
	Jan-Bernd Themann <themann@...ibm.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-ppc <linuxppc-dev@...abs.org>,
	Marcus Eder <meder@...ibm.com>,
	netdev <netdev@...r.kernel.org>,
	Thomas Klein <tklein@...ibm.com>,
	Stefan Roscher <ossrosch@...ux.vnet.ibm.com>
Subject: Re: [PATCH 1/1] eHEA: Introducing support vor DLPAR memory add

Thomas Klein wrote:
> This patch adds support for DLPAR memory add to the eHEA driver. To detect
> whether memory was added the driver uses its own memory mapping table and
> checks for kernel addresses whether they're located in already known memory
> sections. If not the function ehea_rereg_mrs() is triggered which performs
> a rebuild of the mapping table and a re-registration of the global memory
> region.
> 
> Signed-off-by: Thomas Klein <tklein@...ibm.com>
> ---
> 
>  drivers/net/ehea/ehea.h      |   23 +++++--
>  drivers/net/ehea/ehea_main.c |  144 +++++++++++++++++++++++++++++++++++----
>  drivers/net/ehea/ehea_phyp.h |    3 +
>  drivers/net/ehea/ehea_qmr.c  |  156 ++++++++++++++++++++++++++++++------------
>  drivers/net/ehea/ehea_qmr.h  |   14 +++-
>  5 files changed, 275 insertions(+), 65 deletions(-)

applied


-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html