From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Kumar, Venkat" <Venkat.Kumar@lsi.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Inter VM Communication
Date: Wed, 25 Mar 2009 08:44:39 +0200 [thread overview]
Message-ID: <49C9D2D7.7030501@redhat.com> (raw)
In-Reply-To: <49C99495.5070005@codemonkey.ws>
Anthony Liguori wrote:
> So one gotcha about using a BAR is that we emulate a 32-bit PCI device
> so that limits where the BAR can live in memory and how large it can be.
We can overcome that by emulating a 64-bit device...
> I think bars also have to be powers of two in size.
I think that's right; but the device can define the the range [0, X) as
shared RAM and the range [X, 2^n) as undefined. So long as it makes X
available in the config space.
Besides, computer people have trouble imagining numbers which are not
powers of two.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2009-03-25 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 11:00 Inter VM Communication Kumar, Venkat
2009-03-24 12:45 ` Avi Kivity
2009-03-24 20:41 ` Cam Macdonell
2009-03-24 21:06 ` Avi Kivity
2009-03-24 22:31 ` Brian Jackson
2009-03-25 2:19 ` Anthony Liguori
2009-03-25 6:44 ` Avi Kivity [this message]
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=49C9D2D7.7030501@redhat.com \
--to=avi@redhat.com \
--cc=Venkat.Kumar@lsi.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox