From: Anthony Liguori <anthony@codemonkey.ws> To: "Andreas Färber" <afaerber@suse.de> Cc: Paolo Bonzini <pbonzini@redhat.com>, quintela@redhat.com, Developers qemu-devel <qemu-devel@nongnu.org>, KVM devel mailing list <kvm@vger.kernel.org> Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 7 Date: Tue, 07 Feb 2012 10:53:24 -0600 [thread overview] Message-ID: <4F315704.1040306@codemonkey.ws> (raw) In-Reply-To: <4F31544B.8040808@suse.de> On 02/07/2012 10:41 AM, Andreas Färber wrote: > Am 07.02.2012 16:21, schrieb Paolo Bonzini: >> BTW, I would like to change /i440fx to /devices/i440fx, so that we will >> 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 mind > the other root-level nodes though. Let's try Paolo's cleanup for now. I am worried about proliferation of things in the root hierarchy and the nice advantage of having /devices is that we can work towards making our build infrastructure roughly match our hierarchy. 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
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws> To: "Andreas Färber" <afaerber@suse.de> Cc: Paolo Bonzini <pbonzini@redhat.com>, Developers qemu-devel <qemu-devel@nongnu.org>, KVM devel mailing list <kvm@vger.kernel.org>, quintela@redhat.com Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 7 Date: Tue, 07 Feb 2012 10:53:24 -0600 [thread overview] Message-ID: <4F315704.1040306@codemonkey.ws> (raw) In-Reply-To: <4F31544B.8040808@suse.de> On 02/07/2012 10:41 AM, Andreas Färber wrote: > Am 07.02.2012 16:21, schrieb Paolo Bonzini: >> BTW, I would like to change /i440fx to /devices/i440fx, so that we will >> 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 mind > the other root-level nodes though. Let's try Paolo's cleanup for now. I am worried about proliferation of things in the root hierarchy and the nice advantage of having /devices is that we can work towards making our build infrastructure roughly match our hierarchy. 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
next prev parent reply other threads:[~2012-02-07 16:53 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-06 19:25 KVM call agenda for Tuesday 7 Juan Quintela 2012-02-06 19:25 ` [Qemu-devel] " Juan Quintela 2012-02-07 13:45 ` Andreas Färber 2012-02-07 13:45 ` Andreas Färber 2012-02-07 13:52 ` Paolo Bonzini 2012-02-07 13:52 ` Paolo Bonzini 2012-02-07 14:56 ` Anthony Liguori 2012-02-07 14:56 ` Anthony Liguori 2012-02-07 15:21 ` Paolo Bonzini 2012-02-07 15:21 ` Paolo Bonzini 2012-02-07 16:24 ` Anthony Liguori 2012-02-07 16:24 ` Anthony Liguori 2012-02-07 16:27 ` Paolo Bonzini 2012-02-07 16:27 ` Paolo Bonzini 2012-02-07 16:33 ` Anthony Liguori 2012-02-07 16:33 ` Anthony Liguori 2012-02-07 16:40 ` Peter Maydell 2012-02-07 16:40 ` Peter Maydell 2012-02-07 17:04 ` Paolo Bonzini 2012-02-07 17:04 ` Paolo Bonzini 2012-02-07 16:41 ` Andreas Färber 2012-02-07 16:41 ` Andreas Färber 2012-02-07 16:53 ` Anthony Liguori [this message] 2012-02-07 16:53 ` Anthony Liguori 2012-02-07 18:01 ` Anthony Liguori 2012-02-07 18:01 ` Anthony Liguori 2012-02-07 18:17 ` Andreas Färber 2012-02-07 18:17 ` Andreas Färber 2012-02-07 19:06 ` Anthony Liguori 2012-02-07 14:23 ` Juan Quintela 2012-02-07 14:23 ` [Qemu-devel] " Juan Quintela
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4F315704.1040306@codemonkey.ws \ --to=anthony@codemonkey.ws \ --cc=afaerber@suse.de \ --cc=kvm@vger.kernel.org \ --cc=pbonzini@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=quintela@redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.