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: <1354896579.3224.75.camel@bling.home>
Date:	Fri, 07 Dec 2012 09:09:39 -0700
From:	Alex Williamson <alex.williamson@...hat.com>
To:	Takuya Yoshikawa <takuya.yoshikawa@...il.com>
Cc:	mtosatti@...hat.com, gleb@...hat.com, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org
Subject: Re: [PATCH 10/10] kvm: Increase user memory slots on x86 to 125

On Fri, 2012-12-07 at 23:02 +0900, Takuya Yoshikawa wrote:
> On Thu, 06 Dec 2012 15:21:26 -0700
> Alex Williamson <alex.williamson@...hat.com> wrote:
> 
> > With the 3 private slots, this gives us a nice round 128 slots total.
> 
> So I think this patch needs to be applied after resolving the
> slot_bitmap issue.  We may not need to protect slots with large
> slot id values, but still it's possible to do so.
> 
> Taking into account that the merge window is so close that this
> patch set should be targeted for 3.9, it may be possible to do
> the work timely: I will post my patch series next week if possible.

This obviously increases the slot_bitmap, actually only doubles it since
it's an unsigned long and we're only using 36 bits, but why should
removing the slot_bitmap gate this series?  Thanks,

Alex

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