WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Usage of "container_of" in QEMU

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] Usage of "container_of" in QEMU
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Fri, 2 Jun 2006 23:39:22 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 02 Jun 2006 14:40:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <e3efccb021ee6ec7360e13b4204bbc56@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcaGdZwj1upU5MgsS5+vZgft5Mz/gQAFoWNQ
Thread-topic: Usage of "container_of" in QEMU
Regarding the suggestion to use container_of() macro to fish out more
complex context for QEMU from the ops callback functions, do you have a
suggestion of where the container_of() macro should be copied/moved to.
At the moment, I've just made a copy of it in helper2 where I've
currently put all new code - but that's not a particulary good way to
reuse an existing macro... On the other hand, I don't think we want to
include kernel.h into QEMU?

Although looking further, it doesn't look like
.../xen/include/xen/kernel.h contains ANYTHING kernel, just a few fairly
generic macros... Maybe renaming the file is a better solution [or
moving everything in it into a different file - leaving this one
empty-ish] ?

--
Mats


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel