From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Han, Weidong" <weidong.han@intel.com>, xen-devel@lists.xensource.com
Cc: joshua.levasseur@netronome.com, "Li, Xin B" <xin.b.li@intel.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>,
espen.skoglund@netronome.com
Subject: Re: Dom0 hypercall for adding and removing PCI devices
Date: Wed, 23 Jul 2008 10:10:22 +0100 [thread overview]
Message-ID: <C4ACB40E.2477E%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <0122C7C995D32147B66BF4F440D301630167FE74@pdsmsx415.ccr.corp.intel.com>
On 23/7/08 10:04, "Han, Weidong" <weidong.han@intel.com> wrote:
> 1) Add a check in domain_context_unmap_one(), don't remove the device
> from dom0 if it has RMRR. This check is added yesterday. But it's not
> clean enough. The device is not assigned to dom0, while it is mapped in
> dom0 VT-d page table.
>
> 2) Establish a separate RMRR page table. If the device with RMRR is
> removed from dom0, unmap it from dom0 VT-d page table, instead map it to
> the separate RMRR page table. This solution is clean, but it introduces
> a new VT-d page table. Currently each domain has only one VT-d page
> table.
>
> What's your opinions?
So this would be one extra VT-d pagetable, for the whole system, which would
be the fallback location for RMRR mappings for devices which are currently
not assigned to any domain? Thus allowing firmware to successfully initiate
DMA operations on those devices? Sounds sensible.
-- Keir
next prev parent reply other threads:[~2008-07-23 9:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 9:04 Dom0 hypercall for adding and removing PCI devices Han, Weidong
2008-07-23 9:10 ` Keir Fraser [this message]
2008-07-23 9:26 ` Han, Weidong
2008-07-23 9:28 ` Keir Fraser
2008-07-23 18:07 ` Espen Skoglund
[not found] ` <0122C7C995D32147B66BF4F440D301630159F319@pdsmsx415.ccr.corp.intel.com>
2008-07-24 8:20 ` Han, Weidong
2008-07-24 8:23 ` Keir Fraser
2008-07-24 8:32 ` Han, Weidong
2008-07-24 8:37 ` Keir Fraser
2008-07-24 8:43 ` Tian, Kevin
2008-07-24 8:47 ` Keir Fraser
2008-07-24 9:14 ` Han, Weidong
2008-07-24 9:27 ` Keir Fraser
2008-07-24 14:16 ` Espen Skoglund
2008-07-24 14:47 ` Tian, Kevin
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=C4ACB40E.2477E%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=espen.skoglund@netronome.com \
--cc=joshua.levasseur@netronome.com \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=xin.b.li@intel.com \
--cc=yunhong.jiang@intel.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.