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: <20090210143158.056bbd43@osiris.boeblingen.de.ibm.com>
Date:	Tue, 10 Feb 2009 14:31:58 +0100
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Glauber Costa <glommer@...hat.com>
Cc:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org, mingo@...e.hu,
	avi@...hat.com, akataria@...are.com
Subject: Re: [PATCH 2/2] show hypervisor information on sysfs

On Tue, 10 Feb 2009 11:20:23 -0200
Glauber Costa <glommer@...hat.com> wrote:
> > Anyway, just wanted to make you aware of what might come next.
> 
> Why wouldn't it be extensible? So far, I've only added an attribute. But we
> can easily add others, and directories with even more attributes if we must.

Oh, sure it's easily extensible, the question is if the first attribute
you now add will be at the right place. That is: is all information
about the 1st level hypervisor supposed to be found in /sys/hypervisor
or should it be in a subdirectory? E.g. /sys/hypervisor/level1 or
something like that.
But adding your attribute won't hurt. The worst case is that it gets
duplicated.
--
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