|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] Re: [PATCH 0/4] Machine config files |
Date: | Mon, 06 Jul 2009 19:12:28 +0300 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2 |
On 07/06/2009 05:40 PM, Gerd Hoffmann wrote:
It might make sense to integrate savevm callbacks into qdev, then you'd have actually a chance to figure which driver belongs to your piece of savevm state.
That's my preference. The very first pass iterates the device tree and serializes it.
I suspect it isn't enougth to make it work though, you still need to know the position of the device in the device tree. To answer questions like "is your pci device behind a bridge and if so which one?".
Isn't that info provided by qdev? qdev will walk the pci bus, note there's a bridge, walk the bridged pci bus, note there's a usb controller, walk the usb bus, note there's a usb-scsi controller, walk the scsi bus, ... (ran out of steam).
-- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |