From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Andre Przywara <andre.przywara@amd.com>,
Christoph Egger <christoph.egger@amd.com>,
"Keir (Xen.org)" <keir@xen.org>,
Eddie Dong <eddie.dong@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Wei Wang <wei.wang2@amd.com>, Jan Beulich <JBeulich@suse.com>,
"xiantao.zhang@intel.com" <xiantao.zhang@intel.com>
Subject: Re: Other PCI devices to mark mark as read-only for dom0
Date: Fri, 22 Jun 2012 11:11:53 +0100 [thread overview]
Message-ID: <4FE444E9.8080809@citrix.com> (raw)
In-Reply-To: <1783278186.20120622112436@eikelenboom.it>
On 22/06/12 10:24, Sander Eikelenboom wrote:
>
>> Are there any others I have overlooked, or reasons that dom0 should be
>> able to write to these areas?
> Make devices specified for pci passthrough be really hidden and "owned" by the hyperviso ?
> - which can in turn delegate ownership to a domain (including dom0)
> - If a domain is destroyed, the hypervisor resets the device and becomes the owner again instead of dom0 ?
Why?
Currently this is covered by unbinding the dom0 driver and binding
pciback to the device. Well behaved device drivers will not cause problems.
This way, the toolstack has control of which domains own what.
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next prev parent reply other threads:[~2012-06-22 10:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 9:04 Other PCI devices to mark mark as read-only for dom0 Andrew Cooper
2012-06-22 9:24 ` Sander Eikelenboom
2012-06-22 10:11 ` Andrew Cooper [this message]
2012-06-22 9:43 ` Jan Beulich
2012-06-22 10:08 ` Andrew Cooper
2012-06-22 11:23 ` Jan Beulich
2012-06-22 12:06 ` Andrew Cooper
2012-06-22 12:20 ` Jan Beulich
2012-06-22 12:30 ` Andrew Cooper
2012-06-22 11:30 ` Jan Beulich
2012-06-22 12:27 ` Andrew Cooper
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=4FE444E9.8080809@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=andre.przywara@amd.com \
--cc=christoph.egger@amd.com \
--cc=eddie.dong@intel.com \
--cc=keir@xen.org \
--cc=linux@eikelenboom.it \
--cc=wei.wang2@amd.com \
--cc=xen-devel@lists.xen.org \
--cc=xiantao.zhang@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.