From: Sheng Yang <sheng@linux.intel.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: [PATCH][v2] Hybrid extension support in Xen
Date: Tue, 2 Feb 2010 20:54:09 +0800 [thread overview]
Message-ID: <201002022054.09843.sheng@linux.intel.com> (raw)
In-Reply-To: <1265109741.2965.22412.camel@zakaz.uk.xensource.com>
On Tuesday 02 February 2010 19:22:21 Ian Campbell wrote:
> On Tue, 2010-02-02 at 08:16 +0000, Sheng Yang wrote:
> > +/* Reserve 128KB for grant table */
> > +#define GNTTAB_MEMBASE 0xfbfe0000
> > +#define GNTTAB_MEMSIZE 0x20000
>
> Why is this necessary? Isn't the grant table contained within one of the
> BARS on the virtual PCI device? What needs grant tables for prior to the
> kernel finding the PCI device which necessitates hardcoding these
> addresses in both guest and hypervisor?
>
Thanks for so quick and detail comments. :)
And this one is purposed, because we don't want to depends on QEmu. As you
see, we now have PV drivers, QEmu is an alternative way to provide device
model now. We think that still involving QEmu as a requirement is somehow
strange. So this reserved region is there, to drop the dependence with QEmu to
provide PV driver(PV driver depends on QEmu is still strange, right?).
--
regards
Yang, Sheng
next prev parent reply other threads:[~2010-02-02 12:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 8:16 [PATCH][v2] Hybrid extension support in Xen Sheng Yang
2010-02-02 11:22 ` Ian Campbell
2010-02-02 12:54 ` Sheng Yang [this message]
2010-02-02 13:19 ` Ian Campbell
2010-02-02 13:28 ` Sheng Yang
2010-02-02 13:50 ` Ian Campbell
2010-02-02 14:00 ` Tim Deegan
2010-02-02 14:22 ` Sheng Yang
2010-02-02 14:28 ` Sheng Yang
2010-02-02 13:35 ` Keir Fraser
2010-02-02 13:52 ` Sheng Yang
2010-02-02 14:01 ` Keir Fraser
2010-02-02 14:13 ` Sheng Yang
2010-02-02 11:26 ` Ian Campbell
2010-02-02 13:06 ` Sheng Yang
2010-02-02 13:52 ` Ian Campbell
2010-02-02 14:04 ` Stefano Stabellini
2010-02-02 14:07 ` Sheng Yang
2010-02-02 16:15 ` Ian Campbell
2010-02-02 16:31 ` Sheng Yang
2010-02-02 18:03 ` Ian Campbell
2010-02-02 18:27 ` Stefano Stabellini
2010-02-03 5:15 ` Sheng Yang
2010-02-03 10:39 ` Tim Deegan
2010-02-02 11:32 ` Paul Durrant
2010-02-02 13:23 ` Keir Fraser
2010-02-02 13:37 ` Sheng Yang
2010-02-02 14:03 ` Keir Fraser
2010-02-02 14:08 ` Sheng Yang
2010-02-02 14:32 ` Keir Fraser
2010-02-02 14:37 ` Keir Fraser
2010-02-02 15:51 ` Sheng Yang
2010-02-02 14:39 ` Sheng Yang
2010-02-02 13:52 ` Ian Campbell
2010-02-02 13:53 ` Sheng Yang
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=201002022054.09843.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=Ian.Campbell@citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.