qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC v2 2/6] qtest: add support for target-i386 -M pc


From: Anthony Liguori
Subject: Re: [Qemu-devel] [RFC v2 2/6] qtest: add support for target-i386 -M pc
Date: Thu, 29 Dec 2011 12:47:27 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15

On 12/29/2011 11:40 AM, Peter Maydell wrote:
On 1 December 2011 18:43, Anthony Liguori<address@hidden>  wrote:
This involves forcing the CPU into the halted state if qtest is enabled and
replacing the local APIC with the qtest interrupt controller.

It should be pretty straight forward to do the same for other machine types on
other architectures.

Having to modify every machine type seems to me like a huge red flag that this
is the wrong approach for device level tests. Surely the right thing is to
(a) instantiate the device (b) manipulate it via its publicly exposed interfaces
(ie the memory regions, gpio signals, irqs, etc etc) ?

The problem is the machine creation. Once we convert everything to QOM including machine setup, yes, this is what we can do.

Regards,

Anthony Liguori


Alternatively if you're just testing features of the device as it
is wired up on the board then you want something that generates an
image that can just be run on the unmodified QEMU model; that then
lets you cross check by running your tests on real hardware.

-- PMM





reply via email to

[Prev in Thread] Current Thread [Next in Thread]