public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [RFC][PATCH] qemu-kvm: Drop vga dirty logging workarounds
Date: Mon, 15 Nov 2010 14:26:36 +0100	[thread overview]
Message-ID: <4CE1350C.3080304@siemens.com> (raw)
In-Reply-To: <4CE132B2.9050507@redhat.com>

Am 15.11.2010 14:16, Avi Kivity wrote:
> On 11/15/2010 12:32 PM, Jan Kiszka wrote:
>> These diffs to upstream should all date back to the days qemu-kvm
>> supported vga dirty logging with restricted/broken kvm kernel modules.
>> We no longer do, so there is no need for those workarounds. Even worse
>> they can trigger internal bug checks these days:
>>
>> BUG: kvm_dirty_pages_log_change: invalid parameters 00000000000a8000-00000000000affff
> 
> I'd like to apply this.  What kind of testing has this seen?  autotest 
> likely isn't a good enough test.

No systematic testing.

It's based on the fact that I'm not aware of any VGA issues in upstream
when KVM is enabled, on the fact that explicit log enable/disable became
obsolete when switching to upstream's logging backend, and the annoying
BUG messages only issued under qemu-kvm. There just remains a slight
uncertainty about what mark_dirty and s[123] were once doing - or may
still be useful for.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-11-15 13:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 10:32 [RFC][PATCH] qemu-kvm: Drop vga dirty logging workarounds Jan Kiszka
2010-11-15 13:16 ` Avi Kivity
2010-11-15 13:26   ` Jan Kiszka [this message]
2010-11-15 13:29     ` 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=4CE1350C.3080304@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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