All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, gcosta@redhat.com
Subject: Re: [Qemu-devel] Re: [PATCH] Make page_find() return 0 for too-large addresses
Date: Fri, 12 Sep 2008 18:47:04 -0300	[thread overview]
Message-ID: <20080912214704.GC10147@blackpad> (raw)
In-Reply-To: <48CADEC2.3060204@codemonkey.ws>

On Fri, Sep 12, 2008 at 04:27:30PM -0500, Anthony Liguori wrote:
> Eduardo Habkost wrote:
>> On Fri, Sep 12, 2008 at 05:14:06PM -0300, Eduardo Habkost wrote:
>>   
>>> On Fri, Sep 12, 2008 at 02:50:33PM -0500, Anthony Liguori wrote:
>>>     
>>>> Eduardo Habkost wrote:
>>>>       
>>>>> On some cases, such as under KVM, tb_invalidate_phys_page_range()
>>>>> may be called for large addresses, when qemu is configured to more than
>>>>> 4GB of RAM.
>>>>>
>>>>> On these cases, qemu was crashing because it was using an index too
>>>>> large for l1_map[], that supports only 32-bit addresses when compiling
>>>>> without CONFIG_USER_ONLY.
>>>>>           
>> <snip>
>>   
>
> So... are you building with kqemu enabled?

No, as I've stated in the reply I've sent before the patch.


> If so,  
> TARGET_PHYS_ADDR_SPACE_BITS will be 32.  So I don't think this sort of  
> work-around is correct.  A better solution would be to validate ram_size  
> against TARGET_PHYS_ADDR_SPACE_BITS.

This is a good idea (maybe it is already checked?), but it is not the
case I am dealing with.


>
> To put it another way, if you have kqemu enabled (at build time), you  
> cannot use > ~4GB of memory for the guest.

Right.

-- 
Eduardo

  reply	other threads:[~2008-09-12 21:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 18:58 [PATCH] Make page_find() return 0 for too-large addresses Eduardo Habkost
2008-09-12 18:58 ` [Qemu-devel] " Eduardo Habkost
2008-09-12 19:50 ` Anthony Liguori
2008-09-12 19:50   ` [Qemu-devel] " Anthony Liguori
2008-09-12 20:14   ` Eduardo Habkost
2008-09-12 20:14     ` [Qemu-devel] " Eduardo Habkost
2008-09-12 20:44     ` Eduardo Habkost
2008-09-12 21:27       ` Anthony Liguori
2008-09-12 21:47         ` Eduardo Habkost [this message]
2008-09-15 13:08         ` Glauber Costa
2008-09-15 13:08           ` Glauber Costa
2008-09-15 15:29       ` Anthony Liguori
2008-09-15 15:48         ` Eduardo Habkost
2008-09-15 15:57           ` Anthony Liguori

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=20080912214704.GC10147@blackpad \
    --to=ehabkost@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=gcosta@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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.