From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 7
Date: Tue, 07 Feb 2012 10:53:24 -0600
Message-ID: <4F315704.1040306@codemonkey.ws>
References: <87ehu7pxvf.fsf@elfo.elfo> <4F312AFC.6020908@suse.de>	<4F312C8A.9080700@redhat.com> <4F313BA8.9070601@codemonkey.ws>	<4F31417F.2000102@redhat.com> <4F31544B.8040808@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15;
	format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: Paolo Bonzini <pbonzini@redhat.com>, quintela@redhat.com,
	Developers qemu-devel <qemu-devel@nongnu.org>,
	KVM devel mailing list <kvm@vger.kernel.org>
To: =?ISO-8859-15?Q?Andreas_F=E4rber?= <afaerber@suse.de>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail-pw0-f46.google.com ([209.85.160.46]:51714 "EHLO
	mail-pw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751507Ab2BGQxc (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 7 Feb 2012 11:53:32 -0500
Received: by pbdu11 with SMTP id u11so6032866pbd.19
        for <kvm@vger.kernel.org>; Tue, 07 Feb 2012 08:53:31 -0800 (PST)
In-Reply-To: <4F31544B.8040808@suse.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 02/07/2012 10:41 AM, Andreas F=E4rber wrote:
> Am 07.02.2012 16:21, schrieb Paolo Bonzini:
>> BTW, I would like to change /i440fx to /devices/i440fx, so that we w=
ill
>> have clean namespaces:
>>
>> /block
>>      ...
>> /chardev
>>      ...
>> /clocks
>>      ...
>> /devices
>>      /peripheral
>>          ...                 # named devices created with -device
>>      /peripheral-anon
>>          /child[...]         # unnamed devices created with -device
>>      /default
>>          /child[...]         # created with qdev_create
>
> I don't like that, I prefer /i440fx over /devices/i440fx. I don't min=
d
> the other root-level nodes though.

Let's try Paolo's cleanup for now.  I am worried about proliferation of=
 things=20
in the root hierarchy and the nice advantage of having /devices is that=
 we can=20
work towards making our build infrastructure roughly match our hierarch=
y.

Since 1.1 is unstable for QOM, we can always change it later.

>
> For PC-style machines I'd expect board-level stuff like the CPUs to
> appear directly under /. That would roughly correspond to the
> OpenFirmware device tree then.

I think devices trees are a bad example that should not be emulated.

Regards,

Anthony Liguori