From: Roman Shaposhnik <roman@zededa.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: "jgross@suse.com" <jgross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
"jbeulich@suse.com" <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx
Date: Mon, 19 Aug 2019 19:03:33 -0700 [thread overview]
Message-ID: <CAMmSBy-QF3avMhbsQOG5AOdEFXyX7pZLcg-wiOmg0qqfKdXhug@mail.gmail.com> (raw)
In-Reply-To: <20190819081637.dg2k5kv54o72wrty@Air-de-Roger>
On Mon, Aug 19, 2019 at 1:16 AM Roger Pau Monné <roger.pau@citrix.com> wrote:
>
> On Sun, Aug 18, 2019 at 10:00:17PM -0700, Roman Shaposhnik wrote:
> > Hi Roger!
> >
> > Some good news, some bad news ;-)
> >
> > Good news is that on the newer BIOS, your original patch seems to work fine.
> >
> > IOW, with newer BIOS:
> > 1. without your original patch I see garbled screen
> > 2. with your original patch everything boots normally.
>
> That would be my expectation.
>
> > Bad news is that with older BIOS, your original patch seems to either
> > work or not depending on the BIOS some of the BIOS settings.
> >
> > IOW, with older BIOS:
> > 1. without your original patch I see garbled screen (regardless of
> > BIOS settings)
> > 2. with your original patch AND resetting to a factory defaults of
> > BIOS settings -- everything boots normally
> > 3. when I load up our custom settings -- the only thing that can
> > boot normally is the latest patch
> >
> > So, would it make sense and commit your original patch for now? This
> > will unlock me with newer BIOSes on these boxes.
>
> I think so, can you please provide a tested-by to the patch:
>
> https://lists.xenproject.org/archives/html/xen-devel/2019-07/msg01547.html
Done.
> Feel free to also note the weird behaviour you are seeing with this
> box and firmware version.
>
> > As for the older BIOSes, I still feel that it would be great for Xen
> > to boot more reliably -- especially since Xen 4.10 seems to be doing
> > fine regardless of BIOS version and settings.
> >
> > What do you think?
>
> We could add a quirk for this fimrware version and hardware if we know
> exactly what the issue is. Have you figured out if it's related to the
> flush? ie: iommu_iotlb_flush vs iommu_iotlb_flush_all vs iommu_flush_all?
I am actually at Open Source Summit in San Diego right now -- away from
my lab. I'll try to capture as much data on Fri as possible when I come back.
Please stay tuned.
Thanks,
Roman.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-08-20 2:04 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 19:31 [Xen-devel] [BUG] After upgrade to Xen 4.12.0 iommu=no-igfx Roman Shaposhnik
2019-07-19 20:02 ` Roman Shaposhnik
2019-07-22 8:20 ` Paul Durrant
2019-07-22 11:48 ` Roger Pau Monné
2019-07-22 11:54 ` Paul Durrant
2019-07-22 13:48 ` Roger Pau Monné
2019-07-22 14:03 ` Paul Durrant
2019-07-22 14:39 ` Roger Pau Monné
2019-07-22 15:02 ` Paul Durrant
2019-07-22 15:21 ` Roger Pau Monné
2019-07-22 23:36 ` Roman Shaposhnik
2019-07-22 23:47 ` Andrew Cooper
2019-07-23 17:32 ` Roman Shaposhnik
2019-07-23 17:35 ` Andrew Cooper
2019-07-23 17:48 ` Roman Shaposhnik
2019-07-23 17:50 ` Andrew Cooper
2019-07-23 17:58 ` Roman Shaposhnik
2019-07-23 18:12 ` Andrew Cooper
2019-07-23 18:25 ` Roman Shaposhnik
2019-07-26 7:58 ` Jan Beulich
2019-07-30 17:56 ` Roman Shaposhnik
2019-07-31 8:34 ` Jan Beulich
2019-07-31 8:58 ` Andrew Cooper
2019-07-31 9:30 ` Jan Beulich
2019-07-31 19:37 ` Roman Shaposhnik
2019-07-24 12:00 ` Jan Beulich
2019-07-24 12:04 ` Jan Beulich
2019-07-24 11:23 ` Andrew Cooper
2019-07-24 11:40 ` Andrew Cooper
2019-07-24 14:11 ` Roger Pau Monné
2019-07-26 0:47 ` Roman Shaposhnik
2019-07-26 9:35 ` Roger Pau Monné
2019-07-30 9:21 ` Roger Pau Monné
2019-07-30 17:55 ` Roman Shaposhnik
2019-07-31 8:31 ` Jan Beulich
2019-07-31 8:36 ` Roger Pau Monné
2019-07-31 8:43 ` Roger Pau Monné
2019-07-31 19:35 ` Roman Shaposhnik
2019-07-31 19:46 ` Andrew Cooper
2019-07-31 21:03 ` Roman Shaposhnik
2019-08-01 8:15 ` Roger Pau Monné
2019-08-01 18:25 ` Roman Shaposhnik
2019-08-02 8:05 ` Roger Pau Monné
2019-08-06 16:17 ` Roger Pau Monné
2019-08-06 21:48 ` Roman Shaposhnik
2019-08-07 7:08 ` Jan Beulich
2019-08-07 9:57 ` Roger Pau Monné
2019-08-07 10:03 ` Jan Beulich
2019-08-07 7:35 ` Roger Pau Monné
2019-08-07 8:31 ` Jan Beulich
2019-08-07 10:17 ` Roger Pau Monné
2019-08-12 8:57 ` Roger Pau Monné
2019-08-13 19:24 ` Roman Shaposhnik
2019-08-14 8:06 ` Roger Pau Monné
2019-08-19 5:00 ` Roman Shaposhnik
2019-08-19 8:16 ` Roger Pau Monné
2019-08-20 2:03 ` Roman Shaposhnik [this message]
2019-08-01 7:35 ` Jan Beulich
2019-07-31 19:30 ` Roman Shaposhnik
2019-08-01 8:45 ` Roger Pau Monné
2019-08-01 18:19 ` Roman Shaposhnik
2019-07-20 16:39 ` Andrew Cooper
2019-07-22 8:03 ` Paul Durrant
2019-07-24 17:42 ` Rich Persaud
2019-07-26 1:13 ` Roman Shaposhnik
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=CAMmSBy-QF3avMhbsQOG5AOdEFXyX7pZLcg-wiOmg0qqfKdXhug@mail.gmail.com \
--to=roman@zededa.com \
--cc=Paul.Durrant@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.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).