From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH 3/4] Move KVMState to common header Date: Mon, 08 Jun 2009 21:54:34 +0200 Message-ID: <4A2D6C7A.4080008@web.de> References: <1244488224-31171-1-git-send-email-glommer@redhat.com> <1244488224-31171-2-git-send-email-glommer@redhat.com> <1244488224-31171-3-git-send-email-glommer@redhat.com> <1244488224-31171-4-git-send-email-glommer@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA34E905D6881986AE33480CF" Cc: kvm@vger.kernel.org, avi@redhat.com, Anthony Liguori To: Glauber Costa Return-path: Received: from fmmailgate03.web.de ([217.72.192.234]:33531 "EHLO fmmailgate03.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751130AbZFHTyh (ORCPT ); Mon, 8 Jun 2009 15:54:37 -0400 In-Reply-To: <1244488224-31171-4-git-send-email-glommer@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA34E905D6881986AE33480CF Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Glauber Costa wrote: > This patch should be applied to main qemu, but I'll > first post it here for appreciation. In this patch, > we move KVMState definition to kvm.h header. With this > done, we can also use its definition in our files, until > there is no more such thing as "our" files. This is too > selfish anyway. >=20 > Later on, we'll move our internal state inside it. Well, in upstream no one outside kvm-all.c needs to (and likely should be allowed to) access fields from struct KVMState & KVMSlot directly. That avoids misuse outside the KVM layer and enforces KVM arch code to properly call into the generic layer. But I see the problem for qemu-kvm's transition time, so let's try to find an intermediate solution until its code layout is aligned (I don't see any blockers for this). Suggestion: Replicate the relevant structures into a new, temporary header. If upstream may extend its original structures, this should from now on have happened *first* inside qemu-kvm, so no inconsistency can arise unless downstream messed it up already. At some point (hopefully not too far away), no user of that header will remain and we will be able to drop it again. Jan --------------enigA34E905D6881986AE33480CF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkotbH4ACgkQniDOoMHTA+keqgCeKYRqjg7UIIjemMVPx4F4bfDA 6wwAnA0v1toEngv/tV0bzRdQVkftkMxY =8Vz0 -----END PGP SIGNATURE----- --------------enigA34E905D6881986AE33480CF--