From: Anthony Liguori <anthony@codemonkey.ws>
To: Jeff Dike <jdike@addtoit.com>
Cc: Avi Kivity <avi@qumranet.com>,
KVM devel <kvm-devel@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] [PATCH 3/3] KVM - add hypercall nr to kvm_run
Date: Wed, 18 Jul 2007 11:28:18 -0500 [thread overview]
Message-ID: <469E3FA2.7060408@codemonkey.ws> (raw)
In-Reply-To: <20070717160710.GC7965@c2.user-mode-linux.org>
Jeff Dike wrote:
> On Tue, Jul 17, 2007 at 09:15:51AM -0500, Anthony Liguori wrote:
>
>> I'm planning on breaking this interface again since the new hypercall
>> API only takes 4 arguments instead of 6.
>>
>
> Is anything written anywhere about this hypercall interface?
>
I've posted patches. I'll post more in the near future since we decided
to make some rather drastic changes. With the new patchset, guest's
will use vmcall directly with a couple bytes of padding. The hypervisor
may or may not patch the calling site to use something different (like
vmmcall).
> The thing which would make me happy (which the current code comes
> close to) is for the guest to be able to pass out Linux system calls
> with VMCALL.
>
Within the kernel right (VMCALL is only usable in ring 1). Is it
terribly important to be able to pass through the syscall arguments in
registers verses packing them in a data structure and passing a pointer
to that structure?
Regards,
Anthony Liguori
> Jeff
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Jeff Dike <jdike-OPE4K8JWMJJBDgjK7y7TUQ@public.gmane.org>
Cc: KVM devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 3/3] KVM - add hypercall nr to kvm_run
Date: Wed, 18 Jul 2007 11:28:18 -0500 [thread overview]
Message-ID: <469E3FA2.7060408@codemonkey.ws> (raw)
In-Reply-To: <20070717160710.GC7965-1LLyehjZOUUZWFFyALql+T+iFHGzDt/a@public.gmane.org>
Jeff Dike wrote:
> On Tue, Jul 17, 2007 at 09:15:51AM -0500, Anthony Liguori wrote:
>
>> I'm planning on breaking this interface again since the new hypercall
>> API only takes 4 arguments instead of 6.
>>
>
> Is anything written anywhere about this hypercall interface?
>
I've posted patches. I'll post more in the near future since we decided
to make some rather drastic changes. With the new patchset, guest's
will use vmcall directly with a couple bytes of padding. The hypervisor
may or may not patch the calling site to use something different (like
vmmcall).
> The thing which would make me happy (which the current code comes
> close to) is for the guest to be able to pass out Linux system calls
> with VMCALL.
>
Within the kernel right (VMCALL is only usable in ring 1). Is it
terribly important to be able to pass through the syscall arguments in
registers verses packing them in a data structure and passing a pointer
to that structure?
Regards,
Anthony Liguori
> Jeff
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-07-18 16:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 19:24 [PATCH 3/3] KVM - add hypercall nr to kvm_run Jeff Dike
2007-07-16 19:24 ` Jeff Dike
2007-07-17 8:23 ` Avi Kivity
2007-07-17 8:23 ` Avi Kivity
2007-07-17 8:40 ` Avi Kivity
2007-07-17 8:40 ` Avi Kivity
2007-07-17 14:15 ` [kvm-devel] " Anthony Liguori
2007-07-17 14:15 ` Anthony Liguori
2007-07-17 16:07 ` [kvm-devel] " Jeff Dike
2007-07-17 16:07 ` Jeff Dike
2007-07-18 16:28 ` Anthony Liguori [this message]
2007-07-18 16:28 ` Anthony Liguori
2007-07-18 17:41 ` [kvm-devel] " Jeff Dike
2007-07-18 17:41 ` Jeff Dike
2007-07-18 19:25 ` [kvm-devel] " Anthony Liguori
2007-07-18 19:25 ` 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=469E3FA2.7060408@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=jdike@addtoit.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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.