[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] ARM QOM conversion / class hierarchy
From: |
Paul Brook |
Subject: |
Re: [Qemu-devel] ARM QOM conversion / class hierarchy |
Date: |
Tue, 20 Mar 2012 17:14:08 +0000 |
User-agent: |
KMail/1.13.7 (Linux/3.2.0-1-amd64; KDE/4.7.4; x86_64; ; ) |
> Make an ARMCPUClass that maps to the existing ARM support. Do *not* expose
> all of the different features as properties. Make ARMCPUClass abstract.
>
> Subclass ARMCPUClass for specific models, set default flags to implement
> the necessary logic. Expose tunables on a case-by-case basis (if there
> needs to be a 'neon' flag for cortex-a9, then make one, but don't make
> everything a flag just for the hell of it).
As long as we can avoid the sort of duplication and redundant implementation
that the initial .feature patch introduced. If only having a neon knob on
some cores means we have to duplicate a whole bunch of boilerplate between
those cores then we're doing it wrong.
Paul
Re: [Qemu-devel] ARM QOM conversion / class hierarchy, Anthony Liguori, 2012/03/20
Re: [Qemu-devel] ARM QOM conversion / class hierarchy, Michael Roth, 2012/03/20