public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Izik Eidus <ieidus@redhat.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH] kvm-userspace: set pci mem to start at 0xc100000 and vesa to 0xc000000
Date: Sat, 17 Jan 2009 03:23:14 +0200	[thread overview]
Message-ID: <49713302.1010705@redhat.com> (raw)
In-Reply-To: <20090117005748.GA32499@sequoia.sous-sol.org>

Chris Wright wrote:
> * Izik Eidus (ieidus@redhat.com) wrote:
>   
>> This patch make the pci mem region larger (1 giga now).
>> this is needed for pci devices that require large amount of memory
>> such as video cards.
>>
>> for pea guests this patch is not an issue beacuse the guest OS will map
>> the rest of the ram after 0x100000000...,
>> for 32bits that arent pea, it mean the maximum memory that would be
>> avaible now is 3giga.
>>     
>
> Seems a little heavy handed.
>
> a) Given the size...code could be cleaned up so that a simple constant
> change doesn't need to touch so much code.
>   

Yea it probably can...

> b) It is brute force.  I'm not sure it really matters all that much to
> limit a 32-bit (non-PAE) guest to 3G, but it's a little extreme for the
> cases that don't care about the large hole. 
>
> Is there anyway to make it dynamic based on the requirements of the
> devices that are part of the launched VM?
>   

There is (you need to transfer data to the bios but it is possible...), 
the thing is - there was concern that
it will make windows crazy if you keep changing the devices physical mapping

Avi what do you think?

> thanks,
> -chris
>   


  reply	other threads:[~2009-01-17  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11  1:25 [PATCH 0/1] pci hole remaping Izik Eidus
2009-01-11  1:25 ` [PATCH] kvm-userspace: set pci mem to start at 0xc100000 and vesa to 0xc000000 Izik Eidus
2009-01-17  0:57   ` Chris Wright
2009-01-17  1:23     ` Izik Eidus [this message]
2009-01-18  8:41       ` 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=49713302.1010705@redhat.com \
    --to=ieidus@redhat.com \
    --cc=avi@redhat.com \
    --cc=chrisw@sous-sol.org \
    --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