From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: ioctl number overlap? Date: Mon, 15 Jun 2009 22:19:38 +0200 Message-ID: <4A36ACDA.8030105@web.de> References: <4A369C5F.1020404@us.ibm.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE7E2295D403D49373BC3CFCF" Cc: kvm To: Beth Kon Return-path: Received: from fmmailgate01.web.de ([217.72.192.221]:36313 "EHLO fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751259AbZFOUT5 (ORCPT ); Mon, 15 Jun 2009 16:19:57 -0400 In-Reply-To: <4A369C5F.1020404@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE7E2295D403D49373BC3CFCF Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Beth Kon wrote: > kvm.h has >=20 > #define KVM_SET_GUEST_DEBUG _IOW(KVMIO, 0x9b, struct > kvm_guest_debug) >=20 > and >=20 > #define KVM_IA64_VCPU_SET_STACK _IOW(KVMIO, 0x9b, void *) >=20 > Seems that these could conflict? Argh... The IA64 world also collides with KVM_NMI - though I have no clue if NMIs are known to that arch. The good news is that different structure sizes (and different flags for 0x9a) should resolve the conflict numerically. Still messy, though. Jan --------------enigE7E2295D403D49373BC3CFCF 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 iEYEARECAAYFAko2rN0ACgkQniDOoMHTA+lTLACfZIwpQ0C8mDxm+MX0nRO4Brll kpoAn3DGpee0LyinlMokfQTk3huHQeZP =vf6d -----END PGP SIGNATURE----- --------------enigE7E2295D403D49373BC3CFCF--