All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: seabios@seabios.org, kvm@vger.kernel.org
Subject: Re: [PATCH] support piix PAM registers in KVM
Date: Tue, 21 Sep 2010 16:06:01 -0300	[thread overview]
Message-ID: <20100921190601.GA25269@amt.cnet> (raw)
In-Reply-To: <20100921123142.GB11145@redhat.com>

On Tue, Sep 21, 2010 at 02:31:42PM +0200, Gleb Natapov wrote:
> Without this BIOS fails to remap 0xf0000 memory from ROM to RAM so writes
> to F-segment modify ROM content instead of memory copy. Since QEMU does
> not reloads ROMs during reset on next boot modified copy of BIOS is used.
> 
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
> diff --git a/hw/piix_pci.c b/hw/piix_pci.c
> index 933ad86..0bf435d 100644
> --- a/hw/piix_pci.c
> +++ b/hw/piix_pci.c
> @@ -99,10 +99,6 @@ static void i440fx_update_memory_mappings(PCII440FXState *d)
>      int i, r;
>      uint32_t smram, addr;
>  
> -    if (kvm_enabled()) {
> -        /* FIXME: Support remappings and protection changes. */
> -        return;
> -    }
>      update_pam(d, 0xf0000, 0x100000, (d->dev.config[I440FX_PAM] >> 4) & 3);
>      for(i = 0; i < 12; i++) {
>          r = (d->dev.config[(i >> 1) + (I440FX_PAM + 1)] >> ((i & 1) * 4)) & 3;
> --
> 			Gleb.

Ugh, we should support ro slots to avoid such kind of problems...

Applied, thanks.

  reply	other threads:[~2010-09-22 20:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 12:31 [PATCH] support piix PAM registers in KVM Gleb Natapov
2010-09-21 19:06 ` Marcelo Tosatti [this message]
2010-09-25 15:43   ` Kevin O'Connor
2011-06-15 11:58 ` Jason Krieg
2011-06-15 13:17   ` Avi Kivity
2011-06-15 13:54     ` Jason Krieg
2011-06-15 13:57       ` Avi Kivity
2011-06-15 13:59         ` Avi Kivity
2011-06-15 14:11           ` Jason Krieg
2011-06-15 14:25             ` Jason Krieg
2011-06-15 15:16           ` Jason Krieg
2011-06-15 15:19             ` Avi Kivity
2011-06-15 15:27               ` Jason Krieg
2011-06-19 12:45                 ` Avi Kivity

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=20100921190601.GA25269@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=seabios@seabios.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.