From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: out of memory page request
Date: Tue, 09 Oct 2007 11:41:46 +0200 [thread overview]
Message-ID: <470B4CDA.40501@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A014E8B00-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Dong, Eddie wrote:
> kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org wrote:
>
>> David Brown wrote:
>>
>>>> Can you run 'gdb /path/to/kvm.ko' and post the output of
>>>> 'disassemble ioapic_mmio_write' please?
>>>>
>>>>
>>>>
>>> Sorry for not getting back sooner.
>>>
>>> (gdb) disassemble ioapic_mmio_write
>>> Dump of assembler code for function ioapic_mmio_write:
>>>
>>>
>> The attached patch should fix, though there's probably another
>> problem lurking in there.
>>
>>
> Should we printk something to alert something error already?
> Eddie
>
It needs to be pr_debug() to avoid allowing a guest to spam the host
logs. But I don't think it will help in this case. There's probably a
bug under low memory conditions that causes the guest to execute
incorrectly, and it just happened to hit this bug. I don't think it's
really related to the ioapic.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-09 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 4:43 out of memory page request David Brown
[not found] ` <9c21eeae0710032143j3ed5f43dgc3858a8fde6806d1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-05 13:14 ` Avi Kivity
[not found] ` <470638A5.3020609-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-07 17:37 ` David Brown
[not found] ` <9c21eeae0710071037o452bea4bm706e044526ed7ab7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-08 8:03 ` Avi Kivity
[not found] ` <4709E43D.40003-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-08 23:53 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A014E8B00-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-09 9:41 ` Avi Kivity [this message]
2007-10-10 3:19 ` David Brown
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=470B4CDA.40501@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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