Carsten Otte wrote:
>
>>> System call latency adds to the in-kernel approach here.
>> I don't understand this.
> What I meant to state was: If the host side of the block driver runs
> in userspace, we have the extra latency to leave the kernel system
> call context, compute on behalf of the user
Avi Kivity wrote:
> I don't see an immediate need to put the host-side driver in the kernel,
> but I don't want to embed the host fd (which is an implementation
> detail) into the host/guest ABI. There may not even be a host fd.
Your point is taken, it also punches a hole in the security barrier
Carsten Otte wrote:
>
> Avi Kivity wrote:
>> Is this the host file descriptor? If so, we want to use something
>> more abstract (if the host side is in kernel, there will be no fd, or
>> if the device is implemented using >1 files (or <1 files)).
> This is indeed the host file descriptor. Host u
Avi Kivity wrote:
> Oh. Why not use Xen's pending block driver? It probably has everything
> needed.
We're not too eager to have our own device drivers become the solution
of choice. I have'nt looked at it so far, will do.
so long,
Carsten
---
Avi Kivity wrote:
> Is this the host file descriptor? If so, we want to use something more
> abstract (if the host side is in kernel, there will be no fd, or if the
> device is implemented using >1 files (or <1 files)).
This is indeed the host file descriptor. Host userland uses sys_open
to re
Carsten Otte wrote:
> From: Carsten Otte <[EMAIL PROTECTED]>
>
> This driver provides access to virtual block devices. It does use its own
> make_request function which passes the bio to a workqueue thread. The
> workqueue
> thread does use the diagnose hypervisor call to call the hosting Linux.
>
Carsten Otte wrote:
> From: Carsten Otte <[EMAIL PROTECTED]>
>
> This driver provides access to virtual block devices. It does use its own
> make_request function which passes the bio to a workqueue thread. The
> workqueue
> thread does use the diagnose hypervisor call to call the hosting Linux.
>
From: Carsten Otte <[EMAIL PROTECTED]>
This driver provides access to virtual block devices. It does use its own
make_request function which passes the bio to a workqueue thread. The workqueue
thread does use the diagnose hypervisor call to call the hosting Linux.
The hypervisor code in host users
