From: "Zhang, Xiantao" <xiantao.zhang@intel.com>
To: Jan Beulich <JBeulich@suse.com>,
"Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "wei.huang2@amd.com" <wei.huang2@amd.com>,
"weiwang.dd@gmail.com" <weiwang.dd@gmail.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: iommu=dom0-passthrough behavior
Date: Fri, 16 Nov 2012 06:21:59 +0000 [thread overview]
Message-ID: <B6C2EB9186482D47BD0C5A9A4834564403384F23@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <50A4BE6D02000078000A8B89@nat28.tlf.novell.com>
> >> Which, if I'm not mistaken, could be implemented entirely independent
> >> of "iommu=dom0-passthrough". I'll see if that helps on the offending
> system.
> >
> > I mean this one:
> >>>c) we could provide a command line option to allow fake devices to be
> >>>create
> >
> > Yes, I don't think "iommu=dom0-passthrough" can meet your requirement.
> > We had better add a cmd line option to pass the related information
> > to hypervisor and VT-d can create the pass-through context entry for
> > the undetectable device.
>
> You misunderstood: What I was saying (and seeking confirmation) is that I
> don't think the new command line option would need to have any
> connection to the existing, non-suitable one. In particular, for it to take effect,
> "iommu=dom0-passthrough"
> wouldn't need to be specified at all.
Okay. Back to your customer's issue, I don't think we have a clean solution if the device can't be detected by hypervisor. We only can figure out how to workaround this issue through a new command line option.
BTW, if the device can't be detected, how to load its driver by OS ?
Xiantao
next prev parent reply other threads:[~2012-11-16 6:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 14:30 iommu=dom0-passthrough behavior Jan Beulich
2012-11-13 0:11 ` Zhang, Yang Z
2012-11-13 8:07 ` Jan Beulich
2012-11-13 8:50 ` Zhang, Xiantao
2012-11-13 9:41 ` Jan Beulich
2012-11-13 11:13 ` Zhang, Yang Z
2012-11-13 11:24 ` Jan Beulich
2012-11-13 15:02 ` Zhang, Xiantao
2012-11-13 15:29 ` Jan Beulich
2012-11-14 0:37 ` Zhang, Xiantao
2012-11-14 13:40 ` Jan Beulich
2012-11-15 8:23 ` Zhang, Xiantao
2012-11-15 9:05 ` Jan Beulich
2012-11-16 6:21 ` Zhang, Xiantao [this message]
2012-11-16 8:22 ` Jan Beulich
2012-11-16 9:26 ` Jan Beulich
2012-11-16 9:43 ` Zhang, Xiantao
2012-11-16 9:53 ` Jan Beulich
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=B6C2EB9186482D47BD0C5A9A4834564403384F23@SHSMSX101.ccr.corp.intel.com \
--to=xiantao.zhang@intel.com \
--cc=JBeulich@suse.com \
--cc=wei.huang2@amd.com \
--cc=weiwang.dd@gmail.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.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.