From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:36895)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1TtMLy-0005wo-BG
	for qemu-devel@nongnu.org; Thu, 10 Jan 2013 12:55:48 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1TtMLv-0007jK-Ki
	for qemu-devel@nongnu.org; Thu, 10 Jan 2013 12:55:46 -0500
Received: from cantor2.suse.de ([195.135.220.15]:54004 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1TtMLv-0007iI-5c
	for qemu-devel@nongnu.org; Thu, 10 Jan 2013 12:55:43 -0500
Message-ID: <50EF0098.8020101@suse.de>
Date: Thu, 10 Jan 2013 18:55:36 +0100
From: =?ISO-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>
MIME-Version: 1.0
References: <1355834518-17989-1-git-send-email-vasilis.liaskovitis@profitbricks.com>
	<50ECB514.1020508@suse.de>
	<20130110173657.GA21593@dhcp-192-168-178-175.profitbricks.localdomain>
In-Reply-To: <20130110173657.GA21593@dhcp-192-168-178-175.profitbricks.localdomain>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [RFC PATCH v4 00/30] ACPI memory hotplug
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/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: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>
Cc: pingfank@linux.vnet.ibm.com, Eduardo Habkost <ehabkost@redhat.com>, gleb@redhat.com, stefanha@gmail.com, jbaron@redhat.com, seabios@seabios.org, qemu-devel@nongnu.org, blauwirbel@gmail.com, kevin@koconnor.net, kraxel@redhat.com, Anthony Liguori <anthony@codemonkey.ws>, Igor Mammedov <imammedo@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>

Am 10.01.2013 18:36, schrieb Vasilis Liaskovitis:
> Btw, is the CPU link<socket> feature already implemented in a qom-cpu b=
ranch?

No, the latest topology series moves fields around as preparation.
There's still one CPUState per hyperthread, but as a DeviceState now.

Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe=
rg