 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-users] Re: [Xen-devel] Xen - Guest memory allocation
| To: | "dinesh chandrasekaran" <dinesh_chan8@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-users] Re: [Xen-devel] Xen - Guest memory allocation |
| From: | "Grzegorz Miłoś" <gm281@xxxxxxxxx> |
| Date: | Fri, 20 Jun 2008 18:03:20 +0100 |
| Cc: | xen developers community <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen users community <xen-users@xxxxxxxxxxxxxxxxxxx> |
| Delivery-date: | Fri, 20 Jun 2008 10:03:44 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=DZZglPBTSLINb2V8ZvBFPV3hEe9J6yTYJmj67mEebOM=; b=ol1AH3yH43CpJS6jOzAwJFrbWoZSBGRqk3MJUkXokxZvG40fq8/7HbE7daCz3LCr4M oeVZ2llqzOFxnB4tZb1Vxpuq0ec4ifbohrkCcNUHi+MkO+sNVmXTKHUiXTmAk4sglDuY Z2OD+ZzlE4ZTrPqNnen2PuIb2zOgXLwxh3jOg= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=hULN/XGJGgqfmYsog7s3xc5nZSfxNm5yka38teo9XIiewLO6in9JZtwR6sS7OZTacc xfHLnoaTZWgW6gVis487XRQQJ8jg7tO3QYxZuTs7DHwbB0WNTdiWc/pk2eoZQ9TFYE5T p83z4D4W3MX7znoMHhRWwfh4irn8QPowF44Cc= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| In-reply-to: | <BAY111-W11EDA9AC4B7242CACCA89DB1A50@xxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <BAY111-W11EDA9AC4B7242CACCA89DB1A50@xxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
>> Why do you want to restrict DomU to use frames from certain range >> only? What's the logic behind that? > > Im trying to allocate memory for domUs from memory behind a PCI device. The > machine_addr_start is obtained by probing the device (as I know the vendor > and device info) during xen boot-up. That's what I was suspecting. I think you should give PCI passthrough a go first. PCI passthrough allows a PCI device to be hidden away from Dom0 and exported to a DomU. You achieve the first by passing pciback.hide=(XX:XX.X) option to Dom0 kernel and adding pci = [ 'XX:XX.X′ ] to DomU config file. You'll also need CONFIG_XEN_PCIDEV_FRONTEND=y and CONFIG_XEN_PCIDEV_BACKEND=y in your DomU and Dom0 kernel configs. Hope this helps Gr(z)egor(z) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| Previous by Date: | Re: [Xen-devel] [PATCH][2/2] AMD PowerNow! in the Hypervisor (hypervisor changes), Keir Fraser |
|---|---|
| Next by Date: | [Xen-devel] [PATCH] PV-GRUB: compilation fix caused by 17880, Samuel Thibault |
| Previous by Thread: | RE: [Xen-users] Re: [Xen-devel] Xen - Guest memory allocation, dinesh chandrasekaran |
| Next by Thread: | FW: [Xen-users] Re: [Xen-devel] Xen - Guest memory allocation, dinesh chandrasekaran |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
