From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Keir Fraser <keir@xen.org>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86/boot: Fix BIOS memory corruption on certain IBM systems
Date: Wed, 04 Dec 2013 18:59:25 +0000 [thread overview]
Message-ID: <CEC52C0D.692F1%keir.xen@gmail.com> (raw)
In-Reply-To: <529F16450200007800109EC4@nat28.tlf.novell.com>
On 04/12/2013 10:47, "Jan Beulich" <JBeulich@suse.com> wrote:
>>>> * Declare that our target operating mode is long mode.
>>>> * Initialise 32-bit registers since some buggy BIOSes depend on
>>>> it.
>>>> */
>>>> + xor %ecx,%ecx
>>>> + xor %edx,%edx
>>>> + xor %esi,%esi
>>>> + xor %edi,%edi
>>>> + xor %ebp,%ebp
>>>> movl $0xec00,%eax # declare target operating mode
>>>> movl $0x0002,%ebx # long mode
>>>> int $0x15
>>> ... I can't really see the value of the change here: If we're to
>>> work around theoretical BIOS bugs, we'd need to do this prior to
>>> each BIOS call. That's surely overkill. Therefore let's focus on
>>> what is needed to work around _known_ BIOS bugs.
>>
>> I admit that I was leaning on the cautious side with these changes.
>>
>> I can take them out if you think that would be better, but given this
>> int was already flagged as buggy in some BIOSes, and we have found
>> another case, I think covering all GPRs is the safer option.
>
> As said - I doubt this would help much. I'd really prefer at least this
> part of the patch to be taken out again. Unless Keir is specifically of
> the opposite opinion...
The change does kind of fit with the comment immediately above though.
Overall I don't really care that much either way.
-- Keir
next prev parent reply other threads:[~2013-12-04 18:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 20:34 [PATCH] x86/boot: Fix BIOS memory corruption on certain IBM systems Andrew Cooper
2013-12-04 7:17 ` Keir Fraser
2013-12-04 10:03 ` Jan Beulich
2013-12-04 10:35 ` Andrew Cooper
2013-12-04 10:47 ` Jan Beulich
2013-12-04 18:59 ` Keir Fraser [this message]
2013-12-04 10:09 ` 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=CEC52C0D.692F1%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=keir@xen.org \
--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).