From: Anthony Liguori <aliguori@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, John Levon <levon@movementarian.org>
Subject: Re: [PATCH] change dom0 headers path
Date: Thu, 20 Apr 2006 09:43:19 -0500 [thread overview]
Message-ID: <44479E07.5020003@us.ibm.com> (raw)
In-Reply-To: <8ab943f8056ddeae5d130d695e5b4d56@cl.cam.ac.uk>
Keir Fraser wrote:
>
> On 20 Apr 2006, at 14:55, Anthony Liguori wrote:
>
>> Because libxc "leaks" a few of the dom0_op structures like
>> dom0_getvcpuinfo_t, dom0_shadow_control_stats_t, etc in its public
>> interface. This could be fixed by making sure all of those
>> structures had wrapper (like xc_dominfo_t).
>
> Those are defined in Xen public header files, not in Linux's privcmd.h.
Yes, sorry, I read the first mail to quickly. This is another of my
gripes though (it would be nice if xenctrl.h didn't pull in the Xen
public headers too).
About privcmd.h, the users of it are making hypercalls that aren't
exposed through libxenctrl. Those users probably ought to add the
appropriate plumbing to libxenctrl. This includes the ACM stuff,
xenmon/xentrace, and xenstat.
Regards,
Anthony Liguori
> -- Keir
>
next prev parent reply other threads:[~2006-04-20 14:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 12:39 [PATCH] change dom0 headers path John Levon
2006-04-20 13:00 ` Keir Fraser
2006-04-20 13:13 ` John Levon
2006-04-20 13:36 ` Keir Fraser
2006-04-20 13:47 ` John Levon
2006-04-20 14:31 ` Keir Fraser
2006-04-20 14:40 ` John Levon
2006-04-20 14:48 ` Keir Fraser
2006-04-21 17:55 ` John Levon
2006-04-22 8:30 ` Keir Fraser
2006-04-20 13:55 ` Anthony Liguori
2006-04-20 14:09 ` Keir Fraser
2006-04-20 14:43 ` Anthony Liguori [this message]
2006-04-20 14:50 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44479E07.5020003@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=levon@movementarian.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.