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]
Date:	Fri, 28 Mar 2008 09:07:11 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	LKML <linux-kernel@...r.kernel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Yasunori Goto <y-goto@...fujitsu.com>,
	Christoph Lameter <clameter@....com>,
	Dave Hansen <dave@...ux.vnet.ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0 of 4] [RFC] hotplug memory: minor updates

Ingo Molnar wrote:
> the x86 bits look small and trivial, so i'd suggest you get this into 
> -mm to after all the other VM patches, because this seems primarily a VM 
> issue.
>   

I would do that, but I'm planning on posting some Xen balloon driver 
patches which depend on at least one of these patches.

I'll drop "hotplug-memory: adding non-section-aligned memory is bad" 
because it was just warnings and it was NACKed.  "hotplug-memory: add 
add_memory_resource()" is just a refactor, and should be a noop as far 
as the existing add_memory() is concerned.


> i've applied #3 to x86.git straight away. Does #4 have dependencies on 
> the other patches? I suspect it does so it cannot be applied standalone.
>   

You mean the "paravirt_ops: don't steal memory resources in 
paravirt_disable_iospace"?  That shouldn't have any dependencies.  It's 
the only patch in my queue which even references that file.  Rusty said 
he picked it up too; are you exchanging patches with him?

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