From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Kiselev,
Sergey" <sergey.kiselev-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Physical memory read: word crosses page boundary + host kernel oops
Date: Thu, 29 Mar 2007 16:30:05 +0200 [thread overview]
Message-ID: <460BCD6D.9020604@qumranet.com> (raw)
In-Reply-To: <C07C4589BE74A34981C3C3525EE1F80101AE2908-t8eeqVGEwHVP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Kiselev, Sergey wrote:
> Hi
>
> 1. It seems that first problem happens because this particular
> double-word (address 0x9FFFD) is located on the boundary between regular
> memory and video memory. Probably this address accessed because some bug
> in that old kernel (I don't see any good reason to read this location).
> But it will be nice to check for reads/writes to such addresses.
>
>
I agree.
> 2. Problem (oops) is gone away in rev 4571. Not sure why. Still it can
> be repeatedly reproduced on kvm-18.
>
> If needed, I can upload an image that reproduces these problems (~150MB
> compressed size).
>
I'd like to see it.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-03-29 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 14:28 Physical memory read: word crosses page boundary + host kernel oops Kiselev, Sergey
[not found] ` <C07C4589BE74A34981C3C3525EE1F80101AB0E55-t8eeqVGEwHVP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-03-27 14:45 ` Avi Kivity
[not found] ` <46092DF8.1020202-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-29 13:59 ` Kiselev, Sergey
[not found] ` <C07C4589BE74A34981C3C3525EE1F80101AE2908-t8eeqVGEwHVP9JyJpTNKArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-03-29 14:30 ` Avi Kivity [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=460BCD6D.9020604@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=sergey.kiselev-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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