From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Dor Laor <dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH 2/4] [HYPERCALL] Enable userspace too include kvm_para.
Date: Sat, 25 Aug 2007 11:10:41 +0300 [thread overview]
Message-ID: <46CFE401.2010206@qumranet.com> (raw)
In-Reply-To: <64F9B87B6B770947A9F8391472E032160D59004D-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
Dor Laor wrote:
> Since some hypercalls can be handled in userspace, it needs
> to include kvm_para too. Chande kernel types into user and
> add includes for them and for page_size.
> @@ -25,17 +28,17 @@ struct kvm_vcpu_para_state {
> * is supposed to work - new host versions will support all old
> * guest API versions.
> */
> - u32 guest_version;
> - u32 host_version;
> - u32 size;
> - u32 ret;
> + __u32 guest_version;
> + __u32 host_version;
> + __u32 size;
> + __u32 ret;
>
> /*
> * The address of the vm exit instruction (VMCALL or VMMCALL),
> * which the host will patch according to the CPU model the
> * VM runs on:
> */
> - u64 hypercall_gpa;
> + __u64 hypercall_gpa;
>
> } __attribute__ ((aligned(PAGE_SIZE)));
>
>
>
But userspace isn't really interested in kvm_para_state, right? You can
just wrap it in #ifdef __KERNEL__.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-08-25 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 23:58 [PATCH 2/4] [HYPERCALL] Enable userspace too include kvm_para Dor Laor
[not found] ` <64F9B87B6B770947A9F8391472E032160D59004D-yEcIvxbTEBqsx+V+t5oei8rau4O3wl8o3fe8/T/H7NteoWH0uzbU5w@public.gmane.org>
2007-08-25 8:10 ` Avi Kivity [this message]
[not found] ` <46CFE401.2010206-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-25 9:40 ` Dor Laor
2007-08-27 22:17 ` Anthony Liguori
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=46CFE401.2010206@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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.