xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Brian Woods <brian.woods@amd.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [Xen-devel] [PATCH] AMD/IOMMU: revert "amd/iommu: assign iommu devices to Xen"
Date: Tue, 4 Jun 2019 10:48:07 +0200	[thread overview]
Message-ID: <20190604084807.3hevw5rh6qu5w3ul@Air-de-Roger> (raw)
Message-ID: <20190604084807.bk-n1RvIWkuYSmHQWrmKCatFN-0axg2pmnngXK_eW2g@z> (raw)
In-Reply-To: <5CF519E902000078002349FF@prv1-mh.provo.novell.com>

On Mon, Jun 03, 2019 at 07:00:25AM -0600, Jan Beulich wrote:
> This reverts commit b6bd02b7a877f9fac2de69e64d8245d56f92ab25. The change
> was redundant with amd_iommu_detect_one_acpi() already calling
> pci_ro_device().
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

I think this needs to be squashed together with your `AMD/IOMMU: don't
"add" IOMMUs` patch, or else PVH dom0 will break because
update_paging_mode will find devices not behind an IOMMU assigned to
dom0, thus returning an error and crashing dom0.

Thanks, Roger.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-06-04  8:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 13:00 [PATCH] AMD/IOMMU: revert "amd/iommu: assign iommu devices to Xen" Jan Beulich
2019-06-03 13:00 ` [Xen-devel] " Jan Beulich
2019-06-04  8:48 ` Roger Pau Monné [this message]
2019-06-04  8:48   ` Roger Pau Monné
2019-06-04  9:29   ` Jan Beulich
2019-06-04  9:29     ` [Xen-devel] " Jan Beulich
2019-06-04 13:02   ` Jan Beulich
2019-06-04 16:20     ` Roger Pau Monné
2019-06-05  7:55       ` Jan Beulich
2019-06-05  8:02         ` Jan Beulich
2019-06-05  9:52           ` Roger Pau Monné
2019-06-05  9:06         ` Roger Pau Monné
2019-06-05  9:12           ` Andrew Cooper
2019-06-05  9:14           ` Jan Beulich
2019-06-04  9:04 ` Andrew Cooper
2019-06-04  9:04   ` [Xen-devel] " Andrew Cooper
2019-06-04  9:21   ` Jan Beulich
2019-06-04  9:21     ` [Xen-devel] " Jan Beulich
2019-06-04 12:08   ` Jan Beulich
2019-06-19 16:29 ` Woods, Brian

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=20190604084807.3hevw5rh6qu5w3ul@Air-de-Roger \
    --to=roger.pau@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=brian.woods@amd.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).