From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
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>,
"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 13:30:08 +0100 [thread overview]
Message-ID: <4FE46550.20300@citrix.com> (raw)
In-Reply-To: <4FE47F28020000780008B686@nat28.tlf.novell.com>
On 22/06/12 13:20, Jan Beulich wrote:
>>> Because, just like for normal, non-PCI based serial ones, ports
>>> that Xen doesn't use should remain usable by Dom0. For
>>> example, I have a PCI card with two serial and one parallel
>>> ports, so with Xen using one serial port for itself, there's no
>>> reason not to allow Dom0 to use the other or the parallel one.
>> I apologize. I originally used the term 'device' when I intended to use
>> 'function', so I think we are arguing for the same point.
> And I understood you meaning so - from a PCI terminology pov.
> Multi-function here, however, means multiple serial/parallel ports
> within a single PCI function (PCI_CLASS_COMMUNICATION_MULTISERIAL
> or PCI_CLASS_COMMUNICATION_OTHER). Hence we shouldn't hide a
> full S:B:D.F just because we use some portion of it.
>
> Jan
>
Ah right. Yes. Perhaps then a warning on the Xen console if Xen
encounters such a device.
--
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 12:30 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
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 [this message]
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=4FE46550.20300@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=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.