[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <469E3FA2.7060408@codemonkey.ws>
Date: Wed, 18 Jul 2007 11:28:18 -0500
From: Anthony Liguori <anthony@...emonkey.ws>
To: Jeff Dike <jdike@...toit.com>
CC: Avi Kivity <avi@...ranet.com>,
KVM devel <kvm-devel@...ts.sourceforge.net>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [kvm-devel] [PATCH 3/3] KVM - add hypercall nr to kvm_run
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
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists