|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] [PATCH 0/6] Device state visualization reloaded |
Date: | Wed, 07 Sep 2011 08:23:10 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10 |
On 09/07/2011 08:17 AM, Michael S. Tsirkin wrote:
On Wed, Sep 07, 2011 at 03:13:00PM +0200, Jan Kiszka wrote:On 2011-09-07 15:06, Michael S. Tsirkin wrote:But if the command is not for users at all, if it's for qemu debugging, then exposing internals is a very logical thing. Only problem is - we must make it very very clear which commands are for qemu debugging.This command it also for users, to debug guests. JanHmm, guest visible state must be stable by definition. So why can't we make the interfaces stable then?
Because right now how you reference devices cannot be stable.Going back to a previous thread, what if the command took a qdev class type as a filter?
That would be a stable name, not require anonymous IDs, and would have the property of usually being a single device.
Regards, Anthony Liguori
-- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux
[Prev in Thread] | Current Thread | [Next in Thread] |