[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Baffled by multipage_allocation_permitted()


  • To: Jan Beulich <JBeulich@xxxxxxxxxx>, Dave McCracken <dcm@xxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Tue, 16 Jun 2009 10:41:46 +0100
  • Cc: Xen Developers List <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 16 Jun 2009 02:42:29 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcnuY5nf3gGayPR6RWup3+knoGraTQAAw/y8
  • Thread-topic: [Xen-devel] Baffled by multipage_allocation_permitted()

On 16/06/2009 10:19, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

>> We can just get rid of it I think. There are arguably worse other things we
>> already allow, like any guest can allocate low memory by specifying a small
>> value of XENMEMF_address_bits().
> 
> Wouldn't it be better to tighten things rather than relaxing them?

It'll need policy to be expressed and pushed down from the toolstack
somehow. Noone's really thought about it too much. In this case I think I
will keep the checking macro actually, and simply disallow allocations
greater than order-9 (2MB superpage) unless the domain has direct hardware
access capability.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.