From: Avi Kivity <avi@redhat.com>
To: David Evensky <evensky@dancer.ca.sandia.gov>
Cc: Sasha Levin <levinsasha928@gmail.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Pekka Enberg <penberg@kernel.org>, Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org, cam@cs.ualberta.ca
Subject: Re: [PATCH] kvm tools: adds a PCI device that exports a host shared segment as a PCI BAR in the guest
Date: Fri, 26 Aug 2011 00:11:03 +0300 [thread overview]
Message-ID: <4E56BA67.9000901@redhat.com> (raw)
In-Reply-To: <20110825210018.GA27983@dancer.ca.sandia.gov>
On 08/26/2011 12:00 AM, David Evensky wrote:
> I've tested ivshmem with the latest git pull (had minor trouble
> building on debian sid, vnc and unused var, but trivial to work
> around).
>
> QEMU's -device ivshmem,size=16,shm=/kvm_shmem
>
> seems to function as my proposed
>
> --shmem pci:0xfd000000:16M:handle=/kvm_shmem
>
> except that I can't specify the BAR. I am able to read what
> I'm given, 0xfd000000, from lspci -vvv; but for our application
> we need to be able to specify the address on the command line.
>
> If folks are open, I would like to request this feature in the
> ivshmem.
It's not really possible. Qemu does not lay out the BARs, the guest does
(specifically the bios). You might be able to re-arrange the layout
after the guest boots.
Why do you need the BAR at a specific physical address?
> It would be cool to test our application with QEMU,
> even if we can't use it in production.
Why can't you use qemu in production?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-08-25 21:11 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
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 [this message]
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=4E56BA67.9000901@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=cam@cs.ualberta.ca \
--cc=evensky@dancer.ca.sandia.gov \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--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 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.