From: Zachary Amsden <zach@vmware.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: Vmware crashes if compress/misc.c scrolls?
Date: Thu, 21 Jun 2007 14:54:37 -0700 [thread overview]
Message-ID: <467AF39D.5020606@vmware.com> (raw)
In-Reply-To: <4679CA51.3080600@zytor.com>
H. Peter Anvin wrote:
> Jeremy Fitzhardinge wrote:
>
>> H. Peter Anvin wrote:
>>
>>> Jeremy Fitzhardinge wrote:
>>>
>>>
>>>> You mean "is a real failure"? Or "is triggered by particular
>>>> instructions"? It seems profoundly bogus (as in, surely DOS or
>>>> something reads the framebuffer).
>>>>
>>>>
>>>>
>>> A real failure (although only triggered from some variant of protected
>>> mode -- paging off?)
>>>
>>>
>> Oh, it only happens in protected mode? So the answer to "how does the
>> shadow framebuffer get populated?" is "real mode does it before
>> switching to protected mode".
>>
>>
>
> Sure, but that means frobbing the boot parameter structure, with
> associated problems. I guess I'm not inherently opposed to it, but I'd
> like to understand if there is a cleaner workaround first.
>
I'm failing to understand exactly what the failure here is. Can you
provide sample code that generates the problem? Surely, it should be
possible to read the framebuffer.
Zach
next prev parent reply other threads:[~2007-06-21 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 23:44 Vmware crashes if compress/misc.c scrolls? H. Peter Anvin
2007-06-21 0:07 ` Jeremy Fitzhardinge
2007-06-21 0:17 ` H. Peter Anvin
2007-06-21 0:21 ` Jeremy Fitzhardinge
2007-06-21 0:25 ` H. Peter Anvin
2007-06-21 0:27 ` Jeremy Fitzhardinge
2007-06-21 0:46 ` H. Peter Anvin
2007-06-21 21:54 ` Zachary Amsden [this message]
2007-06-22 2:22 ` H. Peter Anvin
2007-06-22 2:34 ` Zachary Amsden
2007-06-22 3:09 ` Jeremy Fitzhardinge
2007-08-04 4:48 ` Zachary Amsden
2007-08-04 9:24 ` Andi Kleen
2007-08-04 12:08 ` Zachary Amsden
2007-08-04 14:19 ` Zachary Amsden
2007-08-04 20:14 ` [syslinux] " H. Peter Anvin
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=467AF39D.5020606@vmware.com \
--to=zach@vmware.com \
--cc=hpa@zytor.com \
--cc=virtualization@lists.osdl.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).