xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Julien Grall' <julien.grall@arm.com>, Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
	Lars Kurth <lars.kurth@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86/boot: re-arrange how/when we do disk I/O
Date: Mon, 26 Jun 2017 15:14:50 +0000	[thread overview]
Message-ID: <e2e182ef72534b59baeb3e64b8712026@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <ce6de5e4-40c7-37f5-de2a-9c5d623e8709@arm.com>

> -----Original Message-----
> From: Julien Grall [mailto:julien.grall@arm.com]
> Sent: 26 June 2017 14:04
> To: Jan Beulich <JBeulich@suse.com>
> Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>; Paul Durrant
> <Paul.Durrant@citrix.com>; xen-devel <xen-devel@lists.xenproject.org>;
> Lars Kurth <lars.kurth@citrix.com>
> Subject: Re: [PATCH] x86/boot: re-arrange how/when we do disk I/O
> 
> Hi,
> 
> On 12/06/17 17:59, Julien Grall wrote:
> > Hi Jan,
> >
> > On 12/06/17 16:27, Jan Beulich wrote:
> >>>>> On 12.06.17 at 17:11, <JBeulich@suse.com> wrote:
> >>> We place the trampoline no lower than at 256k, so we have ample space
> >>> to read the MBRs of BIOS disks into an aligned buffer right below the
> >>> trampoline (not doing so has been found to be a problem on a buggy
> BIOS
> >>> coming with a Skull Canyon NUC). To facilitate that move MBR reading
> >>> past EDD info retrieval.
> >>>
> >>> Also add a wrap check to the EDD info retrieval loop, to match that in
> >>> the MBR reading one.
> >>>
> >>> Reported-by: Paul Durrant <Paul.Durrant@citrix.com>
> >>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> >>> Tested-by: Paul Durrant <Paul.Durrant@citrix.com>
> >>
> >> As to 4.9 inclusion, I think I should have mentioned right away
> >> that such a change of course isn't without risk: We're trying to
> >> work around a BIOS bug by relying on other information
> >> coming from the BIOS being correct / usable. Obviously there is
> >> the risk that this regresses with some other BIOS having a bug
> >> elsewhere.
> >>
> >> I'm therefore leaning towards suggesting to take this change
> >> only for master right now, and consider pulling it into the 4.9
> >> branch in a couple of weeks time, when the patch has seen at
> >> least a little more testing on a wider set of systems.
> >
> > I agree on your conclusion. I would suggest to add a release note if it
> > is not backported before the release.
> >
> > I will keep track of this.
> 
> I haven't seen any update on this. Can someone describe briefly the
> problem so we can add it in the section "known issues" of the release notes?
> 

Julien,

  The symptom is an apparent failure to progress beyond the grub stage when trying to boot Xen on a skull canyon. You see the messages about loading the modules, but then nothing more except maybe a reset of the vga mode (depending on what your xen command line looks like).
  The problem is a buggy BIOS which wedges in the int13 handler in some cases. Xen 4.9 happens to tickle this bug whereas Xen 4.8 got away with it.

  Cheers,

    Paul

> Cheers,
> 
> --
> Julien Grall

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

  reply	other threads:[~2017-06-26 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-12 15:11 [PATCH] x86/boot: re-arrange how/when we do disk I/O Jan Beulich
2017-06-12 15:27 ` Jan Beulich
2017-06-12 16:59   ` Julien Grall
2017-06-26 13:03     ` Julien Grall
2017-06-26 15:14       ` Paul Durrant [this message]
2017-06-12 15:33 ` Andrew Cooper

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=e2e182ef72534b59baeb3e64b8712026@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth@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).