From: Daniel Bareiro <daniel-listas@gmx.net>
To: kvm@vger.kernel.org
Subject: Re: kvm-88: KVM_APIC_READ: read reserved register b0
Date: Sun, 30 Aug 2009 12:28:47 -0300 [thread overview]
Message-ID: <20090830152847.GC3014@defiant.freesoftware.org> (raw)
In-Reply-To: <20090830114959.GV30093@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
On Sunday, 30 August 2009 14:49:59 +0300,
Gleb Natapov wrote:
> > > This printk no longer exists in upstream kvm.
Between emails of the list, I found the suggestion to apply this [1]
patch, but I suppose that not yet it must be applied in the download
version.
> > just to be curious: What was the reason to add that debugging
> > message?
> Because well behaved OS shouldn't read write only register.
> Unfortunately older Linux kernels sometimes uses xchg to access
> eoi(b0) apic register which will generate read/write.
According to I see, guest kernel is 2.6.26-2-486. Apparently, after a
reboot, the OS boots with it instead of amd64 kernel. After boot with
amd64 kernel, no longer flooding in syslog takes place.
I didn't test yet, but I think that with a 686 kernel also the problem
had been solved from the moment that the kernel is nearer the hardware
architecture which I'm using.
Thanks to both for your replies.
Regards,
Daniel
[1] http://thread.gmane.org/gmane.comp.emulators.qemu/24029
--
Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Squeeze - Linux user #188.598
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-08-30 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 10:04 kvm-88: KVM_APIC_READ: read reserved register b0 Christoph Lechner
2009-08-29 16:37 ` Christoph Lechner
2009-08-29 21:20 ` Daniel Bareiro
2009-08-30 9:59 ` Christoph Lechner
2009-08-30 10:01 ` Gleb Natapov
2009-08-30 11:42 ` Christoph Lechner
2009-08-30 11:49 ` Gleb Natapov
2009-08-30 15:28 ` Daniel Bareiro [this message]
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=20090830152847.GC3014@defiant.freesoftware.org \
--to=daniel-listas@gmx.net \
--cc=dbareiro@gmx.net \
--cc=kvm@vger.kernel.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