From: Sasha Levin <levinsasha928@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Pekka Enberg <penberg@kernel.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
David Evensky <evensky@dancer.ca.sandia.gov>,
Alexander Graf <agraf@suse.de>,
David Evensky <evensky@sandia.gov>,
kvm@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] kvm tools: adds a PCI device that exports a host shared segment as a PCI BAR in the guest
Date: Thu, 25 Aug 2011 14:51:18 +0300 [thread overview]
Message-ID: <1314273078.3692.32.camel@lappy> (raw)
In-Reply-To: <4E56325E.4010807@redhat.com>
On Thu, 2011-08-25 at 14:30 +0300, Avi Kivity wrote:
> On 08/25/2011 02:15 PM, Pekka Enberg wrote:
> > On Thu, Aug 25, 2011 at 1:59 PM, Stefan Hajnoczi<stefanha@gmail.com> wrote:
> > > Introducing yet another non-standard and non-Linux interface doesn't
> > > help though. If there is no significant improvement over ivshmem then
> > > it makes sense to let ivshmem gain critical mass and more users
> > > instead of fragmenting the space.
> >
> > Look, I'm not going to require QEMU compatibility from tools/kvm
> > contributors. If you guys really feel that strongly about the
> > interface, then either
> >
> > - Get Rusty's "virtio spec pixie pee" for ivshmem
>
> It's not a virtio device (doesn't do dma). It does have a spec in
> qemu.git/docs/specs.
Please note that the spec you have in /docs/specs is different from what
Cam has in his git tree
(https://gitorious.org/nahanni/guest-code/blobs/master/device_spec.txt
).
If we are going to add it to KVM tool maybe it's a good time to move it
out of QEMU tree and make it less QEMU specific?
>
> > - Get the Linux driver merged to linux-next
>
> ivshmem uses uio, so it doesn't need an in-kernel driver, IIRC. Map
> your BAR from sysfs and go.
>
> > - Help out David and Sasha to change interface
> >
> > But don't ask me to block clean code from inclusion to tools/kvm
> > because it doesn't have a QEMU-capable interface.
>
> A lot of thought has gone into the design and implementation of
> ivshmem. But don't let that stop you from merging clean code.
Theres a big difference in requiring it to be ivshmem compatible because
ivshmem is good and requiring it to be ivshmem compatible because thats
what QEMU is doing.
Looking at the comments in this thread I would have expected to see much
more comments regarding the technical supremacy of ivshmem over a simple
memory shared block instead of the argument that KVM tools has to
conform to QEMU standards.
--
Sasha.
next prev parent reply other threads:[~2011-08-25 11:51 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 22:25 [PATCH] kvm tools: adds a PCI device that exports a host shared segment as a PCI BAR in the guest David Evensky
2011-08-25 3:27 ` Alexander Graf
2011-08-25 4:49 ` David Evensky
2011-08-25 4:52 ` Alexander Graf
2011-08-25 5:11 ` Pekka Enberg
[not found] ` <A16CB574-D2F7-440B-BD26-12EB4DEAD917@suse.de>
2011-08-25 5:37 ` Pekka Enberg
2011-08-25 5:38 ` Alexander Graf
2011-08-25 5:06 ` Pekka Enberg
2011-08-25 5:49 ` David Evensky
2011-08-25 10:31 ` Stefan Hajnoczi
2011-08-25 10:37 ` Pekka Enberg
2011-08-25 10:59 ` Stefan Hajnoczi
2011-08-25 11:15 ` Pekka Enberg
2011-08-25 11:30 ` Avi Kivity
2011-08-25 11:38 ` Pekka Enberg
2011-08-25 11:51 ` Avi Kivity
2011-08-25 12:01 ` Pekka Enberg
2011-08-25 11:51 ` Sasha Levin [this message]
2011-08-25 11:25 ` Sasha Levin
2011-08-25 15:08 ` David Evensky
2011-08-25 22:08 ` Eric Northup
2011-08-25 22:27 ` David Evensky
2011-08-26 6:33 ` Sasha Levin
2011-08-26 15:05 ` David Evensky
[not found] ` <30669_1314285268_p7PFESZN013126_20110825150806.GF24996@dancer.ca.sandia.gov>
2011-08-25 21:00 ` David Evensky
2011-08-25 21:11 ` Avi Kivity
2011-08-25 22:03 ` David Evensky
2011-08-28 7:34 ` Avi Kivity
2011-08-29 4:55 ` David Evensky
2011-08-25 5:41 ` Avi Kivity
2011-08-25 6:01 ` David Evensky
2011-08-25 6:02 ` Pekka Enberg
2011-08-25 6:11 ` David Evensky
[not found] ` <CAFO3S41WOutTEmMGAeor6w=OZ_cax_AHB7Wo24jfUioynv3DFg@mail.gmail.com>
[not found] ` <4E55E378.4060904@kernel.org>
2011-08-25 6:30 ` Asias He
2011-08-25 7:02 ` Pekka Enberg
2011-08-25 7:20 ` Asias He
2011-08-25 7:24 ` Pekka Enberg
2011-08-25 21:35 ` Anthony Liguori
2011-08-25 21:50 ` David Evensky
2011-08-26 6:11 ` Sasha Levin
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=1314273078.3692.32.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=evensky@dancer.ca.sandia.gov \
--cc=evensky@sandia.gov \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=stefanha@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox