From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>, xiantao.zhang@intel.com
Subject: Re: [PATCH 1/1] x86/AMD: Fix setup ssss:bb:dd:f for d0 failed
Date: Fri, 30 Aug 2013 19:03:54 -0500 [thread overview]
Message-ID: <522132EA.1090309@amd.com> (raw)
In-Reply-To: <52206F5C02000078000EFA14@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 1203 bytes --]
On 8/30/2013 3:09 AM, Jan Beulich wrote:
>> Sorry for didn't get a chance to follow up with this sooner. Ok, I see
>> >the code you mentioned.
>> >However, if I understand this correctly, it is also mapping the bridge
>> >to the domU
>> >along with the end-device. This is not the same as what you mentioned
>> >that the bridge should
>> >be mapped to only Dom0.
> I don't think I ever said this. Whether we're talking about DomU or
> Dom0 here is irrelevant. I'm just pointing out that bridges do get
> mappings established for them whenever a device behind them gets
> mapped.
>
> Jan
Ok, I think Iunderstand it a bit more now. I'll modify the code to skip
only the hostbridge when they are not
specifiedin the IVRS as it is not needed to be mapped to adomain. I'll
send out the code shortly.
However, I also found out that the current AMD IOMMU driver maps other
type of bridges
(i.e. DEV_TYPE_PCIe_BRIDGE, DEV_TYPE_PCIe2PCI_BRIDGE, and
DEV_TYPE_LEGACY_PCI_BRIDGE) _only_ to Dom0,
and they won't get reassignedwhen the end point devices downstreamare
assignedto other domain.
I don't think this is correct.I'll work on this and and send out a
separate patch for this.
Thank you,
Suravee
[-- Attachment #1.2: Type: text/html, Size: 5039 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-08-31 0:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 2:40 [PATCH 1/1] x86/AMD: Fix setup ssss:bb:dd:f for d0 failed suravee.suthikulpanit
2013-08-07 2:42 ` Suravee Suthikulanit
2013-08-07 8:33 ` Stefan Bader
2013-08-08 11:12 ` Stefan Bader
2013-08-08 11:49 ` Jan Beulich
2013-08-08 12:07 ` Stefan Bader
2013-08-08 12:29 ` Jan Beulich
2013-08-08 12:35 ` Stefan Bader
2013-08-07 7:33 ` Jan Beulich
2013-08-07 15:31 ` Suravee Suthikulanit
2013-08-07 15:42 ` Jan Beulich
2013-08-07 19:20 ` Suravee Suthikulanit
2013-08-08 6:38 ` Jan Beulich
2013-08-30 1:25 ` Suravee Suthikulpanit
2013-08-30 8:09 ` Jan Beulich
2013-08-31 0:03 ` Suravee Suthikulpanit [this message]
2013-08-07 9:34 ` Andrew Cooper
2013-08-07 9:57 ` 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=522132EA.1090309@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.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.