From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=52571 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OmDz5-0006ch-CQ
	for qemu-devel@nongnu.org; Thu, 19 Aug 2010 18:53:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <av1474@comtv.ru>) id 1OmDyf-0000EI-16
	for qemu-devel@nongnu.org; Thu, 19 Aug 2010 18:52:53 -0400
Received: from fe01x03-cgp.akado.ru ([77.232.31.164]:64620 helo=akado.ru)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <av1474@comtv.ru>) id 1OmDye-0000EA-QM
	for qemu-devel@nongnu.org; Thu, 19 Aug 2010 18:52:52 -0400
Date: Fri, 20 Aug 2010 02:52:47 +0400 (MSD)
From: malc <av1474@comtv.ru>
Subject: Re: [Qemu-devel] [PATCH v2 0/7] APIC/IOAPIC cleanup
In-Reply-To: <4C6DA75D.40303@codemonkey.ws>
Message-ID: <alpine.LNX.2.00.1008200251570.1410@linmac>
References: <AANLkTikId-kuGpCNvhLklY5SiTJhpOKaCDzpNvLT0Wd4@mail.gmail.com>
	<4C6D86F9.3010602@codemonkey.ws>
	<AANLkTimGH9WAgFs5VuvdhFxjPnTjpcKXgkEf7cOSk5JV@mail.gmail.com>
	<4C6D98E7.9020109@codemonkey.ws>
	<AANLkTin4m9v07ut=wad_Mh-BKhBfO0jMP9xCikV9eeTH@mail.gmail.com>
	<4C6DA75D.40303@codemonkey.ws>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>, "Liu >> \"Liu,
	Jinsong\"" <jinsong.liu@intel.com>, Paul Brook <paul@codesourcery.com>, Avi Kivity <avi@redhat.com>, qemu-devel <qemu-devel@nongnu.org>

On Thu, 19 Aug 2010, Anthony Liguori wrote:

> On 08/19/2010 04:21 PM, Blue Swirl wrote:
> > > Should CPUs appear in the QEMU device tree?
> > >      
> > They have several properties that should be user visible.
> >    
> 
> Sure, but that's an argument for having some of the qdev features (like
> variant properties) be consumable outside of qdev.
> 

[..snip..]

> 
> Yes, but the programming model was different.
> 
> Look at the PIC compared to the lapic.  The PIC is programmed via pio at a
> fixed location.  There is only one PIC and it interacts with the system just
> like all other devices.  IOW, there is no reference to CPUState.

There are two PICs actually there's a cascade..

> 
> When you look at the local APIC (apic.c) however, you see that it's the only
> device in the tree that actually interacts with a CPUState.  The notion of
> cpu_get_current_apic() is a good example of the tricks needed to make this
> work.
> 
> The local APIC is a cpu feature, not a device.
> 
> Regards,
> 
> Anthony Liguori
> 

-- 
mailto:av1474@comtv.ru