qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin O'Connor <kevin@koconnor.net>
To: Gleb Natapov <gleb@redhat.com>
Cc: ghammer@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/8] qemu-ga: add support for Windows
Date: Tue, 7 Feb 2012 19:35:34 -0500	[thread overview]
Message-ID: <20120208003534.GA8786@morn.localdomain> (raw)
In-Reply-To: <20120207084439.GA23536@redhat.com>

On Tue, Feb 07, 2012 at 10:44:39AM +0200, Gleb Natapov wrote:
> On Mon, Feb 06, 2012 at 07:09:42PM -0500, Kevin O'Connor wrote:
> > Perhaps a semantic distinction, but I don't consider that to be a
> > seabios defect.
> > 
> Non optimal default. The default didn't change BTW, but it was config
> parameter before and we changed it for RHEL. Now config parameter is
> gone.

Config parameter moved from compile time to runtime.  But I agree it
is unfortunate that knowledge of that didn't get to the right people.

> > In any case, I don't think this was addressed.  Gerd published a patch
> > that can address this in qemu:
> > http://www.seabios.org/pipermail/seabios/2012-January/002944.html
> > 
> Strictly speaking the patch is incorrect since it introduces the file
> for all architectures, but I do not think qemu is the right place to
> tune SeaBIOS defaults. I propose this patch instead:
[...]
>      // Load some config settings that impact VGA.
>      EnforceChecksum = romfile_loadint("etc/optionroms-checksum", 1);
> -    S3ResumeVgaInit = romfile_loadint("etc/s3-resume-vga-init", 0);
> +    S3ResumeVgaInit = romfile_loadint("etc/s3-resume-vga-init", !CONFIG_COREBOOT);
>      ScreenAndDebug = romfile_loadint("etc/screen-and-debug", 1);

I'm concerned about the VGA passthrough case.  (I know that's not
common and has other issues, but I also know several people have been
working with it.)  As near as I can tell, running the VGA rom on S3
resume has as much chance of breaking things as helping things.  It's
fine for the cirrus/bochsvga vgaroms that are totally under our
control, but it'd be an open guess for any third-party code.  (Again,
if someone has documentation to the contrary please let me know.)

So, compiling this into SeaBIOS doesn't seems like the right choice to
me.

-Kevin

  reply	other threads:[~2012-02-08  0:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 19:58 [Qemu-devel] [PATCH v2 0/8] qemu-ga: add support for Windows Michael Roth
2012-02-02 19:58 ` [Qemu-devel] [PATCH v2 1/8] qemu-ga: Add schema documentation for types Michael Roth
2012-02-02 19:58 ` [Qemu-devel] [PATCH v2 2/8] qemu-ga: move channel/transport functionality into wrapper class Michael Roth
2012-02-02 19:58 ` [Qemu-devel] [PATCH v2 3/8] qemu-ga: separate out common commands from posix-specific ones Michael Roth
2012-02-02 19:58 ` [Qemu-devel] [PATCH v2 4/8] qemu-ga: rename guest-agent-commands.c -> commands-posix.c Michael Roth
2012-02-02 19:58 ` [Qemu-devel] [PATCH v2 5/8] qemu-ga: fixes for win32 build of qemu-ga Michael Roth
2012-02-02 19:58 ` [Qemu-devel] [PATCH v2 6/8] qemu-ga: add initial win32 support Michael Roth
2012-02-02 19:58 ` [Qemu-devel] [PATCH v2 7/8] qemu-ga: add Windows service integration Michael Roth
2012-02-02 19:59 ` [Qemu-devel] [PATCH v2 8/8] qemu-ga: add win32 guest-shutdown command Michael Roth
2012-02-03 14:18 ` [Qemu-devel] [PATCH v2 0/8] qemu-ga: add support for Windows Luiz Capitulino
2012-02-03 16:37   ` Michael Roth
2012-02-03 16:45     ` Luiz Capitulino
2012-02-03 17:23       ` Michael Roth
2012-02-03 19:16         ` Luiz Capitulino
2012-02-04 15:34           ` Kevin O'Connor
2012-02-06 15:43             ` Luiz Capitulino
2012-02-07  0:09               ` Kevin O'Connor
2012-02-07  8:44                 ` Gleb Natapov
2012-02-08  0:35                   ` Kevin O'Connor [this message]
2012-02-08  7:18                     ` Gleb Natapov
2012-02-08 13:25                       ` Kevin O'Connor

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=20120208003534.GA8786@morn.localdomain \
    --to=kevin@koconnor.net \
    --cc=aliguori@us.ibm.com \
    --cc=ghammer@redhat.com \
    --cc=gleb@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.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).