From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH] Sysfs Interface for balloon driver Date: Wed, 20 Sep 2006 18:40:15 -0500 Message-ID: <4511D15F.90904@us.ibm.com> References: <20060920011235.GA7931@totally.trollied.org> <00c401c6dc60$f22303f0$4c87380a@ad.spf.cl.nec.co.jp><20060920152006.GA32328@totally.trollied.org> <451187D9.7080609@us.ibm.com> <3AAA99889D105740BE010EB6D5A5A3B202A2AC@paddington.ad.cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <3AAA99889D105740BE010EB6D5A5A3B202A2AC@paddington.ad.cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: Satoshi Uchida , xen-devel@lists.xensource.com, John Levon List-Id: xen-devel@lists.xenproject.org Ian Pratt wrote: >> Personally, I think the ballooning information ought to be exposed as >> > a > >> module parameter and appear in the sysfs module path. I've always >> thought /sys/hypervisor ought to expose information from the >> > hypervisor. > > I don't think the memory target stuff is a driver. 'balloon' should not > appear in the name anyhow -- this stuff is getting ever more closely > integrated with Linux's core memory management anyhow, it's definitely > not a driver. > > I sort of slightly buy Anthony's argument that /sys/hypervisor should > just expose information about the hypervisor. > > /sys/devices/system/memory/{target,current,max,..} ? > Works for me. Regards, Anthony Liguori > Ian > > > >