xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, Wei Wang2 <wei.wang2@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: AMD IOMMU related boot failure due to page coalescing c/s 23767
Date: Fri, 19 Aug 2011 17:29:20 +0100	[thread overview]
Message-ID: <CA744DF0.1F790%keir.xen@gmail.com> (raw)
In-Reply-To: <20046.35926.517204.166312@mariner.uk.xensource.com>

On 19/08/2011 17:16, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:

> Wei Wang2 writes ("Re: AMD IOMMU related boot failure due to page coalescing
> c/s 23767"):
>> Oh, that is another issue that I haven't got time to look at...
>> you could use iommu=no-perdev-vector-map to workaround this.
> 
> Err.  Right.  Is there perhaps some other recent changeset that needs
> fixing or reverting ?  That would make five ...

You could try nobbling c/s 23754. E.g., change the static initialiser for
iommu_amd_perdev_vector_map (defined in drivers/passthrough/iommu.c,
somewhat oddly) to 0.

 -- Keir

> Ian.

  reply	other threads:[~2011-08-19 16:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 13:19 AMD IOMMU related boot failure due to page coalescing c/s 23767 Ian Jackson
2011-08-19 13:55 ` Wei Wang2
2011-08-19 13:58   ` Logging xen dmesg John Backes
2011-08-19 14:24     ` Pasi Kärkkäinen
2011-08-19 14:25     ` Keir Fraser
2011-08-19 14:55 ` AMD IOMMU related boot failure due to page coalescing c/s 23767 Wei Wang2
2011-08-19 15:57   ` Ian Jackson
2011-08-19 15:59     ` Ian Jackson
2011-08-19 16:12       ` Wei Wang2
2011-08-19 16:16         ` Ian Jackson
2011-08-19 16:29           ` Keir Fraser [this message]
2011-08-19 16:30         ` Ian Jackson
2011-08-22 11:29       ` George Dunlap

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=CA744DF0.1F790%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=wei.wang2@amd.com \
    --cc=xen-devel@lists.xensource.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 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).